部署方式:
采用helm部署
Ingress-nginx 版本:v0.41.2
[root@master ingress-nginx]# cat values-prod.yaml# values-prod.yamlcontroller:name: controllerimage:repository: cnych/ingress-nginxtag: "v0.41.2"digest:dnsPolicy: ClusterFirstWithHostNethostNetwork: truepublishService: # hostNetwork 模式下设置为false,通过节点IP地址上报ingress status数据enabled: falsekind: DaemonSet# tolerations: # kubeadm 安装的集群默认情况下master是有污点,需要容忍这个污点才可以部署# - key: "node-role.kubernetes.io/master"# operator: "Equal"# effect: "NoSchedule"# nodeSelector: # 固定到master1节点# kubernetes.io/hostname: "master1"service: # HostNetwork 模式不需要创建serviceenabled: falsedefaultBackend:enabled: truename: defaultbackendimage:repository: cnych/ingress-nginx-defaultbackendtag: "1.5"[root@master ingress-nginx]#
[root@master ~]# kubectl get nodes -o wideNAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIMEmaster Ready master 7d11h v1.19.8 192.168.11.150 <none> CentOS Linux 7 (Core) 3.10.0-1062.el7.x86_64 docker://20.10.7node1 Ready worker 7d11h v1.19.8 192.168.11.151 <none> CentOS Linux 7 (Core) 3.10.0-1062.el7.x86_64 docker://20.10.7node2 Ready worker 7d11h v1.19.8 192.168.11.152 <none> CentOS Linux 7 (Core) 3.10.0-1062.el7.x86_64 docker://20.10.7[root@master ~]#
[root@master ~]# kubectl -n ingress-nginx get allNAME READY STATUS RESTARTS AGEpod/ingress-nginx-controller-4xt4x 1/1 Running 0 10hpod/ingress-nginx-controller-lpdvw 1/1 Running 1 10hpod/ingress-nginx-defaultbackend-796bdb7766-r9gsg 1/1 Running 0 10hNAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGEservice/ingress-nginx-controller-admission ClusterIP 10.233.14.225 <none> 443/TCP 10hservice/ingress-nginx-defaultbackend ClusterIP 10.233.51.252 <none> 80/TCP 10hNAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGEdaemonset.apps/ingress-nginx-controller 2 2 2 2 2 kubernetes.io/os=linux 10hNAME READY UP-TO-DATE AVAILABLE AGEdeployment.apps/ingress-nginx-defaultbackend 1/1 1 1 10hNAME DESIRED CURRENT READY AGEreplicaset.apps/ingress-nginx-defaultbackend-796bdb7766 1 1 1 10h[root@master ~]#
