Kubernetes實驗 Service
文章目錄
Service
Service是Pod的邏輯分組，Service使用Label selector來匹配Pod的Labels（Pod用Labels來確定自己在哪個Service分組）
Service能夠提供負載均衡的能力，但只有4層負載均衡能力
Service的型別：
- ClusterIP：預設型別，自動分配一個僅Cluster內部可以訪問的虛擬IP
- NodePort：在ClusterIP基礎上為Service在每臺機器上繫結一個埠，外部可以通過NodeIP:NodePort來訪問該服務
- LoadBalancer：在NodePort的基礎上，藉助cloud provider建立一個外部負載均衡器，並將請求轉發到NodeIP:NodePort
- ExternalName：把叢集外的服務引入到叢集內部，在叢集內部直接使用
ClusterIP
當請求傳送到對應ClusterIP和埠，
將被轉發（iptables或ipvs）到kube-proxy中，
kube-proxy內部對請求進行負載均衡，
並查詢該Service下對應Pod的地址和埠，
再將請求轉發到Pod的地址和埠
# 先建立一個控制器
apiVersion: apps/v1
kind: Deployment
metadata:
name: myapp-deployment
spec:
replicas: 3
selector:
matchLabels:
app: myapp
release: stabel
template:
metadata:
labels:
app: myapp
release: stabel
env: test
spec:
containers:
- name: myapp
image: nginx:1.8
imagePullPolicy: IfNotPresent
ports:
- name: http
containerPort: 80
---
# 再建立控制器下Pod的Service
apiVersion: v1
kind: Service
metadata:
name: myapp
spec:
# Service型別為ClusterIP
type: ClusterIP
# 如果Pod存在以下標籤，則Pod屬於該Service邏輯分組
selector:
app: myapp
release: stabel
# Pod要暴露到ClusterIP的埠組
ports:
- name: http
# ClusterIP要暴露的埠
port: 9999
# 目標Pod上的埠
targetPort: 80
kubectl get deployment,rs,pod,service -o wide
# NAME READY UP-TO-DATE AVAILABLE AGE CONTAINERS IMAGES SELECTOR
# deployment.apps/myapp-deployment 3/3 3 3 65s myapp nginx:1.8 app=myapp,release=stabel
# NAME DESIRED CURRENT READY AGE CONTAINERS IMAGES SELECTOR
# replicaset.apps/myapp-deployment-69696c78f7 3 3 3 65s myapp nginx:1.8 app=myapp,pod-template-hash=69696c78f7,release=stabel
# NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
# pod/myapp-deployment-69696c78f7-8p6xb 1/1 Running 0 65s 172.19.1.49 k8s-node01 <none> <none>
# pod/myapp-deployment-69696c78f7-spg8v 1/1 Running 0 65s 172.19.1.48 k8s-node01 <none> <none>
# pod/myapp-deployment-69696c78f7-wmrpj 1/1 Running 0 65s 172.19.2.21 k8s-node02 <none> <none>
# NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE SELECTOR
# service/kubernetes ClusterIP 172.18.0.1 <none> 443/TCP 3d19h <none>
# service/myapp ClusterIP 172.18.0.204 <none> 9999/TCP 65s app=myapp,release=stabel
kubectl run -it testservice --image=busybox --image-pull-policy=IfNotPresent --restart=Never --rm=true -- wget http://myapp:9999 -O - | cat -
# Connecting to myapp:9999 (172.18.0.204:9999)
# writing to stdout
# <!DOCTYPE html>
# <html>
# <head>
# <title>Welcome to nginx!</title>
# <style>
# body {
# width: 35em;
# margin: 0 auto;
# font-family: Tahoma, Verdana, Arial, sans-serif;
# }
# </style>
# </head>
# <body>
# <h1>Welcome to nginx!</h1>
# <p>If you see this page, the nginx web server is successfully installed and
# working. Further configuration is required.</p>
# <p>For online documentation and support please refer to
# <a href="http://nginx.org/">nginx.org</a>.<br/>
# Commercial support is available at
# <a href="http://nginx.com/">nginx.com</a>.</p>
# <p><em>Thank you for using nginx.</em></p>
# </body>
# </html>
# - 100% |********************************| 612 0:00:00 ETA
# written to stdout
# pod "testservice" deleted
# 在Pod中可以直接通過Pod的名字訪問（沒有service的情況下，Pod只能通過IP訪問目標Pod）
wget http://myapp:9999 -O - | cat -
# --2020-11-30 11:24:44-- http://myapp:9999/
# Resolving myapp (myapp)... failed: Name or service not known.
# wget: unable to resolve host address ‘myapp’
# 在叢集外則不行
Headless Service
apiVersion: v1
kind: Service
metadata:
name: myapp-headless
spec:
selector:
app: myapp
# 顯式宣告clusterIP
clusterIP: "None"
ports:
- port: 9992
targetPort: 80
kubectl get svc -o wide
# NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE SELECTOR
# kubernetes ClusterIP 172.18.0.1 <none> 443/TCP 3d23h <none>
# myapp ClusterIP 172.18.0.204 <none> 9999/TCP 3h56m app=myapp,release=stabel
# myapp-headless ClusterIP None <none> 9992/TCP 17s app=myapp
kubectl run -it testservice --image=busybox --image-pull-policy=IfNotPresent --restart=Never --rm=true -- ping myapp-headless
# If you don't see a command prompt, try pressing enter.
# 64 bytes from 172.19.1.48: seq=1 ttl=62 time=0.634 ms
# 64 bytes from 172.19.1.48: seq=2 ttl=62 time=0.620 ms
# ^C
# --- myapp-headless ping statistics ---
# 3 packets transmitted, 3 packets received, 0% packet loss
# round-trip min/avg/max = 0.595/0.616/0.634 ms
# 叢集內訪問myapp-headless獲得Pod地址
NodePort
在Node上開個埠，使叢集外部可以訪問內部服務
apiVersion: v1
kind: Service
metadata:
name: myapp-nodepod
spec:
type: NodePort
selector:
app: myapp
release: stabel
ports:
- name: http
# 叢集中暴露的埠
port: 9999
# 目標Pod上的埠
targetPort: 80
kubectl get svc -o wide
# NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE SELECTOR
# kubernetes ClusterIP 172.18.0.1 <none> 443/TCP 9m6s <none>
# myapp-nodepod NodePort 172.18.0.90 <none> 9999:31231/TCP 4m43s app=myapp,release=stabel
# 隨機生成叢集外部可訪問埠：31231
wget http://k8s-master01:31231 -O - | cat -
# --2020-11-30 15:56:15-- http://k8s-master01:31231/
# Resolving k8s-master01 (k8s-master01)... 172.16.22.101
# Connecting to k8s-master01 (k8s-master01)|172.16.22.101|:31231... connected.
# HTTP request sent, awaiting response... 200 OK
# Length: 612 [text/html]
# Saving to: ‘STDOUT’
# 100%[============================================================================>] 612 --.-K/s in 0s
# 2020-11-30 15:56:15 (34.6 MB/s) - written to stdout [612/612]
# <!DOCTYPE html>
# <html>
# <head>
# <title>Welcome to nginx!</title>
# <style>
# body {
# width: 35em;
# margin: 0 auto;
# font-family: Tahoma, Verdana, Arial, sans-serif;
# }
# </style>
# </head>
# <body>
# <h1>Welcome to nginx!</h1>
# <p>If you see this page, the nginx web server is successfully installed and
# working. Further configuration is required.</p>
# <p>For online documentation and support please refer to
# <a href="http://nginx.org/">nginx.org</a>.<br/>
# Commercial support is available at
# <a href="http://nginx.com/">nginx.com</a>.</p>
# <p><em>Thank you for using nginx.</em></p>
# </body>
# </html>
# 叢集外訪問k8s-master01:31231
kubectl run -it testservice --image=busybox --image-pull-policy=IfNotPresent --restart=Never --rm=true -- wget http://myapp-nodepod:9999 -O - | cat -
# Connecting to myapp-nodepod:9999 (172.18.0.90:9999)
# writing to stdout
# <!DOCTYPE html>
# <html>
# <head>
# <title>Welcome to nginx!</title>
# <style>
# body {
# width: 35em;
# margin: 0 auto;
# font-family: Tahoma, Verdana, Arial, sans-serif;
# }
# </style>
# </head>
# <body>
# <h1>Welcome to nginx!</h1>
# <p>If you see this page, the nginx web server is successfully installed and
# working. Further configuration is required.</p>
# <p>For online documentation and support please refer to
# <a href="http://nginx.org/">nginx.org</a>.<br/>
# Commercial support is available at
# <a href="http://nginx.com/">nginx.com</a>.</p>
# <p><em>Thank you for using nginx.</em></p>
# </body>
# </html>
# - 100% |********************************| 612 0:00:00 ETA
# written to stdout
# pod "testservice" deleted
# 叢集內訪問myapp-nodepod:9999
LoadBalancer
需要雲服務提供商支援
ExternalName
對映叢集外部服務到叢集內，通過定義外部服務的別名來對叢集內提供服務
apiVersion: v1
kind: Service
metadata:
name: my-baidu-service
spec:
type: ExternalName
# my-baidu-service.dufault.svc.cluster.local
externalName: www.baidu.com
kubectl get svc -o wide
# NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE SELECTOR
# kubernetes ClusterIP 172.18.0.1 <none> 443/TCP 45m <none>
# my-baidu-service ExternalName <none> www.baidu.com <none> 3m58s <none>
Ingress
官網：https://kubernetes.github.io/ingress-nginx/
nginx的修改版
根據不同的域名或路徑訪問不同的埠服務
Pod和Ingress通過Service關聯
Ingress作為統一入口，由Service關聯一組Pod
該元件非kubernetes內建元件，需要單獨安裝部署進kubernetes
安裝Ingress
# 只支援helm3部署
helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx
helm repo update
helm search repo ingress-nginx
helm install cs-ingress ingress-nginx/ingress-nginx
# NAME: cs-ingress
# LAST DEPLOYED: Sat Dec 5 13:32:23 2020
# NAMESPACE: default
# STATUS: deployed
# REVISION: 1
# TEST SUITE: None
# NOTES:
# The ingress-nginx controller has been installed.
# It may take a few minutes for the LoadBalancer IP to be available.
# You can watch the status by running 'kubectl --namespace default get services -o wide -w cs-ingress-ingress-nginx-controller'
# An example Ingress that makes use of the controller:
# apiVersion: networking.k8s.io/v1beta1
# kind: Ingress
# metadata:
# annotations:
# kubernetes.io/ingress.class: nginx
# name: example
# namespace: foo
# spec:
# rules:
# - host: www.example.com
# http:
# paths:
# - backend:
# serviceName: exampleService
# servicePort: 80
# path: /
# # This section is only required if TLS is to be enabled for the Ingress
# tls:
# - hosts:
# - www.example.com
# secretName: example-tls
# If TLS is enabled for the Ingress, a Secret containing the certificate and key must also be provided:
# apiVersion: v1
# kind: Secret
# metadata:
# name: example-tls
# namespace: foo
# data:
# tls.crt: <base64 encoded cert>
# tls.key: <base64 encoded key>
# type: kubernetes.io/tls
kubectl get all
# NAME READY STATUS RESTARTS AGE
# pod/cs-ingress-ingress-nginx-controller-6878568799-9spzb 1/1 Running 0 60s
# NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
# service/cs-ingress-ingress-nginx-controller LoadBalancer 172.18.0.125 <pending> 80:30730/TCP,443:31025/TCP 36m
# service/cs-ingress-ingress-nginx-controller-admission ClusterIP 172.18.0.142 <none> 443/TCP 36m
# service/kubernetes ClusterIP 172.18.0.1 <none> 443/TCP 4d3h
# NAME READY UP-TO-DATE AVAILABLE AGE
# deployment.apps/cs-ingress-ingress-nginx-controller 1/1 1 1 36m
# NAME DESIRED CURRENT READY AGE
# replicaset.apps/cs-ingress-ingress-nginx-controller-6878568799 1 1 1 36m
# 檢測已安裝版本
POD_NAME=$(kubectl get pods -l app.kubernetes.io/name=ingress-nginx -o jsonpath='{.items[0].metadata.name}')
kubectl exec -it $POD_NAME -- /nginx-ingress-controller --version
# -------------------------------------------------------------------------------
# NGINX Ingress controller
# Release: v0.41.2
# Build: d8a93551e6e5798fc4af3eb910cef62ecddc8938
# Repository: https://github.com/kubernetes/ingress-nginx
# nginx version: nginx/1.19.4
# -------------------------------------------------------------------------------
使用Ingress
apiVersion: apps/v1
kind: Deployment
metadata:
name: web
spec:
selector:
matchLabels:
app: myapp
template:
metadata:
labels:
app: myapp
spec:
containers:
- name: myapp-container
image: nginx:1.19-alpine
imagePullPolicy: IfNotPresent
ports:
- name: web
containerPort: 80
---
apiVersion: v1
kind: Service
metadata:
name: web
spec:
type: NodePort
selector:
app: myapp
ports:
- name: web
port: 60000
targetPort: 80
---
# 建立Ingress規則
apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:
name: example-ingress
spec:
rules:
# 訪問後端應用時使用的域名
- host: example.ingredemo.com
http:
paths:
# 路徑
- path: /
backend:
# 後端應用的Service名字
serviceName: web
# 後端應用的Service埠
servicePort: 60000
kubectl get all -o wide
# NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
# pod/cs-ingress-ingress-nginx-controller-6878568799-9spzb 1/1 Running 0 59m 172.19.1.97 k8s-node01 <none> <none>
# pod/web-84c44bf89d-mzcgh 1/1 Running 0 7s 172.19.1.100 k8s-node01 <none> <none>
# NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE SELECTOR
# service/cs-ingress-ingress-nginx-controller LoadBalancer 172.18.0.125 <pending> 80:30730/TCP,443:31025/TCP 95m app.kubernetes.io/component=controller,app.kubernetes.io/instance=cs-ingress,app.kubernetes.io/name=ingress-nginx
# service/cs-ingress-ingress-nginx-controller-admission ClusterIP 172.18.0.142 <none> 443/TCP 95m app.kubernetes.io/component=controller,app.kubernetes.io/instance=cs-ingress,app.kubernetes.io/name=ingress-nginx
# service/kubernetes ClusterIP 172.18.0.1 <none> 443/TCP 4d4h <none>
# service/web NodePort 172.18.0.146 <none> 60000:31346/TCP 7s app=myapp
# NAME READY UP-TO-DATE AVAILABLE AGE CONTAINERS IMAGES SELECTOR
# deployment.apps/cs-ingress-ingress-nginx-controller 1/1 1 1 95m controller k8s.gcr.io/ingress-nginx/controller:v0.41.2@sha256:1f4f402b9c14f3ae92b11ada1dfe9893a88f0faeb0b2f4b903e2c67a0c3bf0de app.kubernetes.io/component=controller,app.kubernetes.io/instance=cs-ingress,app.kubernetes.io/name=ingress-nginx
# deployment.apps/web 1/1 1 1 7s myapp-container nginx:1.19-alpine app=myapp
# NAME DESIRED CURRENT READY AGE CONTAINERS IMAGES SELECTOR
# replicaset.apps/cs-ingress-ingress-nginx-controller-6878568799 1 1 1 95m controller k8s.gcr.io/ingress-nginx/controller:v0.41.2@sha256:1f4f402b9c14f3ae92b11ada1dfe9893a88f0faeb0b2f4b903e2c67a0c3bf0de app.kubernetes.io/component=controller,app.kubernetes.io/instance=cs-ingress,app.kubernetes.io/name=ingress-nginx,pod-template-hash=6878568799
# replicaset.apps/web-84c44bf89d 1 1 1 7s myapp-container nginx:1.19-alpine app=myapp,pod-template-hash=84c44bf89d
kubectl get ingress
# Warning: extensions/v1beta1 Ingress is deprecated in v1.14+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress
# NAME CLASS HOSTS ADDRESS PORTS AGE
# example-ingress <none> example.ingredemo.com 80 43s
kubectl get svc
# NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
# cs-ingress-ingress-nginx-controller LoadBalancer 172.18.0.125 <pending> 80:30730/TCP,443:31025/TCP 106m
# cs-ingress-ingress-nginx-controller-admission ClusterIP 172.18.0.142 <none> 443/TCP 106m
# kubernetes ClusterIP 172.18.0.1 <none> 443/TCP 4d5h
# web NodePort 172.18.0.146 <none> 60000:31346/TCP 15s
# ----------------------------------------------------------------------------------------------------------------------------------------------------
# 直接用地址和埠訪問後端對外服務（埠為31346）
curl k8s-master01:31346
# <!DOCTYPE html>
# <html>
# <head>
# <title>Welcome to nginx!</title>
# <style>
# body {
# width: 35em;
# margin: 0 auto;
# font-family: Tahoma, Verdana, Arial, sans-serif;
# }
# </style>
# </head>
# <body>
# <h1>Welcome to nginx!</h1>
# <p>If you see this page, the nginx web server is successfully installed and
# working. Further configuration is required.</p>
# <p>For online documentation and support please refer to
# <a href="http://nginx.org/">nginx.org</a>.<br/>
# Commercial support is available at
# <a href="http://nginx.com/">nginx.com</a>.</p>
# <p><em>Thank you for using nginx.</em></p>
# </body>
# </html>
# 向hosts寫入域名
echo "example.ingredemo.com 172.16.22.101" >> /etc/hosts
# 測試域名（埠為ingress對外埠30730）
curl example.ingredemo.com:30730
# <!DOCTYPE html>
# <html>
# <head>
# <title>Welcome to nginx!</title>
# <style>
# body {
# width: 35em;
# margin: 0 auto;
# font-family: Tahoma, Verdana, Arial, sans-serif;
# }
# </style>
# </head>
# <body>
# <h1>Welcome to nginx!</h1>
# <p>If you see this page, the nginx web server is successfully installed and
# working. Further configuration is required.</p>
# <p>For online documentation and support please refer to
# <a href="http://nginx.org/">nginx.org</a>.<br/>
# Commercial support is available at
# <a href="http://nginx.com/">nginx.com</a>.</p>
# <p><em>Thank you for using nginx.</em></p>
# </body>
# </html>
# 使用錯誤的域名訪問ingress埠（一個錯誤的示範）
curl k8s-master01:30730
# <html>
# <head><title>404 Not Found</title></head>
# <body>
# <center><h1>404 Not Found</h1></center>
# <hr><center>nginx</center>
# </body>
# </html>
# 使用IP訪問ingress埠（另一個錯誤的示範）
curl 172.16.22.101:30730
# <html>
# <head><title>404 Not Found</title></head>
# <body>
# <center><h1>404 Not Found</h1></center>
# <hr><center>nginx</center>
# </body>
# </html>
HPA
HPA通過定期查詢Pod的狀態，獲得Pod的監控資料
然後通過現有Pod的使用率的平均值跟目標使用率進行比較
Pod的使用率的平均值：
監控資源1分鐘使用的平均值/設定的每個Pod的request資源值
擴容的Pod數計算公式：
TargetNumOfPods = ceil(sum(CurrentPodsCPUUtuilization)/Target)
Ceil函式：
返回大於或等於指定表示式的最小整數
每次擴容和縮容時都有一個視窗時間，
即每次伸縮操作後就會進入視窗時間，
在此時間段不會再進行伸縮操作。
- 擴容後3分鐘視窗時間
- 縮容後5分鐘視窗時間
之後如果avg/Target下降9%，會再進行縮容，
或增加10%，將進行擴容
HPA的實現條件：
- HPA不能autoscale daemonset型別control
- 要實現autoscale，Pod必須設定request
監控指標收集過程：
- kubelet收集本機的監控資料，儲存與內容中
- Metrics server週期性的從kubelet的Summary API採集資訊
- 通過metric-api的形式暴露出去
- HPA控制器直接同metric-api獲取監控指標
安裝與應用
https://github.com/kubernetes-sigs/metrics-server
# 安裝metrics server
wget https://github.com/kubernetes-sigs/metrics-server/releases/latest/download/components.yaml
# 在components.yaml的容器命令中加入可以使用不安全的tls（command節）
# containers:
# - args:
# - --cert-dir=/tmp
# - --secure-port=4443
# - --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname
# - --kubelet-use-node-status-port
# command: ["/metrics-server", "--kubelet-insecure-tls"] 加入這一行
# image: k8s.gcr.io/metrics-server/metrics-server:v0.4.1
# imagePullPolicy: IfNotPresent
# 沒有上面那步，探針將無法探測成功
kubectl apply -f components.yaml
# serviceaccount/metrics-server created
# clusterrole.rbac.authorization.k8s.io/system:aggregated-metrics-reader created
# clusterrole.rbac.authorization.k8s.io/system:metrics-server created
# rolebinding.rbac.authorization.k8s.io/metrics-server-auth-reader created
# clusterrolebinding.rbac.authorization.k8s.io/metrics-server:system:auth-delegator created
# clusterrolebinding.rbac.authorization.k8s.io/system:metrics-server created
# service/metrics-server created
# deployment.apps/metrics-server created
# apiservice.apiregistration.k8s.io/v1beta1.metrics.k8s.io created
kubectl -n kube-system get all | grep metrics
# pod/metrics-server-56c887f446-4gxg8 1/1 Running 0 10m
# service/metrics-server ClusterIP 172.18.0.15 <none> 443/TCP 10m
# deployment.apps/metrics-server 1/1 1 1 10m
# replicaset.apps/metrics-server-56c887f446 1 1 1 10m
# 測試是否安裝成功
kubectl top node
# NAME CPU(cores) CPU% MEMORY(bytes) MEMORY%
# k8s-master01 229m 5% 2883Mi 36%
# k8s-node01 110m 2% 2271Mi 28%
# k8s-node02 42m 1% 2660Mi 33%
使用HPA
apiVersion: apps/v1
kind: Deployment
metadata:
name: test-hpa-deployment
labels:
app: test-hpa
spec:
selector:
matchLabels:
app: test-hpa-pod
template:
metadata:
labels:
app: test-hpa-pod
spec:
containers:
- name: app-container
image: nginx:1.19-alpine
imagePullPolicy: IfNotPresent
ports:
- containerPort: 80
# 要使用HPA必須要有請求資源，不同版本HPA對能支援的資源不同
resources:
requests:
cpu: 100m
---
apiVersion: v1
kind: Service
metadata:
name: web-test-hpa-service
spec:
type: NodePort
selector:
app: test-hpa-pod
ports:
- name: web
port: 60001
targetPort: 80
---
# HPA版本影響HPA能度量的資源
apiVersion: autoscaling/v2beta2
# HPA
kind: HorizontalPodAutoscaler
metadata:
name: test-hpa
spec:
# 最多增加到10個例項
maxReplicas: 10
# 最少減少到1個例項
minReplicas: 1
# 被測量目標參照
scaleTargetRef:
apiVersion: apps/v1
kind: Deployment
name: test-hpa-deployment
metrics:
- type: Resource
resource:
name: cpu
target:
# 型別：利用率
type: Utilization
averageUtilization: 80
kubectl get hpa
# NAME REFERENCE TARGETS MINPODS MAXPODS REPLICAS AGE
# test-hpa Deployment/test-hpa-deployment 0%/80% 1 10 1 3m21s
kubectl get hpa,svc,deployment,pod
# NAME REFERENCE TARGETS MINPODS MAXPODS REPLICAS AGE
# horizontalpodautoscaler.autoscaling/test-hpa Deployment/test-hpa-deployment 0%/80% 1 10 1 4m26s
# NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
# service/web-test-hpa-service NodePort 172.18.0.193 <none> 60001:32553/TCP 4m26s
# NAME READY UP-TO-DATE AVAILABLE AGE
# deployment.apps/web 1/1 1 1 10h
# NAME READY STATUS RESTARTS AGE
# pod/test-hpa-deployment-5bfcdf778-m7rgr 1/1 Running 0 4m26s
相關文章
- Kubernetes 實戰——發現應用（Service）
- kubernetes實踐之二十四：Service
- kubernetes實踐之十四：Service Account與Secret
- kubernetes實踐之六十五：Service Mesh
- Kubernetes Service之ClusterIP
- kubernetes實踐之四十三： Service詳解
- Kubernetes中Service機制
- Azure Kubernetes Service 入門
- Kubernetes中Service的使用
- kubernetes實踐之五十三：Service中的故障排查
- kubernetes實踐之四十八：Service Controller與Endpoint ControllerController
- 【解構雲原生】初識Kubernetes Service
- 【Azure App Service】.NET程式碼實驗App Service應用中獲取TLS/SSL 證書 (App Service Windows)APPTLSWindows
- kubernetes實踐之七十四：Service Mesh Meetup深圳站學習總結
- 淺入Kubernetes(11)：瞭解 Service 和 Endpoint
- 如何在Kubernetes裡建立一個Nginx serviceNginx
- 驗證Kubernetes YAML的最佳實踐和策略YAML
- kubernetes實踐之七：安全機制API Server認證之Service Account TokenAPIServer
- 在 Google Kubernetes Cluster 上使用 HANA Expression Database ServiceGoExpressDatabase
- Kubernetes的資源控制器和Service(四)
- 不懂 Kubernetes 實現雲原生是什麼體驗？
- 阿里雲Kubernetes容器服務Istio實踐之整合日誌服務Log Service阿里
- 如何利用 knest 構建資料中心的 Kubernetes as a Service？
- Kubernetes--初體驗
- Kubernetes-6.服務、負載均衡、聯網（2）Service負載
- 淺入Kubernetes(7)：應用部署例項，Deployment、Service、ReplicaSet
- Kubernetes 兩步驗證 - 使用 Serverless 實現動態准入控制Server
- service mesh istio微服務實驗之監控日誌與視覺化微服務視覺化
- @Validated、@Valid在service層引數校驗
- 基於Kubernetes服務發現機制的探討Non Service
- service mesh istio-1.0 快速安裝體驗
- 阿里巴巴的 Kubernetes 應用管理實踐經驗與教訓阿里
- eBPF in kubernetes 實戰eBPF
- kubernetes實踐之六十：Cabin-Manage Kubernetes
- Azure Kubernates Service 更新｜提升開發體驗和效率
- 【Azure App Service】在App Service for Windows上驗證能佔用的記憶體最大值APPWindows記憶體
- containerd 與安全沙箱的 Kubernetes 初體驗AI
- 華為雲對Kubernetes在Serverless Container產品落地中的實踐經驗ServerAI