一 什么是微服务
用控制器来完成集群的工作负载，那么应用如何暴漏出去？需要通过微服务暴漏出去后才能被访问
Service是一组提供相同服务的Pod对外开放的接口。
借助Service，应用可以实现服务发现和负载均衡。
service默认只支持4层负载均衡能力，没有7层功能。（可以通过Ingress实现）
二 微服务的类型
| 微服务类型 | 作用描述 | 核心特点 |
|---|---|---|
| ClusterIP | 默认值，k8s 系统给 service 自动分配的虚拟 IP，只能在集群内部访问 | 集群内通信，不能外部访问，最常用默认类型 |
| NodePort | 将 Service 通过指定的 Node 上的端口暴露给外部，访问任意一个NodeIP:nodePort都将路由到 ClusterIP |
在所有节点打开一个端口，外部可通过节点IP+端口访问；端口范围默认 30000~32767 |
| LoadBalancer | 在 NodePort 的基础上，借助 cloud provider 创建一个外部的负载均衡器，并将请求转发到NodeIP:NodePort，此模式只能在云服务器上使用 |
公有云专属，云厂商提供真实公网 LB，流量先到 LB 再转发到集群 |
| ExternalName | 将服务通过 DNS CNAME 记录方式转发到指定的域名（通过 spec.externalName 设定） |
不代理流量，仅 DNS 解析转发，用于集群内访问外部域名 |
示例：
1.利用testservice暴露控制器
cpp
[root@master weifuwu]# kubectl create deployment peng1 --image myapp:v1 --replicas 2 --dry-run=client -o yaml > peng1.yaml
[root@master weifuwu]# kubectl create service clusterip --tcp 80:80 peng1 --dry-run=client -o yaml >> peng1.yaml
[root@master weifuwu]# vim peng1.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
labels:
app: peng1
name: peng1
spec:
replicas: 2
selector:
matchLabels:
app: peng1
template:
metadata:
labels:
app: peng1
spec:
containers:
- image: myapp:v1
name: myapp
---
apiVersion: v1
kind: Service
metadata:
labels:
app: peng1
name: peng1
spec:
ports:
- name: 80-80
port: 80
protocol: TCP
targetPort: 80
selector:
app: peng1
type: ClusterIP
[root@master weifuwu]# kubectl apply -f peng1.yaml
deployment.apps/peng1 created
cpp
Every 1.0s: kubectl describe svc testservice ;kubectl get pod... master: Thu Sep 3 11:20:12 2026
Name: testservice
Namespace: default
Labels: app=testservice
Annotations: <none>
Selector: app=testservice
Type: ClusterIP
IP Family Policy: SingleStack
IP Families: IPv4
IP: 10.106.33.104
IPs: 10.106.33.104
Port: webport 80/TCP
TargetPort: 80/TCP
Endpoints: #被暴露业务为空
Session Affinity: None
Internal Traffic Policy: Cluster
Events: <none>
NAME READY STATUS RESTARTS AGE LABELS
peng1-5cd469c67f-bx25k 1/1 Running 0 3m19s app=peng1,pod-template-hash=5cd469c67
f
peng1-5cd469c67f-kcchq 1/1 Running 0 3m19s app=peng1,pod-template-hash=5cd469c67
cpp
[root@master weifuwu]# kubectl get services
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
extrnalname ExternalName <none> www.xiao.org <none> 7d21h
kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 13d
peng1 ClusterIP 10.103.48.1 <none> 80/TCP 7m10s微服务默认使用iptables调度
cpp
[root@master weifuwu]# kubectl get services -o wide
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE SELECTOR
extrnalname ExternalName <none> www.xiao.org <none> 7d21h app=extrnalname
kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 13d <none>
peng1 ClusterIP 10.103.48.1 <none> 80/TCP 9m19s app=peng1
[root@master weifuwu]# iptables -t nat -nL2.建立pod并测试pod是否可以被testservice暴漏,当标签与service选择器上的标签不同，pod不会被暴漏
cpp
[root@master weifuwu]# kubectl run peng2 --image myapp:v1 --dry-run=client -o yaml > peng2.yml
[root@master weifuwu]# vim peng2.yml
apiVersion: v1
kind: Pod
metadata:
labels:
run: peng2
name: peng2
spec:
containers:
- image: myapp:v1
name: peng2
[root@master weifuwu]# kubectl apply -f peng2.yml
pod/peng2 created
cpp
#检控
[root@k8s-master ~]# watch -n 1 "kubectl describe svc testservice ; kubectl get pods --show-labels "
#检控官内容跟
Name: testservice
Namespace: default
Labels: app=testservice
Annotations: <none>
Selector: app=webserver
Type: ClusterIP
IP Family Policy: SingleStack
IP Families: IPv4
IP: 10.100.62.227
IPs: 10.100.62.227
Port: webport 80/TCP
TargetPort: 80/TCP
Endpoints: #没有被暴露
Session Affinity: None
Internal Traffic Policy: Cluster
Events: <none>更改标签后看监控
cpp
[root@master weifuwu]# kubectl label pods peng2 app=testservice
pod/peng2 labeled
Every 1.0s: kubectl describe svc testservice ;kubectl get pod... master: Thu Sep 3 12:27:24 2026
Name: testservice
Namespace: default
Labels: app=testservice
Annotations: <none>
Selector: app=testservice
Type: ClusterIP
IP Family Policy: SingleStack
IP Families: IPv4
IP: 10.106.33.104
IPs: 10.106.33.104
Port: webport 80/TCP
TargetPort: 80/TCP
Endpoints: 10.244.104.7:80 #被暴露了
Session Affinity: None
Internal Traffic Policy: Cluster
Events: <none>
NAME READY STATUS RESTARTS AGE LABELS
peng2 1/1 Running 0 49m app=testservice,run=peng2
[root@master weifuwu]# curl 10.106.33.104
Hello MyApp | Version: v1 | <a href="hostname.html">Pod Name</a>二.利用service暴漏控制
cpp
[root@master weifuwu]# kubectl delete -f peng2.yml
pod "peng2" deleted from default namespace
[root@master weifuwu]# kubectl create service clusterip --tcp 80:80 peng3 --dry-run=client -o yaml >peng3.yaml
[root@master weifuwu]# kubectl create deployment peng3 --image myapp:v1 --dry-run=client -o yaml >> peng3.yaml
[root@master weifuwu]# vim peng3.yaml
apiVersion: v1
kind: Service
metadata:
labels:
app: peng3
name: peng3
spec:
ports:
- name: 80-80
port: 80
protocol: TCP
targetPort: 80
selector:
app: peng3
type: ClusterIP
---
apiVersion: apps/v1
kind: Deployment
metadata:
labels:
app: peng3
name: peng3
spec:
replicas: 1
selector:
matchLabels:
app: peng3
template:
metadata:
labels:
app: peng3
spec:
containers:
- image: myapp:v1
name: myapp
[root@master weifuwu]# kubectl apply -f peng3.yaml
service/peng3 created
deployment.apps/peng3 created
Every 1.0s: kubectl describe svc peng3 ; kubectl get deploy --show-labels;kubectl get pods -o wide --show-labels master: Thu Sep 3 12:42:37 2026
Name: peng3
Namespace: default
Labels: app=peng3
Annotations: <none>
Selector: app=peng3
Type: ClusterIP
IP Family Policy: SingleStack
IP Families: IPv4
IP: 10.100.250.6
IPs: 10.100.250.6
Port: 80-80 80/TCP
TargetPort: 80/TCP
Endpoints: 10.244.104.9:80
Session Affinity: None
Internal Traffic Policy: Cluster
Events: <none>
NAME READY UP-TO-DATE AVAILABLE AGE LABELS
peng3 1/1 1 1 86s app=peng3
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES LABELS
peng3-768845b8f7-xw6vj 1/1 Running 0 86s 10.244.104.9 node2 <none> <none> app=peng3,pod-template-hash=768845b8f7
[root@master weifuwu]# curl 10.100.250.6
Hello MyApp | Version: v1 | <a href="hostname.html">Pod Name</a>
[root@master weifuwu]# curl 10.100.250.6/hostname.html
peng3-768845b8f7-xw6vj三 ipvs模式
Service 是由 kube-proxy 组件，加上 iptables 来共同实现的
kube-proxy 通过 iptables 处理 Service 的过程，需要在宿主机上设置相当多的 iptables 规则，如 果宿主机有大量的Pod，不断刷新iptables规则，会消耗大量的CPU资源
IPVS模式的service，可以使K8s集群支持更多量级的Pod
3.1 ipvs模式配置方式
1 在所有节点中安装ipvsadm
cpp
[root@master weifuwu]# for i in 100 10 20 30
> do ssh -l root 172.25.254.$i "dnf install ipvsadm -y"
> done2 修改master节点的代理配置
cpp
[root@k8s-master ~]# kubectl -n kube-system edit cm kube-proxy
59 mode: "ipvs"3 重启pod，在pod运行时配置文件中采用默认配置，当改变配置文件后已经运行的pod状态不会变化， 所以要重启pod
cpp
[root@master weifuwu]# kubectl -n kube-system get pods | awk '/kube-proxy/{system("kubectl -n kube-system delete pods "$1)}'
pod "kube-proxy-f2rv7" deleted from kube-system namespace
pod "kube-proxy-hrfz5" deleted from kube-system namespace
pod "kube-proxy-l99fq" deleted from kube-system namespace
pod "kube-proxy-rznvr" deleted from kube-system namespace
[root@master weifuwu]# ipvsadm -Ln
IP Virtual Server version 1.2.1 (size=4096)
Prot LocalAddress:Port Scheduler Flags
-> RemoteAddress:Port Forward Weight ActiveConn InActConn
TCP 172.17.0.1:30665 rr
TCP 172.17.0.1:30753 rr
-> 10.244.166.142:80 Masq 1 0 0
TCP 172.17.0.1:31395 rr
-> 10.244.166.142:443 Masq 1 0 0
TCP 172.17.0.1:32600 rr
TCP 172.25.254.52:80 rr
-> 10.244.166.142:80 Masq 1 0 0
TCP 172.25.254.52:443 rr
-> 10.244.166.142:443 Masq 1 0 0切换ipvs模式后，kube-proxy会在宿主机上添加一个虚拟网卡：kube-ipvs0，并分配所有service IP
cpp
[root@master weifuwu]# ip a | tail
5: flannel.1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state UNKNOWN group default
link/ether aa:62:e1:8c:d6:ac brd ff:ff:ff:ff:ff:ff
inet 10.244.0.0/32 scope global flannel.1
valid_lft forever preferred_lft forever
inet6 fe80::a862:e1ff:fe8c:d6ac/64 scope link
valid_lft forever preferred_lft forever
8: cali697e9cc6c1d@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether ee:ee:ee:ee:ee:ee brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet6 fe80::ecee:eeff:feee:eeee/64 scope link
valid_lft forever preferred_lft forever四 微服务类型详解
4.1 clusterip
特点：
clusterip模式只能在集群内访问，并对集群内的pod提供健康检测和自动发现功能
示例：
cpp
[root@master weifuwu]# cp peng3.yaml peng4.yaml
[root@master weifuwu]# vim peng4.yaml
#把name 部分改为 peng4
[root@master weifuwu]# kubectl delete -f peng3.yaml
service "peng3" deleted from default namespace
deployment.apps "peng3" deleted from default namespace
[root@master weifuwu]# vim peng4.yaml
[root@master weifuwu]# kubectl apply -f peng4.yaml
service/peng4 created
deployment.apps/peng4 created
[root@master weifuwu]# kubectl describe svc peng4
Name: peng4
Namespace: default
Labels: app=peng4
Annotations: <none>
Selector: app=peng4
Type: ClusterIP
IP Family Policy: SingleStack
IP Families: IPv4
IP: 10.100.123.217 #vip模式访问此ip可以进行调度
IPs: 10.100.123.217
Port: 80-80 80/TCP
TargetPort: 80/TCP
Endpoints: 10.244.166.146:80,10.244.104.10:80
Session Affinity: None
Internal Traffic Policy: Cluster
Events: <none>2.在k8s集群内部解析
cs
#资源解析时输入的格式
#dig <servicename>.<namespace>.<sourcetype>.cluster.local @10.96.0.10
cpp
[root@master weifuwu]# kubectl -n kube-system get svc
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
kube-dns ClusterIP 10.96.0.10 <none> 53/UDP,53/TCP,9153/TCP 13d
[root@master weifuwu]# dig peng4.default.svc.cluster.local @10.96.0.10
; <<>> DiG 9.16.23-RH <<>> peng4.default.svc.cluster.local @10.96.0.10
;; global options: +cmd
;; Got answer:
;; WARNING: .local is reserved for Multicast DNS
;; You are currently testing what happens when an mDNS query is leaked to DNS
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 46556
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: c27397b31f8be880 (echoed)
;; QUESTION SECTION:
;peng4.default.svc.cluster.local. IN A
;; ANSWER SECTION:
peng4.default.svc.cluster.local. 30 IN A 10.100.123.217
;; Query time: 33 msec
;; SERVER: 10.96.0.10#53(10.96.0.10)
;; WHEN: Thu Sep 03 13:03:45 CST 2026
;; MSG SIZE rcvd: 119#进群内部通常使用service的解析名称进行通信地址的指定，因为资源的ip会变但是名字不会
4.2 ClusterIP中的特殊模式headless
headless（无头服务）
对于无头 Services 并不会分配 Cluster IP，kube-proxy不会处理它们， 而且平台也不会为它们进行负 载均衡和路由，集群访问通过dns解析直接指向到业务pod上的IP，所有的调度有dns单独完成
当设定此模式，那么service不会被分配一个ip而是直接把endpoints上的ip直接通过dns裸漏
示例：
cpp
[root@master weifuwu]# cp peng4.yaml peng5.yaml
[root@master weifuwu]# vim peng5.yaml
apiVersion: v1
kind: Service
metadata:
labels:
app: peng5
name: peng5
spec:
ports:
- name: 80-80
port: 80
protocol: TCP
targetPort: 80
selector:
app: peng5
type: ClusterIP
clusterIP: None
---
apiVersion: apps/v1
kind: Deployment
metadata:
labels:
app: peng5
name: peng5
spec:
replicas: 2
selector:
matchLabels:
app: peng5
template:
metadata:
labels:
app: peng5
spec:
containers:
- image: myapp:v1
name: myapp
cpp
[root@master weifuwu]# kubectl apply -f peng5.yaml
service/peng5 created
deployment.apps/peng5 created
[root@master weifuwu]# kubectl describe svc peng5
Name: peng5
Namespace: default
Labels: app=peng5
Annotations: <none>
Selector: app=peng5
Type: ClusterIP
IP Family Policy: SingleStack
IP Families: IPv4
IP: None #没有VIP
IPs: None
Port: 80-80 80/TCP
TargetPort: 80/TCP
Endpoints: 10.244.104.11:80,10.244.166.147:80
Session Affinity: None
Internal Traffic Policy: Cluster
Events: <none>
[root@master weifuwu]# dig peng5.default.svc.cluster.local @10.96.0.10
; <<>> DiG 9.16.23-RH <<>> peng5.default.svc.cluster.local @10.96.0.10
;; global options: +cmd
;; Got answer:
;; WARNING: .local is reserved for Multicast DNS
;; You are currently testing what happens when an mDNS query is leaked to DNS
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58401
;; flags: qr aa rd; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: e235ea7f3023022c (echoed)
;; QUESTION SECTION:
;peng5.default.svc.cluster.local. IN A
;; ANSWER SECTION:
peng5.default.svc.cluster.local. 30 IN A 10.244.104.11 #直接解析到pod上
peng5.default.svc.cluster.local. 30 IN A 10.244.166.147
;; Query time: 32 msec
;; SERVER: 10.96.0.10#53(10.96.0.10)
;; WHEN: Thu Sep 03 13:14:21 CST 2026
;; MSG SIZE rcvd: 166
cpp
#测试
[root@master weifuwu]# kubectl run peng --image busyboxplus -it
All commands and output from this session will be recorded in container logs, including credentials and sensitive information passed through the command prompt.
If you don't see a command prompt, try pressing enter.
[ root@peng:/ ]$ nslookup peng5-service
Server: 10.96.0.10
Address 1: 10.96.0.10 kube-dns.kube-system.svc.cluster.local
nslookup: can't resolve 'peng5-service'
[ root@peng:/ ]$ nslookup peng5
Server: 10.96.0.10
Address 1: 10.96.0.10 kube-dns.kube-system.svc.cluster.local
Name: peng5
Address 1: 10.244.166.147 10-244-166-147.peng5.default.svc.cluster.local
Address 2: 10.244.104.11 10-244-104-11.peng5.default.svc.cluster.local
[ root@peng:/ ]$ curl peng5
Hello MyApp | Version: v1 | <a href="hostname.html">Pod Name</a>
[ root@peng:/ ]$ curl peng5/hostname.html
peng5-6566bdbcc5-zh5224.3 nodeport
通过ipvs暴漏端口从而使外部主机通过master节点的对外ip:来访问pod业务
其访问过程为：
示例：
cpp
[root@master weifuwu]# cp peng5.yaml nodepoty.yaml
[root@master weifuwu]# vim nodepoty.yaml
apiVersion: v1
kind: Service
metadata:
labels:
app: peng5
name: peng5
spec:
ports:
- name: 80-80
port: 80
protocol: TCP
targetPort: 80
nodePort: 30951 #指定端口，如不写可以从30000~32767之间随机分
selector:
app: peng5
type: NodePort #nodeport模式
---
apiVersion: apps/v1
kind: Deployment
metadata:
labels:
app: peng5
name: peng5
spec:
replicas: 2
selector:
matchLabels:
app: peng5
template:
metadata:
labels:
app: peng5
spec:
containers:
- image: myapp:v1
name: myapp
[root@master weifuwu]# kubectl apply -f nodepoty.yaml
service/peng5 created
deployment.apps/peng5 created
[root@master weifuwu]# ipvsadm -Ln #查看策略访问
cpp
2026-09-03 13:30.41 /home/mobaxterm curl 172.25.254.100:30951/hostname.html
peng5-6566bdbcc5-mhz9s
✓
2026-09-03 13:32.03 /home/mobaxterm curl 172.25.254.100:30951/hostname.html
peng5-6566bdbcc5-55vn8
✓
2026-09-03 13:32.06 /home/mobaxterm curl 172.25.254.100:30951/hostname.html
peng5-6566bdbcc5-mhz9s
✓
2026-09-03 13:32.07 /home/mobaxterm curl 172.25.254.100:30951/hostname.html
peng5-6566bdbcc5-55vn8端口突破
cpp
[root@master weifuwu]# vim nodepoty.yaml
nodePort: 44444 #书写范围外的端口
[root@master weifuwu]# kubectl delete -f nodepoty.yaml
service "peng5" deleted from default namespace
deployment.apps "peng5" deleted from default namespace
[root@master weifuwu]# kubectl apply -f nodepoty.yaml
deployment.apps/peng5 created
The Service "peng5" is invalid: spec.ports[0].nodePort: Invalid value: 44444: provided port is not in the valid range. The range of valid ports is 30000-32767
#正常情况下，是不能超出30000-32767 范围
cpp
[root@master weifuwu]# vim /etc/kubernetes/manifests/kube-apiserver.yaml
42行 - --servicr-node-port-range=30000-50000
#加入上面内容
[root@master weifuwu]# kubectl apply -f nodepoty.yaml
service/peng5 created
deployment.apps/peng5 created
[root@master weifuwu]# kubectl describe svc peng5
Name: peng5
Namespace: default
Labels: app=peng5
Annotations: <none>
Selector: app=peng5
Type: NodePort
IP Family Policy: SingleStack
IP Families: IPv4
IP: 10.106.184.157
IPs: 10.106.184.157
Port: 80-80 80/TCP
TargetPort: 80/TCP
NodePort: 80-80 44444/TCP #可以看到44444
Endpoints: 10.244.104.16:80,10.244.166.151:80
Session Affinity: None
External Traffic Policy: Cluster
Internal Traffic Policy: Cluster
Events: <none>4.4 loadbalancer
云平台会为我们分配vip并实现访问，如果是裸金属主机那么需要metallb来实现ip的分配
示例：
cpp
[root@master weifuwu]# cp nodepoty.yaml loadbalancer.yml
[root@master weifuwu]# vim loadbalancer.yml
#修改
type: LoadBalancer
[root@master weifuwu]# kubectl apply -f loadbalancer.yml
service/peng5 created
deployment.apps/peng5 created
默认无法分配外部访问IP
[root@master weifuwu]# kubectl get svc
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
extrnalname ExternalName <none> www.xiao.org <none> 8d
kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 13d
peng5 LoadBalancer 10.103.153.206 <pending> 80:49079/TCP 8s
LoadBalancer模式适用云平台，裸金属环境需要安装metallb提供支持4.5 metalLB
官网： https://metallb.universe.tf/installation/
示例：
cpp
[root@master weifuwu]# cp nodepoty.yaml loadbalancer.yml
[root@master weifuwu]# vim loadbalancer.yml
type: LoadBalancer
[root@master weifuwu]# kubectl apply -f loadbalancer.yml
service/peng5 created
deployment.apps/peng5 created
[root@master weifuwu]# kubectl get svc
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
extrnalname ExternalName <none> www.xiao.org <none> 8d
kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 13d
peng5 LoadBalancer 10.103.153.206 <pending> 80:49079/TCP 8smetalLB功能
为LoadBalancer分配vip
构建metalLB上传镜像
cpp
[root@k8s-master services]# tar zxf metallb-v0.16.1.tar.gz
[root@k8s-master metaLLB]# docker load -i metallb-v0.16.1.tar
[root@k8s-master metaLLB]# docker tag quay.io/metallb/controller:v0.16.1 reg.timinglee.org/metallb/controller:v0.16.1
[root@k8s-master metaLLB]# docker tag quay.io/metallb/speaker:v0.16.1 reg.timinglee.org/metallb/speaker:v0.16.1
[root@k8s-master metaLLB]# docker push reg.timinglee.org/metallb/controller:v0.16.1
[root@k8s-master metaLLB]# docker push reg.timinglee.org/metallb/speaker:v0.16.1
cpp
[root@master weifuwu]# kubectl edit configmap -n kube-system kube-proxy
mode: "ipvs"
60 ipvs:
61 strictARP: true
cpp
删除旧的kube-proxy ，看是否能够正常运行
[root@master metaLLB]# kubectl -n kube-system get pods NAME READY STATUS RESTARTS AGE
kube-proxy-4r5mq 1/1 Running 0 7m24s
kube-proxy-crqwf 1/1 Running 0 22m
kube-proxy-h7hn5 1/1 Running 0 22m
kube-proxy-n97f8 1/1 Running 0 22m
[root@master metaLLB]# kubectl -n kube-system delete pods kube-proxy-4r5mq kube-proxy-crqwf kube-proxy-h7hn5 kube-proxy-n97f8
pod "kube-proxy-4r5mq" deleted from kube-system namespace
pod "kube-proxy-crqwf" deleted from kube-system namespace
pod "kube-proxy-h7hn5" deleted from kube-system namespace
pod "kube-proxy-n97f8" deleted from kube-system namespace
[root@master metaLLB]# kubectl -n kube-system get pods
NAME READY STATUS RESTARTS AGE
kube-proxy-9jn7k 1/1 Running 0 18s
kube-proxy-c7plc 1/1 Running 0 18s
kube-proxy-kh5c9 1/1 Running 0 18s
kube-proxy-tjq6f 1/1 Running 0 18s
cpp
[root@master metaLLB]# ls
1-metallb-native.yaml 2-metallb-confmap.yml metallb-v0.16.1.tar
[root@master metaLLB]# vim 1-metallb-native.yaml
2136: image: metallb/controller:v0.16.1
2233: image: metallb/speaker:v0.16.1
[root@master metaLLB]# vim 2-metallb-confmap.yml
apiVersion: metallb.io/v1beta1
kind: IPAddressPool
metadata:
name: first-pool
namespace: metallb-system
spec:
addresses:
- 172.25.254.50-172.25.254.99
---
apiVersion: metallb.io/v1beta1
kind: L2Advertisement
metadata:
name: example
namespace: metallb-system
spec:
ipAddressPools:
- first-pool
[root@master metaLLB]# kubectl apply -f 2-metallb-confmap.yml -f 1-metallb-native.yaml
cpp
[root@master metaLLB]# kubectl get namespaces
NAME STATUS AGE
default Active 14d
ingress-nginx Active 8d
kube-flannel Active 14d
kube-node-lease Active 14d
kube-public Active 14d
kube-system Active 14d
metallb-system Active 8d
[root@master metaLLB]# kubectl -n metallb-system get pods
NAME READY STATUS RESTARTS AGE
controller-b7cdf5787-tbh94 1/1 Running 0 82m
speaker-hpdfz 1/1 Running 1 (5d6h ago) 8d
speaker-ksjtv 1/1 Running 2 (17m ago) 8d
speaker-wlcpf 1/1 Running 2 (17h ago) 8d
speaker-z9gzr 1/1 Running 1 (5d6h ago) 8d
[root@master metaLLB]# kubectl -n metallb-system get cm
NAME DATA AGE
kube-root-ca.crt 1 8d
metallb-excludel2 1 8d
[root@master metaLLB]# cd ..
[root@master weifuwu]# kubectl apply -f loadbalancer.yml
service/peng5 created
deployment.apps/peng5 created
在loadbalancer服务中是否有ip
[root@master weifuwu]# kubectl get svc
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
extrnalname ExternalName <none> www.xiao.org <none> 8d
kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 14d
peng5 LoadBalancer 10.97.187.57#这里有了 172.25.254.50 80:44242/TCP 7s
#可以访问
[root@master weifuwu]# curl 172.25.254.50
Hello MyApp | Version: v1 | <a href="hostname.html">Pod Name</a>4.6 externalname
开启services后，不会被分配IP，而是用dns解析CNAME固定域名来解决ip变化问题
一般应用于外部业务和pod沟通或外部业务迁移到pod内时
在应用向集群迁移过程中，externalname在过度阶段就可以起作用了。
集群外的资源迁移到集群时，在迁移的过程中ip可能会变化，但是域名+dns解析能完美解决此问题
示例：
cpp
[root@master weifuwu]# vim extrnalname.yaml
apiVersion: v1
kind: Service
metadata:
labels:
app: extrnalname
name: extrnalname
spec:
selector:
app: extrnalname
type: ExternalName
externalName: www.xiao.org
[root@master weifuwu]# kubectl delete -f loadbalancer.yml
service "peng5" deleted from default namespace
deployment.apps "peng5" deleted from default namespace
[root@master weifuwu]# kubectl apply -f extrnalname.yaml
service/extrnalname created
[root@master weifuwu]# kubectl get services
extrnalname kubernetes testservice web1 web2 webcluster webserver
[root@master weifuwu]# kubectl get services extrnalname
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
extrnalname ExternalName <none> www.xiao.org <none> 24s五 Ingress-nginx
官网：
https://kubernetes.github.io/ingress-nginx/deploy/#bare-metal-clusters
5.1 ingress-nginx功能
一种全局的、为了代理不同后端 Service 而设置的负载均衡服务,支持7层
Ingress由两部分组成：Ingress controller和Ingress服务
Ingress Controller 会根据你定义的 Ingress 对象，提供对应的代理能力。
业界常用的各种反向代理项目，比如 Nginx、HAProxy、Envoy、Traefik 等，都已经为Kubernetes 专门维护了对应的 Ingress Controller。
5.2 部署ingress
5.2.1 下载部署文件
cpp
[root@master services]# wget https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.15.1/deploy/static/provider/baremetal/deploy.yaml
[root@master services]# grep image: deploy.yaml #有科技的可以用这个方法，没有的话就用压缩包
image: registry.k8s.io/ingress-nginx/controller:v1.15.1@sha256:594ceea76b01c592858f803f9ff4d2cb40542cae2060410b2c95f75907d659e1
image: registry.k8s.io/ingress-nginx/kube-webhook-certgen:v1.6.9@sha256:01038e7de14b78d702d2849c3aad72fd25903c4765af63cf16aa3398f5d5f2dd
image: registry.k8s.io/ingress-nginx/kube-webhook-certgen:v1.6.9@sha256:01038e7de14b78d702d2849c3aad72fd25903c4765af63cf16aa3398f5d5f2dd
[root@master services]# docker pull registry.k8s.io/ingress-nginx/controller:v1.15.1
[root@master services]# docker pull registry.k8s.io/ingress-nginx/kube-webhook-certgen:v1.6.9
cpp
#上传ingress所需镜像到harbor
[root@k8s-master ingress-v1.5.1]# docker tag registry.k8s.io/ingress-nginx/controller:v1.15.1 reg.timinglee.org/ingress-nginx/controller:v1.15.1
[root@k8s-master ingress-v1.5.1]# docker push reg.timinglee.org/ingress-nginx/controller:v1.15.1
[root@k8s-master ~]# docker tag registry.k8s.io/ingress-nginx/kube-webhook-certgen:v1.6.9 reg.timinglee.org/ingress-nginx/kube-webhook-certgen:v1.6.9
[root@k8s-master ~]# docker push reg.timinglee.org/ingress-nginx/kube-webhook-certgen:v1.6.95.2.2 安装ingress
cpp
#更改deploy.yaml
[root@k8s-master ingress-v1.5.1]# vim deploy.yaml
444: image: ingress-nginx/controller:v1.15.1
547: image: ingress-nginx/kube-webhook-certgen:v1.6.9
603: image: ingress-nginx/kube-webhook-certgen:v1.6.9
365 type: LoadBalancer
cpp
[root@master services]# kubectl -n ingress-nginx edit svc ingress-nginx-controller
51 type: LoadBalancer
[root@master services]# kubectl apply -f deploy.yaml
namespace/ingress-nginx unchanged
serviceaccount/ingress-nginx unchanged
serviceaccount/ingress-nginx-admission unchanged
role.rbac.authorization.k8s.io/ingress-nginx unchanged
[root@master services]# kubectl -n ingress-nginx get svc
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
ingress-nginx-controller LoadBalancer 10.104.76.127 172.25.254.52 80:30753/TCP,443:31395/TCP 8d
ingress-nginx-controller-admission ClusterIP 10.101.73.172 <none> 443/TCP 8d在ingress-nginx-controller中看到的对外IP就是ingress最终对外开放的ip
5.2.3 测试ingress
cpp
#业务1
[root@k8s-master services]# kubectl create deployment myappv1 --image myapp:v1 --replicas 2 --dry-run=client -o yaml > myappv1.yaml
[root@k8s-master services]# kubectl create service clusterip servicev1 --tcp 80:80 --dry-run=client -o yaml >> myappv1.yaml
[root@k8s-master services]# vim myappv1.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
labels:
app: myappv1
name: myappv1
spec:
replicas: 2
selector:
matchLabels:
app: myappv1
template:
metadata:
labels:
app: myappv1
spec:
containers:
- image: myapp:v1
name: myapp
---
apiVersion: v1
kind: Service
metadata:
labels:
app: servicev1
name: servicev1
spec:
ports:
- name: 80-80
port: 80
protocol: TCP
targetPort: 80
selector:
app: myappv1
type: ClusterIP
cpp
#业务2
[root@k8s-master services]# vim myappv2.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
labels:
app: myappv2
name: myappv2
spec:
replicas: 2
selector:
matchLabels:
app: myappv2
template:
metadata:
labels:
app: myappv2
spec:
containers:
- image: myapp:v2
name: myapp
---
apiVersion: v1
kind: Service
metadata:
labels:
app: servicev2
name: servicev2
spec:
ports:
- name: 80-80
port: 80
protocol: TCP
targetPort: 80
selector:
app: myappv2
type: ClusterIP
cpp
[root@master services]# kubectl apply -f myappv1.yaml
deployment.apps/myappv1 created
service/servicev1 created
[root@master services]# kubectl apply -f myappv2.yaml
deployment.apps/myappv2 created
service/servicev2 created
[root@master services]# kubectl get svc
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
extrnalname ExternalName <none> www.xiao.org <none> 18m
kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 14d
servicev1 ClusterIP 10.98.237.73 <none> 80/TCP 37s
servicev2 ClusterIP 10.100.197.219 <none> 80/TCP 10s
[root@master services]# curl 10.98.237.73
Hello MyApp | Version: v1 | <a href="hostname.html">Pod Name</a>
[root@master services]# curl 10.100.197.219
Hello MyApp | Version: v2 | <a href="hostname.html">Pod Name</a>
[root@master services]# kubectl get pods
NAME READY STATUS RESTARTS AGE
myappv1-8676894bf8-cqxll 1/1 Running 0 102s
myappv1-8676894bf8-qdldl 1/1 Running 0 102s
myappv2-688fc4d776-pqx9w 1/1 Running 0 75s
myappv2-688fc4d776-z99rm 1/1 Running 0 75s
cpp
[root@master services]# kubectl create ingress ingress1 --class nginx:1.26 --rule "*/=servicev1:80" --dry-run=client -o yaml > 1-ingress.yml
[root@master services]# vim 1-ingress.yml
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: ingress1
annotations:
nginx.ingress.kubernetes.io/rewrite-target: /
spec:
ingressClassName: nginx
rules:
- host: 'www.xiao.org'
http:
paths:
- backend:
service:
name: servicev1
port:
number: 80
path: /v1
pathType: Prefix
- backend:
service:
name: servicev2
port:
number: 80
path: /v2
pathType: Prefix
cpp
[root@master services]# kubectl apply -f 1-ingress.yml
ingress.networking.k8s.io/ingress1 created
[root@master services]# kubectl describe ingress ingress1
Name: ingress1
Labels: <none>
Namespace: default
Address:
Ingress Class: nginx
Default backend: <default>
Rules:
Host Path Backends
---- ---- --------
www.xiao.org
/v1 servicev1:80 (10.244.135.8:80,10.244.166.155:80)
/v2 servicev2:80 (10.244.104.20:80,10.244.135.9:80)
Annotations: nginx.ingress.kubernetes.io/rewrite-target: /
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Sync 23s nginx-ingress-controller Scheduled for sync
cpp
2026-09-03 16:56.53 /home/mobaxterm vim /etc/hosts
172.25.254.52 myapp-tls.xiao.org www.xiao.org myapp1.xiao.org myapp2.xiao.org
#注意：这里的本地解析IP是前面deplay.yaml部署ingress
#[root@k8s-master ingress-v1.5.1]# kubectl -n ingress-nginx get svc
#NAME TYPE CLUSTER-IP EXTERNAL-IP #PORT(S) AGE
#ingress-nginx-controller LoadBalancer 10.103.86.192 172.25.254.52
#是这个的 EXTERNAL-IP
#测试
2026-09-03 16:56.40 /home/mobaxterm curl www.xiao.org/v1
Hello MyApp | Version: v1 | <a href="hostname.html">Pod Name</a>
✓
2026-09-03 16:56.51 /home/mobaxterm curl www.xiao.org/v2
Hello MyApp | Version: v2 | <a href="hostname.html">Pod Name</a>5.3 ingress 的高级用法
5.3.1 基于域名的访问
cpp
[root@master services]# kubectl delete -f 1-ingress.yml
ingress.networking.k8s.io "ingress1" deleted from default namespace
[root@master services]# vim 2-ingress.yaml
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: ingress2
annotations:
# nginx.ingress.kubernetes.io/rewrite-target: /
spec:
ingressClassName: nginx
rules:
- host: myapp1.xiao.org
http:
paths:
- backend:
service:
name: servicev1
port:
number: 80
path: /
pathType: Prefix
- host: myapp2.xiao.org
http:
paths:
- backend:
service:
name: servicev2
port:
number: 80
path: /
pathType: Prefix
[root@master services]# kubectl apply -f 2-ingress.yaml
ingress.networking.k8s.io/ingress1 created
cpp
[root@master services]# kubectl describe ingress ingress2
Name: ingress2
Labels: <none>
Namespace: default
Address: 172.25.254.10
Ingress Class: nginx
Default backend: <default>
Rules:
Host Path Backends
---- ---- --------
myapp1.xiao.org
/ servicev1:80 (10.244.135.8:80,10.244.166.155:80)
myapp2.xiao.org
/ servicev2:80 (10.244.104.20:80,10.244.135.9:80)
Annotations: <none>
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Sync 12s (x2 over 31s) nginx-ingress-controller Scheduled for sync
2026-09-03 16:59.25 /home/mobaxterm curl myapp1.xiao.org
Hello MyApp | Version: v1 | <a href="hostname.html">Pod Name</a>
2026-09-03 17:17.22 /home/mobaxterm curl myapp2.xiao.org
Hello MyApp | Version: v2 | <a href="hostname.html">Pod Name</a>
#注意：前面的myappv1.yaml和myppv2.yaml 不能删除哈，
#不然后端没有代理就会访问失败5.3.2基于动静分离的方式
cpp
[root@master services]# vim 3-ingress.yaml
[root@master services]# kubectl apply -f 3-ingress.yaml
ingress.networking.k8s.io/ingress1 created
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: ingress1
annotations:
nginx.ingress.kubernetes.io/use-regex: "true"
nginx.ingress.kubernetes.io/rewrite-target: /index.html
spec:
ingressClassName: nginx
rules:
- host: www.xiao.org
http:
paths:
- backend:
service:
name: servicev1
port:
number: 80
path: /xiao
pathType: ImplementationSpecific
- backend:
service:
name: servicev2
port:
number: 80
path: /lin
pathType: ImplementationSpecific
cpp
2026-09-03 17:23.31 /home/mobaxterm curl www.xiao.org/xiao/
Hello MyApp | Version: v1 | <a href="hostname.html">Pod Name</a>
✓
2026-09-03 17:24.15 /home/mobaxterm curl www.xiao.org/lin/
Hello MyApp | Version: v2 | <a href="hostname.html">Pod Name</a>5.3.3 建立tls加密
cpp
[root@master services]# openssl req -newkey rsa:2048 -nodes -keyout tls.key -x509 -days 365 -subj "/CN=nginxsvc/O=nginxsvc" -out tls.crt
...+++++++++++++++++++++++++++++++++++++++*.........+.+......+...+......+.....+................+.....+.........+.+...+..+......+++++++++++++++++++++++++++++++++++++++*.+.......+........+...+......+...+............+.........+.+.....+.+..+...+...+......................+.....
[root@master services]# vim 4-ingress.yml
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: ingress1
annotations:
nginx.ingress.kubernetes.io/ssl-redirect: "true" #访问强制跳转到https
nginx.ingress.kubernetes.io/rewrite-target: /
spec:
tls:
- hosts:
- myapp-tls.xiao.org
secretName: web-tls-secret
ingressClassName: nginx
rules:
- host: myapp-tls.xiao.org
http:
paths:
- backend:
service:
name: servicev1
port:
number: 80
path: /
pathType: Prefix
[root@master services]# kubectl apply -f 4-ingress.yml
cpp
2026-09-03 17:41.34 /home/mobaxterm vim /etc/hosts
172.25.254.52 myapp-tls.xiao.org www.xiao.org myapp1.xiao.org myapp2.xiao.org
#需要有解析哟
2026-09-03 17:45.35 /home/mobaxterm curl -k https://myapp-tls.xiao.org/
Hello MyApp | Version: v1 | <a href="hostname.html">Pod Name</a>5.3.4 建立auth认证
cpp
#安装生成认证文件模板工具
[root@master services]# dnf install httpd-tools -y
正在更新 Subscription Management 软件仓库。
无法读取客户身份
本系统尚未在权利服务器中注册。可使用 "rhc" 或 "subscription-manager" 进行注册。
Repository AppStream is listed more than once in the configuration
Repository BaseOS is listed more than once in the configuration
上次元数据过期检查：3:09:41 前，执行于 2026年09月03日 星期四 14时39分05秒。
软件包 httpd-tools-2.4.62-13.el9.x86_64 已安装。
依赖关系解决。
无需任何处理。
完毕！
#生成认证文件
[root@master services]# htpasswd -cm auth admin
New password:
Re-type new password:
Adding password for user admin
[root@master services]# cat auth
admin:$apr1$dN9OHNsL$MSj5Bged30Ff.D0FmgwRm0
cpp
#将认证文件注入k8s中
[root@k8s-master ~]# kubectl create secret generic web-auth --from-file auth
# 在ingress中配置auth认证
[root@k8s-master services]# vim 5-ingress.yaml
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: ingress1
annotations:
nginx.ingress.kubernetes.io/auth-type: basic
nginx.ingress.kubernetes.io/auth-secret: web-auth
nginx.ingress.kubernetes.io/auth-realm: "Please input username and password"
nginx.ingress.kubernetes.io/rewrite-target: /
spec:
ingressClassName: nginx
rules:
- host: www.timinglee.org
http:
paths:
- backend:
service:
name: servicev1
port:
number: 80
path: /v1
pathType: Prefix
[root@k8s-master services]# kubectl apply -f 5-ingress.yaml
#验证auth
[Administrator.DESKTOP-VJ307M3] ➤ curl www.timinglee.org/v1
<html>
<head><title>401 Authorization Required</title></head>
<body>
<center><h1>401 Authorization Required</h1></center>
<hr><center>nginx</center>
</body>
</html>
[Administrator.DESKTOP-VJ307M3] ➤ curl www.timinglee.org/v1 -uadmin:lee
Hello MyApp | Version: v1 | <a href="hostname.html">Pod Name</a>5.3.5rewrite重定向
利用网页从写定义默认发布文件
cpp
[root@master services]# vim 6-ingress.yaml
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: ingress1
annotations:
nginx.ingress.kubernetes.io/app-root: /hostname.html
spec:
ingressClassName: nginx
rules:
- host: www.xiao.org
http:
paths:
- backend:
service:
name: servicev1
port:
number: 80
path: /
pathType: Prefix
[root@master services]# kubectl apply -f 6-ingress.yaml
ingress.networking.k8s.io/ingress1 created
cpp
2026-09-03 17:54.14 /home/mobaxterm curl -I www.xiao.org
HTTP/1.1 302 Moved Temporarily
Date: Thu, 03 Sep 2026 10:01:41 GMT
Content-Type: text/html
Content-Length: 138
Connection: keep-alive
Location: http://www.xiao.org/hostname.html
✓
2026-09-03 18:01.01 /home/mobaxterm curl -L www.xiao.org
myappv1-8676894bf8-qdldl
✓
2026-09-03 18:01.13 /home/mobaxterm curl -L www.xiao.org
myappv1-8676894bf8-qdldl利用正侧表达式从定向网页
cpp
[root@master services]# vim 7-ingress.yaml
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: ingress1
annotations:
nginx.ingress.kubernetes.io/rewrite-target: /$2
nginx.ingress.kubernetes.io/use-regex: "true"
spec:
ingressClassName: nginx
rules:
- host: www.xiao.org
http:
paths:
- backend:
service:
name: servicev2
port:
number: 80
path: /lee(/*.*/*|$)(.*) #意思是访问xxx/lee/会被分配到v2上
pathType: ImplementationSpecific
- backend:
service:
name: servicev1
port:
number: 80
path: /
pathType: Prefix
cpp
[root@master services]# kubectl apply -f 7-ingress.yaml
ingress.networking.k8s.io/ingress1 created
2026-09-03 18:21.47 /home/mobaxterm curl -L www.xiao.org/xiao/lin
Hello MyApp | Version: v1 | <a href="hostname.html">Pod Name</a>
✓
2026-09-03 18:21.49 /home/mobaxterm curl -L www.xiao.org/lee/lin
Hello MyApp | Version: v2 | <a href="hostname.html">Pod Name</a>六 Canary金丝雀发布
6.1 什么是金丝雀发布
金丝雀发布（Canary Release）也称为灰度发布，是一种软件发布策略。
主要目的是在将新版本的软件全面推广到生产环境之前，先在一小部分用户或服务器上进行测试和验 证，以降低因新版本引入重大问题而对整个系统造成的影响。
是一种Pod的发布方式。金丝雀发布采取先添加、再删除的方式，保证Pod的总量不低于期望值。并且在 更新部分Pod后，暂停更新，当确认新Pod版本运行正常后再进行其他版本的Pod的更新。
6.2 Canary发布方式
其中header和weiht中的最多
6.2.1 基于header（http包头）灰度
通过Annotaion扩展
创建灰度ingress，配置灰度头部key以及value
灰度流量验证完毕后，切换正式ingress到新版本
之前我们在做升级时可以通过控制器做滚动更新，默认25%利用header可以使升级更为平滑，通过 key 和vule 测试新的业务体系是否有问题。
示例：
cpp
[root@master services]# vim cannary1.yaml
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: ingress1
annotations:
spec:
ingressClassName: nginx
rules:
- host: www.xiao.org
http:
paths:
- backend:
service:
name: servicev1
port:
number: 80
path: /
pathType: Prefix
---
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: ingress2
annotations:
nginx.ingress.kubernetes.io/canary: "true"
nginx.ingress.kubernetes.io/canary-by-header: "version"
nginx.ingress.kubernetes.io/canary-by-header-value: "2"
spec:
ingressClassName: nginx
rules:
- host: www.xiao.org
http:
paths:
- backend:
service:
name: servicev2
port:
number: 80
path: /
pathType: Prefix
[root@master services]# kubectl apply -f cannary1.yaml
ingress.networking.k8s.io/ingress1 created
ingress.networking.k8s.io/ingress2 created
cpp
2026-09-03 18:22.21 /home/mobaxterm curl www.xiao.org
Hello MyApp | Version: v1 | <a href="hostname.html">Pod Name</a>
2026-09-03 18:26.58 /home/mobaxterm curl -H "version:2" www.xiao.org
Hello MyApp | Version: v2 | <a href="hostname.html">Pod Name</a>6.2.2 基于权重的灰度发布
通过Annotaion拓展
创建灰度ingress，配置灰度权重以及总权重
灰度流量验证完毕后，切换正式ingress到新版本
示例：
cpp
[root@master services]# vim cannary2.yaml
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: ingress1
annotations:
spec:
ingressClassName: nginx
rules:
- host: www.xiao.org
http:
paths:
- backend:
service:
name: servicev1
port:
number: 80
path: /
pathType: Prefix
---
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: ingress2
annotations:
nginx.ingress.kubernetes.io/canary: "true"
nginx.ingress.kubernetes.io/canary-weight: "10"
nginx.ingress.kubernetes.io/canary-weight-total: "100"
spec:
ingressClassName: nginx
rules:
- host: www.xiao.org
http:
paths:
- backend:
service:
name: servicev2
port:
number: 80
path: /
pathType: Prefix
[root@master services]# kubectl apply -f cannary2.yaml
cpp
[root@master services]# kubectl get ingress
NAME CLASS HOSTS ADDRESS PORTS AGE
ingress1 nginx www.xiao.org 172.25.254.10 80 16s
ingress2 nginx www.xiao.org 172.25.254.10 80 16s
[root@master services]# vim check_cannary.sh
#!/bin/bash
v1=0
v2=0
for (( i=0; i<100; i++))
do
response=`curl -s www.timinglee.org |grep -c v1`
v1=`expr $v1 + $response`
v2=`expr $v2 + 1 - $response`
done
echo "v1:$v1, v2:$v2"
[root@master services]# sh check_cannary.sh