k8s的流量负载组件sevice用于四层路由负载ingress用于七层路由负载Service介绍Service概述在kubernetes中pod是应用程序的载体我们可以通过pod的ip来访问应用程序但是pod的ip地址不是固定的这也就意味着不方便直接采用pod的ip对服务进行访问。为了解决这个问题kubernetes提供了Service资源Service会对提供同一个服务的多个pod进行聚合并且提供一个统一的入口地址。通过访问Service的入口地址就能访问到后面的pod服务。Service在很多情况下只是一个概念真正起作用的其实是kube-proxy服务进程每个Node节点上都运行着一个kube-proxy服务进程。当创建Service的时候会通过api-server向etcd写入创建的service的信息而kube-proxy会基于监听的机制发现这种Service的变动然后它会将最新的Service信息转换成对应的访问规则。# 10.97.97.97:80 是service提供的访问入口 # 当访问这个入口的时候可以发现后面有三个pod的服务在等待调用 # kube-proxy会基于rr轮询的策略(ipvs的前提下)将请求分发到其中一个pod上去 # 这个规则会同时在集群内的所有节点上都生成所以在任何一个节点上访问都可以。 [rootnode1 ~]# ipvsadm -Ln IP Virtual Server version 1.2.1 (size4096) Prot LocalAddress:Port Scheduler Flags - RemoteAddress:Port Forward Weight ActiveConn InActConn TCP 10.97.97.97:80 rr - 10.244.1.39:80 Masq 1 0 0 - 10.244.1.40:80 Masq 1 0 0 - 10.244.2.33:80 Masq 1 0 0kube-proxy目前支持三种工作模式:userspace 模式userspace模式下kube-proxy会为每一个Service创建一个监听端口发向Cluster IP的请求被Iptables规则重定向 到kube-proxy监听的端口上kube-proxy根据LB算法选择一个提供服务的Pod并和其建立链接以将请求转发到Pod上。该模式下kube-proxy充当了一个四层负责均衡器的角色。由于kube-proxy运行在userspace中在进行转发处理时会增加内核和用户空间之间的数据拷贝虽然比较稳定但是效率比较低iptables 模式iptables模式下kube-proxy为service后端的每个Pod创建对应的iptables规则直接将发向Cluster IP的请求重定向到一个Pod IP。该模式下kube-proxy不承担四层负责均衡器的角色只负责创建iptables规则。该模式的优点是较userspace模式效率更高但不能提供灵活的LB策略当后端Pod不可用时也无法进行重试。ipvs 模式ipvs模式和iptables类 似kube-proxy监控Pod的变化并创建相应的ipvs规则。ipvs相对iptables转发效率更高。除此以外ipvs支持更多的LB算法。# 此模式必须安装ipvs内核模块否则会降级为iptables # 开启ipvs [rootmaster modules]# ipvsadm -Ln IP Virtual Server version 1.2.1 (size4096) Prot LocalAddress:Port Scheduler Flags - RemoteAddress:Port Forward Weight ActiveConn InActConn # mode模式改成ipvs--modeipvs [rootmaster modules]# kubectl edit cm kube-proxy -n kube-system configmap/kube-proxy edited # 等待自动重建 [rootmaster modules]# kubectl delete pod -l k8s-appkube-proxy -n kube-system pod kube-proxy-vxflz deleted pod kube-proxy-w886d deleted pod kube-proxy-xb7kp deleted [rootmaster modules]# ipvsadm -Ln IP Virtual Server version 1.2.1 (size4096) Prot LocalAddress:Port Scheduler Flags - RemoteAddress:Port Forward Weight ActiveConn InActConn TCP 10.96.0.1:443 rr - 192.168.109.100:6443 Masq 1 0 0 TCP 10.96.0.10:53 rr - 10.244.0.2:53 Masq 1 0 0 - 10.244.0.3:53 Masq 1 0 0 TCP 10.96.0.10:9153 rr - 10.244.0.2:9153 Masq 1 0 0 - 10.244.0.3:9153 Masq 1 0 0 TCP 10.110.157.232:443 rr - 192.168.109.101:4443 Masq 1 0 0 UDP 10.96.0.10:53 rr - 10.244.0.2:53 Masq 1 0 0 - 10.244.0.3:53 Masq 1 0 0Service类型Service的资源清单文件kind: Service # 资源类型 apiVersion: v1 # 资源版本 metadata: # 元数据 name: service # 资源名称 namespace: dev # 命名空间 spec: # 描述 selector: # 标签选择器用于确定当前service代理哪些pod(通过标签获取对应ip存入ipvs) app: nginx type: # Service类型指定service的访问方式 clusterIP: # 虚拟服务的ip地址 sessionAffinity: # session亲和性支持ClientIP、None两个选项同一个请求ip到同一个pod ports: # 端口信息 - protocol: TCP port: 3017 # service端口 targetPort: 5003 # pod端口 nodePort: 31122 # 主机端口# type: Service类型指定service的访问方式 - ClusterIP默认值它是Kubernetes系统自动分配的虚拟IP只能在集群内部访问 - NodePort将Service通过指定的Node上的端口暴露给外部通过此方法就可以在集群外部访问服务 - LoadBalancer使用外接负载均衡器完成到服务的负载分发注意此模式需要外部云环境支持 - ExternalName 把集群外部的服务引入集群内部直接使用Service使用实验环境准备在使用service之前首先利用Deployment创建出3个pod注意要为pod设置appnginx-pod的标签创建deployment.yaml内容如下apiVersion: apps/v1 kind: Deployment metadata: name: pc-deployment namespace: dev spec: replicas: 3 selector: matchLabels: app: nginx-pod template: metadata: labels: app: nginx-pod spec: containers: - name: nginx image: nginx ports: - containerPort: 80# 创建deploy [rootmaster k8sYamlForCSDN]# kubectl apply -f deployment.yaml deployment.apps/pc-deployment created # 查看pod详情 [rootmaster k8sYamlForCSDN]# kubectl get pods -n dev -o wide --show-labels NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES LABELS pc-deployment-6d99999569-dxpzt 1/1 Running 0 40s 10.244.2.101 node2 none none appnginx-pod,pod-template-hash6d99999569 pc-deployment-6d99999569-m69zc 1/1 Running 0 40s 10.244.1.71 node1 none none appnginx-pod,pod-template-hash6d99999569 pc-deployment-6d99999569-wk9nz 1/1 Running 0 40s 10.244.2.102 node2 none none appnginx-pod,pod-template-hash6d99999569 # 为了方便后面的测试修改下三台nginx的index.html页面三台修改的IP地址不一致 # kubectl exec -it pc-deployment-6d99999569-dxpzt -n dev /bin/sh # echo 10.244.2.101 /usr/share/nginx/html/index.html # kubectl exec -it pc-deployment-6d99999569-m69zc -n dev /bin/sh # echo 10.244.1.71 /usr/share/nginx/html/index.html # kubectl exec -it pc-deployment-6d99999569-wk9nz -n dev /bin/sh # echo 10.244.2.102 /usr/share/nginx/html/index.html # 修改完毕之后访问测试 [rootmaster k8sYamlForCSDN]# curl 10.244.2.101:80 10.244.2.101 [rootmaster k8sYamlForCSDN]# curl 10.244.1.71:80 10.244.1.71 [rootmaster k8sYamlForCSDN]# curl 10.244.2.102:80 10.244.2.102***ClusterIP类型的Service它是Kubernetes系统自动分配的虚拟IP缺点只能在集群内部访问创建service-clusterip.yaml文件apiVersion: v1 kind: Service metadata: name: service-clusterip namespace: dev spec: selector: app: nginx-pod clusterIP: 10.97.97.97 # service的ip地址如果不写默认会生成一个 type: ClusterIP ports: - port: 80 # Service端口 targetPort: 80 # pod端口# 创建service [rootmaster k8sYamlForCSDN]# kubectl apply -f service-clusterip.yaml service/service-clusterip created # 查看service [rootmaster k8sYamlForCSDN]# kubectl get svc -n dev -o wide NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE SELECTOR service-clusterip ClusterIP 10.97.97.97 none 80/TCP 17s appnginx-pod # 查看service的详细信息 # 在这里有一个Endpoints列表里面就是当前service可以负载到的服务入口 [rootmaster k8sYamlForCSDN]# kubectl describe svc service-clusterip -n dev Name: service-clusterip Namespace: dev Labels: none Annotations: none Selector: appnginx-pod Type: ClusterIP IP Family Policy: SingleStack IP Families: IPv4 IP: 10.97.97.97 IPs: 10.97.97.97 Port: unset 80/TCP TargetPort: 80/TCP Endpoints: 10.244.1.71:80,10.244.2.101:80,10.244.2.102:80 Session Affinity: None Events: none # 查看ipvs的映射规则 [rootmaster k8sYamlForCSDN]# ipvsadm -Ln IP Virtual Server version 1.2.1 (size4096) Prot LocalAddress:Port Scheduler Flags - RemoteAddress:Port Forward Weight ActiveConn InActConn TCP 10.97.97.97:80 rr - 10.244.1.71:80 Masq 1 0 0 - 10.244.2.101:80 Masq 1 0 0 - 10.244.2.102:80 Masq 1 0 0 # rr-轮询 [rootmaster k8sYamlForCSDN]# curl 10.97.97.97:80 10.244.2.102 [rootmaster k8sYamlForCSDN]# curl 10.97.97.97:80 10.244.2.101 [rootmaster k8sYamlForCSDN]# curl 10.97.97.97:80 10.244.1.71 [rootmaster k8sYamlForCSDN]# curl 10.97.97.97:80 10.244.2.102EndpointEndpoint是kubernetes中的一个资源对象存储在etcd中用来记录一个service对应的所有pod的访问地址它是根据service配置文件中selector描述产生的。一个Service由一组Pod组成这些Pod通过Endpoints暴露出来Endpoints是实现实际服务的端点集合。换句话说service和pod之间的联系是通过endpoints实现的。负载分发策略对Service的访问被分发到了后端的Pod上去目前kubernetes提供了两种负载分发策略如果不定义默认使用kube-proxy的策略比如随机、轮询基于客户端地址的会话保持模式即来自同一个客户端发起的所有请求都会转发到固定的一个Pod上此模式需要在spec中添加sessionAffinity:ClientIP选项# 查看ipvs的映射规则【rr 轮询】 [rootmaster k8sYamlForCSDN]# ipvsadm -Ln IP Virtual Server version 1.2.1 (size4096) Prot LocalAddress:Port Scheduler Flags - RemoteAddress:Port Forward Weight ActiveConn InActConn TCP 10.97.97.97:80 rr - 10.244.1.71:80 Masq 1 0 0 - 10.244.2.101:80 Masq 1 0 0 - 10.244.2.102:80 Masq 1 0 0 # 循环访问测试 [rootmaster k8sYamlForCSDN]# while true;do curl 10.97.97.97:80; sleep 1; done; 10.244.1.71 10.244.2.102 10.244.2.101 10.244.1.71 10.244.2.102 10.244.2.101 # 修改分发策略----sessionAffinity:ClientIP # 查看ipvs规则【persistent 代表持久】 [rootmaster ~]# ipvsadm -Ln [rootmaster k8sYamlForCSDN]# ipvsadm -Ln IP Virtual Server version 1.2.1 (size4096) Prot LocalAddress:Port Scheduler Flags - RemoteAddress:Port Forward Weight ActiveConn InActConn TCP 10.97.97.97:80 rr persistent 10800 - 10.244.1.71:80 Masq 1 0 4 - 10.244.2.101:80 Masq 1 0 4 - 10.244.2.102:80 Masq 1 0 3 # 循环访问测试 [rootmaster k8sYamlForCSDN]# while true;do curl 10.97.97.97:80; sleep 1; done; 10.244.2.102 10.244.2.102 10.244.2.102 10.244.2.102 # 删除service [rootmaster k8sYamlForCSDN]# kubectl delete -f service-clusterip.yaml service service-clusterip deletedHeadLiness类型的ServiceHeadLiness即无头服务在某些场景中开发人员可能不想使用Service提供的负载均衡功能而希望自己来控制负载均衡策略针对这种情况kubernetes提供了HeadLiness Service这类Service不会分配Cluster IP如果想要访问service只能通过service的域名进行查询。创建service-headliness.yamlapiVersion: v1 kind: Service metadata: name: service-headliness namespace: dev spec: selector: app: nginx-pod clusterIP: None # 将clusterIP设置为None即可创建headliness Service type: ClusterIP ports: - port: 80 targetPort: 80# 创建service [rootmaster k8sYamlForCSDN]# kubectl apply -f service-headliness.yaml service/service-headliness created # 获取service 发现CLUSTER-IP未分配 [rootmaster k8sYamlForCSDN]# kubectl get svc service-headliness -n dev NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service-headliness ClusterIP None none 80/TCP 38s # 查看service详情 [rootmaster k8sYamlForCSDN]# kubectl describe svc service-headliness -n dev Name: service-headliness Namespace: dev Labels: none Annotations: none Selector: appnginx-pod Type: ClusterIP IP Family Policy: SingleStack IP Families: IPv4 IP: None IPs: None Port: unset 80/TCP TargetPort: 80/TCP Endpoints: 10.244.1.71:80,10.244.2.101:80,10.244.2.102:80 Session Affinity: None Events: none # 查看域名的解析情况 # 首先查找域名服务器的ip地址 [rootmaster k8sYamlForCSDN]# kubectl exec -it pc-deployment-6d99999569-dxpzt -n dev /bin/sh # cat /etc/resolv.conf nameserver 10.96.0.10 search dev.svc.cluster.local svc.cluster.local cluster.local options ndots:5 # 解析 [rootmaster k8sYamlForCSDN]# dig 10.96.0.10 service-headliness.dev.svc.cluster.local ... ;; ANSWER SECTION: service-headliness.dev.svc.cluster.local. 30 IN A 10.244.2.102 service-headliness.dev.svc.cluster.local. 30 IN A 10.244.1.71 service-headliness.dev.svc.cluster.local. 30 IN A 10.244.2.101 ...***NodePort类型的Service在之前的样例中创建的Service的ip地址只有集群内部才可以访问如果希望将Service暴露给集群外部使用那么就要使用到另外一种类型的Service称为NodePort类型。NodePort的工作原理其实就是将service的端口映射到Node的一个端口上然后就可以通过NodeIp:NodePort来访问service了。创建service-nodeport.yamlapiVersion: v1 kind: Service metadata: name: service-nodeport namespace: dev spec: selector: app: nginx-pod type: NodePort # service类型 ports: - port: 80 nodePort: 6872 # 指定绑定的node的端口(默认的取值范围是30000-32767), 如果不指定会默认分配 targetPort: 80# 创建service [rootmaster k8sYamlForCSDN]# kubectl apply -f service-nodeport.yaml service/service-nodeport created # 查看service [rootmaster k8sYamlForCSDN]# kubectl get svc service-nodeport -n dev NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service-nodeport NodePort 10.99.95.186 none 80:30002/TCP 11s # 接下来可以通过电脑主机的浏览器去访问集群中任意一个nodeip的30002端口即可访问到pod通过NodeIp:NodePort访问会映射到CLUSTER-IP:Port,而CLUSTER-IP:Port又会映射到其中的endpoint里面而我这里集群有3台node实际上就是3台node都开启了NodePort对应的端口。所以不论是100:30002还是101102都可以成功访问192.168.109.100:30002 ---映射到--- 10.99.95.186:80 ---映射算法--- 对应的pod中 192.168.109.101:30002 ---映射到--- 10.99.95.186:80 ---映射算法--- 对应的pod中 192.168.109.102:30002 ---映射到--- 10.99.95.186:80 ---映射算法--- 对应的pod中LoadBalancer类型的ServiceLoadBalancer和NodePort很相似目的都是向外部暴露一个端口区别在于LoadBalancer会在集群的外部再来做一个负载均衡设备而这个设备需要外部环境支持的外部服务发送到这个设备上的请求会被设备负载之后转发到集群中。ExternalName类型的ServiceExternalName类型的Service用于引入集群外部的服务它通过externalName属性指定外部一个服务的地址然后在集群内部访问此service就可以访问到外部的服务了。apiVersion: v1 kind: Service metadata: name: service-externalname namespace: dev spec: type: ExternalName # service类型 externalName: www.baidu.com #改成ip地址也可以# 创建service [rootmaster k8sYamlForCSDN]# kubectl apply -f service-externalname.yaml service/service-externalname created # 查看service [rootmaster k8sYamlForCSDN]# kubectl get svc service-externalname -n dev NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service-externalname ExternalName none www.baidu.com none 34s # 域名解析 [rootmaster k8sYamlForCSDN]# dig 10.96.0.10 service-externalname.dev.svc.cluster.local ...... ;; ANSWER SECTION: service-externalname.dev.svc.cluster.local. 30 IN CNAME www.baidu.com. www.baidu.com. 30 IN CNAME www.a.shifen.com. www.a.shifen.com. 30 IN A 180.101.49.12 www.a.shifen.com. 30 IN A 180.101.49.11......Ingress介绍Service对集群之外暴露服务的主要方式有两种NotePort和LoadBalancer但是这两种方式都有一定的缺点NodePort方式的缺点是会占用很多集群机器的端口那么当集群服务变多的时候这个缺点就愈发明显LB方式的缺点是每个service需要一个LB浪费、麻烦并且需要kubernetes之外设备的支持 基于这种现状kubernetes提供了Ingress资源对象Ingress只需要一个NodePort或者一个LB就可以满足暴露多个Service的需求。工作机制大致如下图表示实际上Ingress相当于一个7层的负载均衡器是kubernetes对反向代理的一个抽象它的工作原理类似于Nginx可以理解成在Ingress里建立诸多映射规则Ingress Controller通过监听这些配置规则并转化成Nginx的反向代理配置 , 然后对外部提供服务。在这里有两个核心概念ingresskubernetes中的一个对象作用是定义请求如何转发到service的规则ingress controller具体实现反向代理及负载均衡的程序对ingress定义的规则进行解析根据配置的规则来实现请求转发实现方式有很多比如Nginx, Contour, Haproxy等等Ingress以Nginx为例的工作原理如下用户编写Ingress规则说明哪个域名对应kubernetes集群中的哪个ServiceIngress控制器动态感知Ingress服务规则的变化然后生成一段对应的Nginx反向代理配置Ingress控制器会将生成的Nginx配置写入到一个运行着的Nginx服务中并动态更新到此为止其实真正在工作的就是一个Nginx了内部配置了用户定义的请求转发规则Ingress使用环境准备搭建ingress环境k8s安装2022新版ingress-nginx详细步骤注意了我们这里没有使用LoadBalancer所以要将上文yaml文件中的type改一下type: LoadBalancer #替换为NodePort type: NodePort# 创建ingress-nginx [rootmaster ingress-controller]# kubectl apply -f ingress-nginx.yaml # 查看ingress-nginx [rootmaster ingress-controller]# kubectl get pods -n ingress-nginx NAME READY STATUS RESTARTS AGE ingress-nginx-admission-create-gvjt4 0/1 Completed 0 16m ingress-nginx-admission-patch-695qk 0/1 Completed 0 16m ingress-nginx-controller-84c544699d-577kf 1/1 Running 0 16m # 查看service [rootmaster ingress-controller]# kubectl get svc -n ingress-nginx NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE ingress-nginx-controller NodePort 10.107.236.215 none 80:31726/TCP,443:31974/TCP 17m ingress-nginx-controller-admission ClusterIP 10.106.83.195 none 443/TCP 17m准备service和pod为了后面的实验比较方便创建如下图所示的模型创建tomcat-nginx.yaml# Deployment控制3个nginx apiVersion: apps/v1 kind: Deployment metadata: name: nginx-deployment namespace: dev spec: replicas: 3 selector: matchLabels: app: nginx-pod template: metadata: labels: app: nginx-pod spec: containers: - name: nginx image: nginx:1.17.1 ports: - containerPort: 80 --- # Deployment控制3个tomcat apiVersion: apps/v1 kind: Deployment metadata: name: tomcat-deployment namespace: dev spec: replicas: 3 selector: matchLabels: app: tomcat-pod template: metadata: labels: app: tomcat-pod spec: containers: - name: tomcat image: tomcat:8.5-jre10-slim ports: - containerPort: 8080 --- # nginx-service关联nginx apiVersion: v1 kind: Service metadata: name: nginx-service namespace: dev spec: selector: app: nginx-pod clusterIP: None type: ClusterIP ports: - port: 80 targetPort: 80 --- # nginx-tomcat关联tomcat apiVersion: v1 kind: Service metadata: name: tomcat-service namespace: dev spec: selector: app: tomcat-pod clusterIP: None type: ClusterIP ports: - port: 8080 targetPort: 8080# 创建 rootmaster k8sYamlForCSDN]# vi tomcat-nginx.yaml [rootmaster k8sYamlForCSDN]# kubectl create ns dev namespace/dev created [rootmaster k8sYamlForCSDN]# kubectl apply -f tomcat-nginx.yaml deployment.apps/nginx-deployment created deployment.apps/tomcat-deployment created service/nginx-service created service/tomcat-service created # 查看 [rootmaster k8sYamlForCSDN]# kubectl get svc -n dev NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE nginx-service ClusterIP None none 80/TCP 36s tomcat-service ClusterIP None none 8080/TCP 36sHttp 代理(ingress-http.yaml)创建ingress-http.yaml注意我们在 Ingress 资源对象中添加了一个 annotationskubernetes.io/ingress.class: “nginx”这就是指定让这个 Ingress 通过 ingress-nginx 来处理如果不添加则不会被ingress控制器所监控到apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: ingress-http namespace: dev annotations: kubernetes.io/ingress.class: nginx spec: rules: - host: nginx.itheima.com # 主机域名ip http: paths: - path: / # 路径 urlhost/path pathType: Prefix backend: service: name: nginx-service # 访问url会转到这个service的80端口上去 port: number: 80 - host: tomcat.itheima.com http: paths: - path: / # 路径 urlhost/path pathType: Prefix backend: service: name: tomcat-service # 访问url会转到这个service的80端口上去 port: number: 8080# 创建 [rootmaster k8sYamlForCSDN]# kubectl apply -f ingress-http.yaml ingress.networking.k8s.io/ingress-http created # 查看 [rootmaster k8sYamlForCSDN]# kubectl get ingress ingress-http -n dev NAME CLASS HOSTS ADDRESS PORTS AGE ingress-http none nginx.itheima.com,tomcat.itheima.com 80 36s # 查看详情 [rootmaster k8sYamlForCSDN]# kubectl get ingress ingress-http -n dev NAME CLASS HOSTS ADDRESS PORTS AGE ingress-http none nginx.itheima.com,tomcat.itheima.com 10.107.236.215 80 16m [rootmaster k8sYamlForCSDN]# kubectl describe ingress ingress-http -n dev Name: ingress-http Labels: none Namespace: dev Address: 10.107.236.215 Default backend: default-http-backend:80 (error: endpoints default-http-backend not found) Rules: Host Path Backends ---- ---- -------- nginx.itheima.com / nginx-service:80 (10.244.1.106:80,10.244.1.107:80,10.244.2.45:80) tomcat.itheima.com / tomcat-service:8080 (10.244.1.108:8080,10.244.2.43:8080,10.244.2.44:8080) Annotations: kubernetes.io/ingress.class: nginx Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Sync 15m (x2 over 16m) nginx-ingress-controller Scheduled for sync [rootmaster k8sYamlForCSDN]# # 接下来,在本地电脑上配置host文件,解析上面的两个域名到192.168.109.100(master)上 # 然后,就可以分别访问tomcat.itheima.com:31726和 nginx.itheima.com:31726查看效果了[rootmaster ingress-controller]# kubectl get pods,svc,ingress -n ingress-nginx NAME READY STATUS RESTARTS AGE pod/ingress-nginx-admission-create-gvjt4 0/1 Completed 0 20m pod/ingress-nginx-admission-patch-695qk 0/1 Completed 0 20m pod/ingress-nginx-controller-84c544699d-577kf 1/1 Running 0 20m NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service/ingress-nginx-controller NodePort 10.107.236.215 none 80:31726/TCP,443:31974/TCP 20m service/ingress-nginx-controller-admission ClusterIP 10.106.83.195 none 443/TCP 20m [rootmaster k8sYamlForCSDN]# kubectl get pods,svc,ingress -n dev NAME READY STATUS RESTARTS AGE pod/nginx-deployment-6756f95949-9zjrd 1/1 Running 0 17m pod/nginx-deployment-6756f95949-k6k7d 1/1 Running 0 17m pod/nginx-deployment-6756f95949-xk9jk 1/1 Running 0 17m pod/tomcat-deployment-76bccfb47c-2gc9j 1/1 Running 0 17m pod/tomcat-deployment-76bccfb47c-5k6lx 1/1 Running 0 17m pod/tomcat-deployment-76bccfb47c-wt7wv 1/1 Running 0 17m NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service/nginx-service ClusterIP None none 80/TCP 17m service/tomcat-service ClusterIP None none 8080/TCP 17m NAME CLASS HOSTS ADDRESS PORTS AGE ingress.networking.k8s.io/ingress-http none nginx.itheima.com,tomcat.itheima.com 10.107.236.215 80 17mHttps代理(ingress-https.yaml)创建证书# 生成证书 openssl req -x509 -sha256 -nodes -days 365 -newkey rsa:2048 -keyout tls.key -out tls.crt -subj /CCN/STBJ/LBJ/Onginx/CNitheima.com # 创建密钥 kubectl create secret tls tls-secret --key tls.key --cert tls.crt创建ingress-https.yamlapiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: ingress-https namespace: dev annotations: kubernetes.io/ingress.class: nginx spec: tls: - hosts: - nginx.itheima.com - tomcat.itheima.com secretName: tls-secret # 指定秘钥 rules: - host: nginx.itheima.com # 主机域名ip http: paths: - path: / # 路径 urlhost/path pathType: backend: service: name: nginx-service # 访问url会转到这个service的80端口上去 port: number: 80 - host: tomcat.itheima.com http: paths: - path: / # 路径 urlhost/path pathType: Prefix backend: service: name: tomcat-service # 访问url会转到这个service的80端口上去 port: number: 8080# 删除验证 [rootmaster k8sYamlForCSDN]#kubectl get validatingwebhookconfigurations ingress-nginx-admission kubectl delete -A ValidatingWebhookConfiguration ingress-nginx-admission # 创建 [rootmaster k8sYamlForCSDN]# kubectl apply -f ingress-https.yaml ingress.networking.k8s.io/ingress-https created # 查看 [rootmaster k8sYamlForCSDN]# kubectl get ing ingress-https -n dev NAME CLASS HOSTS ADDRESS PORTS AGE ingress-https none nginx.itheima.com,tomcat.itheima.com 10.107.236.215 80, 443 98s # 查看详情 [rootmaster k8sYamlForCSDN]# kubectl describe ing ingress-https -n dev Name: ingress-https Labels: none Namespace: dev Address: 10.107.236.215 Default backend: default-http-backend:80 (error: endpoints default-http-backend not found) TLS: tls-secret terminates nginx.itheima.com,tomcat.itheima.com Rules: Host Path Backends ---- ---- -------- nginx.itheima.com / nginx-service:80 (10.244.1.106:80,10.244.1.107:80,10.244.2.45:80) tomcat.itheima.com / tomcat-service:8080 (10.244.1.108:8080,10.244.2.43:8080,10.244.2.44:8080) Annotations: kubernetes.io/ingress.class: nginx Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Sync 103s (x2 over 118s) nginx-ingress-controller Scheduled for sync # 下面可以通过浏览器访问https://nginx.itheima.com:31974和 https://tomcat.itheima.com:31974来查看了 k8s-Service详解（七）
k8s的流量负载组件sevice用于四层路由负载ingress用于七层路由负载Service介绍Service概述在kubernetes中pod是应用程序的载体我们可以通过pod的ip来访问应用程序但是pod的ip地址不是固定的这也就意味着不方便直接采用pod的ip对服务进行访问。为了解决这个问题kubernetes提供了Service资源Service会对提供同一个服务的多个pod进行聚合并且提供一个统一的入口地址。通过访问Service的入口地址就能访问到后面的pod服务。Service在很多情况下只是一个概念真正起作用的其实是kube-proxy服务进程每个Node节点上都运行着一个kube-proxy服务进程。当创建Service的时候会通过api-server向etcd写入创建的service的信息而kube-proxy会基于监听的机制发现这种Service的变动然后它会将最新的Service信息转换成对应的访问规则。# 10.97.97.97:80 是service提供的访问入口 # 当访问这个入口的时候可以发现后面有三个pod的服务在等待调用 # kube-proxy会基于rr轮询的策略(ipvs的前提下)将请求分发到其中一个pod上去 # 这个规则会同时在集群内的所有节点上都生成所以在任何一个节点上访问都可以。 [rootnode1 ~]# ipvsadm -Ln IP Virtual Server version 1.2.1 (size4096) Prot LocalAddress:Port Scheduler Flags - RemoteAddress:Port Forward Weight ActiveConn InActConn TCP 10.97.97.97:80 rr - 10.244.1.39:80 Masq 1 0 0 - 10.244.1.40:80 Masq 1 0 0 - 10.244.2.33:80 Masq 1 0 0kube-proxy目前支持三种工作模式:userspace 模式userspace模式下kube-proxy会为每一个Service创建一个监听端口发向Cluster IP的请求被Iptables规则重定向 到kube-proxy监听的端口上kube-proxy根据LB算法选择一个提供服务的Pod并和其建立链接以将请求转发到Pod上。该模式下kube-proxy充当了一个四层负责均衡器的角色。由于kube-proxy运行在userspace中在进行转发处理时会增加内核和用户空间之间的数据拷贝虽然比较稳定但是效率比较低iptables 模式iptables模式下kube-proxy为service后端的每个Pod创建对应的iptables规则直接将发向Cluster IP的请求重定向到一个Pod IP。该模式下kube-proxy不承担四层负责均衡器的角色只负责创建iptables规则。该模式的优点是较userspace模式效率更高但不能提供灵活的LB策略当后端Pod不可用时也无法进行重试。ipvs 模式ipvs模式和iptables类 似kube-proxy监控Pod的变化并创建相应的ipvs规则。ipvs相对iptables转发效率更高。除此以外ipvs支持更多的LB算法。# 此模式必须安装ipvs内核模块否则会降级为iptables # 开启ipvs [rootmaster modules]# ipvsadm -Ln IP Virtual Server version 1.2.1 (size4096) Prot LocalAddress:Port Scheduler Flags - RemoteAddress:Port Forward Weight ActiveConn InActConn # mode模式改成ipvs--modeipvs [rootmaster modules]# kubectl edit cm kube-proxy -n kube-system configmap/kube-proxy edited # 等待自动重建 [rootmaster modules]# kubectl delete pod -l k8s-appkube-proxy -n kube-system pod kube-proxy-vxflz deleted pod kube-proxy-w886d deleted pod kube-proxy-xb7kp deleted [rootmaster modules]# ipvsadm -Ln IP Virtual Server version 1.2.1 (size4096) Prot LocalAddress:Port Scheduler Flags - RemoteAddress:Port Forward Weight ActiveConn InActConn TCP 10.96.0.1:443 rr - 192.168.109.100:6443 Masq 1 0 0 TCP 10.96.0.10:53 rr - 10.244.0.2:53 Masq 1 0 0 - 10.244.0.3:53 Masq 1 0 0 TCP 10.96.0.10:9153 rr - 10.244.0.2:9153 Masq 1 0 0 - 10.244.0.3:9153 Masq 1 0 0 TCP 10.110.157.232:443 rr - 192.168.109.101:4443 Masq 1 0 0 UDP 10.96.0.10:53 rr - 10.244.0.2:53 Masq 1 0 0 - 10.244.0.3:53 Masq 1 0 0Service类型Service的资源清单文件kind: Service # 资源类型 apiVersion: v1 # 资源版本 metadata: # 元数据 name: service # 资源名称 namespace: dev # 命名空间 spec: # 描述 selector: # 标签选择器用于确定当前service代理哪些pod(通过标签获取对应ip存入ipvs) app: nginx type: # Service类型指定service的访问方式 clusterIP: # 虚拟服务的ip地址 sessionAffinity: # session亲和性支持ClientIP、None两个选项同一个请求ip到同一个pod ports: # 端口信息 - protocol: TCP port: 3017 # service端口 targetPort: 5003 # pod端口 nodePort: 31122 # 主机端口# type: Service类型指定service的访问方式 - ClusterIP默认值它是Kubernetes系统自动分配的虚拟IP只能在集群内部访问 - NodePort将Service通过指定的Node上的端口暴露给外部通过此方法就可以在集群外部访问服务 - LoadBalancer使用外接负载均衡器完成到服务的负载分发注意此模式需要外部云环境支持 - ExternalName 把集群外部的服务引入集群内部直接使用Service使用实验环境准备在使用service之前首先利用Deployment创建出3个pod注意要为pod设置appnginx-pod的标签创建deployment.yaml内容如下apiVersion: apps/v1 kind: Deployment metadata: name: pc-deployment namespace: dev spec: replicas: 3 selector: matchLabels: app: nginx-pod template: metadata: labels: app: nginx-pod spec: containers: - name: nginx image: nginx ports: - containerPort: 80# 创建deploy [rootmaster k8sYamlForCSDN]# kubectl apply -f deployment.yaml deployment.apps/pc-deployment created # 查看pod详情 [rootmaster k8sYamlForCSDN]# kubectl get pods -n dev -o wide --show-labels NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES LABELS pc-deployment-6d99999569-dxpzt 1/1 Running 0 40s 10.244.2.101 node2 none none appnginx-pod,pod-template-hash6d99999569 pc-deployment-6d99999569-m69zc 1/1 Running 0 40s 10.244.1.71 node1 none none appnginx-pod,pod-template-hash6d99999569 pc-deployment-6d99999569-wk9nz 1/1 Running 0 40s 10.244.2.102 node2 none none appnginx-pod,pod-template-hash6d99999569 # 为了方便后面的测试修改下三台nginx的index.html页面三台修改的IP地址不一致 # kubectl exec -it pc-deployment-6d99999569-dxpzt -n dev /bin/sh # echo 10.244.2.101 /usr/share/nginx/html/index.html # kubectl exec -it pc-deployment-6d99999569-m69zc -n dev /bin/sh # echo 10.244.1.71 /usr/share/nginx/html/index.html # kubectl exec -it pc-deployment-6d99999569-wk9nz -n dev /bin/sh # echo 10.244.2.102 /usr/share/nginx/html/index.html # 修改完毕之后访问测试 [rootmaster k8sYamlForCSDN]# curl 10.244.2.101:80 10.244.2.101 [rootmaster k8sYamlForCSDN]# curl 10.244.1.71:80 10.244.1.71 [rootmaster k8sYamlForCSDN]# curl 10.244.2.102:80 10.244.2.102***ClusterIP类型的Service它是Kubernetes系统自动分配的虚拟IP缺点只能在集群内部访问创建service-clusterip.yaml文件apiVersion: v1 kind: Service metadata: name: service-clusterip namespace: dev spec: selector: app: nginx-pod clusterIP: 10.97.97.97 # service的ip地址如果不写默认会生成一个 type: ClusterIP ports: - port: 80 # Service端口 targetPort: 80 # pod端口# 创建service [rootmaster k8sYamlForCSDN]# kubectl apply -f service-clusterip.yaml service/service-clusterip created # 查看service [rootmaster k8sYamlForCSDN]# kubectl get svc -n dev -o wide NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE SELECTOR service-clusterip ClusterIP 10.97.97.97 none 80/TCP 17s appnginx-pod # 查看service的详细信息 # 在这里有一个Endpoints列表里面就是当前service可以负载到的服务入口 [rootmaster k8sYamlForCSDN]# kubectl describe svc service-clusterip -n dev Name: service-clusterip Namespace: dev Labels: none Annotations: none Selector: appnginx-pod Type: ClusterIP IP Family Policy: SingleStack IP Families: IPv4 IP: 10.97.97.97 IPs: 10.97.97.97 Port: unset 80/TCP TargetPort: 80/TCP Endpoints: 10.244.1.71:80,10.244.2.101:80,10.244.2.102:80 Session Affinity: None Events: none # 查看ipvs的映射规则 [rootmaster k8sYamlForCSDN]# ipvsadm -Ln IP Virtual Server version 1.2.1 (size4096) Prot LocalAddress:Port Scheduler Flags - RemoteAddress:Port Forward Weight ActiveConn InActConn TCP 10.97.97.97:80 rr - 10.244.1.71:80 Masq 1 0 0 - 10.244.2.101:80 Masq 1 0 0 - 10.244.2.102:80 Masq 1 0 0 # rr-轮询 [rootmaster k8sYamlForCSDN]# curl 10.97.97.97:80 10.244.2.102 [rootmaster k8sYamlForCSDN]# curl 10.97.97.97:80 10.244.2.101 [rootmaster k8sYamlForCSDN]# curl 10.97.97.97:80 10.244.1.71 [rootmaster k8sYamlForCSDN]# curl 10.97.97.97:80 10.244.2.102EndpointEndpoint是kubernetes中的一个资源对象存储在etcd中用来记录一个service对应的所有pod的访问地址它是根据service配置文件中selector描述产生的。一个Service由一组Pod组成这些Pod通过Endpoints暴露出来Endpoints是实现实际服务的端点集合。换句话说service和pod之间的联系是通过endpoints实现的。负载分发策略对Service的访问被分发到了后端的Pod上去目前kubernetes提供了两种负载分发策略如果不定义默认使用kube-proxy的策略比如随机、轮询基于客户端地址的会话保持模式即来自同一个客户端发起的所有请求都会转发到固定的一个Pod上此模式需要在spec中添加sessionAffinity:ClientIP选项# 查看ipvs的映射规则【rr 轮询】 [rootmaster k8sYamlForCSDN]# ipvsadm -Ln IP Virtual Server version 1.2.1 (size4096) Prot LocalAddress:Port Scheduler Flags - RemoteAddress:Port Forward Weight ActiveConn InActConn TCP 10.97.97.97:80 rr - 10.244.1.71:80 Masq 1 0 0 - 10.244.2.101:80 Masq 1 0 0 - 10.244.2.102:80 Masq 1 0 0 # 循环访问测试 [rootmaster k8sYamlForCSDN]# while true;do curl 10.97.97.97:80; sleep 1; done; 10.244.1.71 10.244.2.102 10.244.2.101 10.244.1.71 10.244.2.102 10.244.2.101 # 修改分发策略----sessionAffinity:ClientIP # 查看ipvs规则【persistent 代表持久】 [rootmaster ~]# ipvsadm -Ln [rootmaster k8sYamlForCSDN]# ipvsadm -Ln IP Virtual Server version 1.2.1 (size4096) Prot LocalAddress:Port Scheduler Flags - RemoteAddress:Port Forward Weight ActiveConn InActConn TCP 10.97.97.97:80 rr persistent 10800 - 10.244.1.71:80 Masq 1 0 4 - 10.244.2.101:80 Masq 1 0 4 - 10.244.2.102:80 Masq 1 0 3 # 循环访问测试 [rootmaster k8sYamlForCSDN]# while true;do curl 10.97.97.97:80; sleep 1; done; 10.244.2.102 10.244.2.102 10.244.2.102 10.244.2.102 # 删除service [rootmaster k8sYamlForCSDN]# kubectl delete -f service-clusterip.yaml service service-clusterip deletedHeadLiness类型的ServiceHeadLiness即无头服务在某些场景中开发人员可能不想使用Service提供的负载均衡功能而希望自己来控制负载均衡策略针对这种情况kubernetes提供了HeadLiness Service这类Service不会分配Cluster IP如果想要访问service只能通过service的域名进行查询。创建service-headliness.yamlapiVersion: v1 kind: Service metadata: name: service-headliness namespace: dev spec: selector: app: nginx-pod clusterIP: None # 将clusterIP设置为None即可创建headliness Service type: ClusterIP ports: - port: 80 targetPort: 80# 创建service [rootmaster k8sYamlForCSDN]# kubectl apply -f service-headliness.yaml service/service-headliness created # 获取service 发现CLUSTER-IP未分配 [rootmaster k8sYamlForCSDN]# kubectl get svc service-headliness -n dev NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service-headliness ClusterIP None none 80/TCP 38s # 查看service详情 [rootmaster k8sYamlForCSDN]# kubectl describe svc service-headliness -n dev Name: service-headliness Namespace: dev Labels: none Annotations: none Selector: appnginx-pod Type: ClusterIP IP Family Policy: SingleStack IP Families: IPv4 IP: None IPs: None Port: unset 80/TCP TargetPort: 80/TCP Endpoints: 10.244.1.71:80,10.244.2.101:80,10.244.2.102:80 Session Affinity: None Events: none # 查看域名的解析情况 # 首先查找域名服务器的ip地址 [rootmaster k8sYamlForCSDN]# kubectl exec -it pc-deployment-6d99999569-dxpzt -n dev /bin/sh # cat /etc/resolv.conf nameserver 10.96.0.10 search dev.svc.cluster.local svc.cluster.local cluster.local options ndots:5 # 解析 [rootmaster k8sYamlForCSDN]# dig 10.96.0.10 service-headliness.dev.svc.cluster.local ... ;; ANSWER SECTION: service-headliness.dev.svc.cluster.local. 30 IN A 10.244.2.102 service-headliness.dev.svc.cluster.local. 30 IN A 10.244.1.71 service-headliness.dev.svc.cluster.local. 30 IN A 10.244.2.101 ...***NodePort类型的Service在之前的样例中创建的Service的ip地址只有集群内部才可以访问如果希望将Service暴露给集群外部使用那么就要使用到另外一种类型的Service称为NodePort类型。NodePort的工作原理其实就是将service的端口映射到Node的一个端口上然后就可以通过NodeIp:NodePort来访问service了。创建service-nodeport.yamlapiVersion: v1 kind: Service metadata: name: service-nodeport namespace: dev spec: selector: app: nginx-pod type: NodePort # service类型 ports: - port: 80 nodePort: 6872 # 指定绑定的node的端口(默认的取值范围是30000-32767), 如果不指定会默认分配 targetPort: 80# 创建service [rootmaster k8sYamlForCSDN]# kubectl apply -f service-nodeport.yaml service/service-nodeport created # 查看service [rootmaster k8sYamlForCSDN]# kubectl get svc service-nodeport -n dev NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service-nodeport NodePort 10.99.95.186 none 80:30002/TCP 11s # 接下来可以通过电脑主机的浏览器去访问集群中任意一个nodeip的30002端口即可访问到pod通过NodeIp:NodePort访问会映射到CLUSTER-IP:Port,而CLUSTER-IP:Port又会映射到其中的endpoint里面而我这里集群有3台node实际上就是3台node都开启了NodePort对应的端口。所以不论是100:30002还是101102都可以成功访问192.168.109.100:30002 ---映射到--- 10.99.95.186:80 ---映射算法--- 对应的pod中 192.168.109.101:30002 ---映射到--- 10.99.95.186:80 ---映射算法--- 对应的pod中 192.168.109.102:30002 ---映射到--- 10.99.95.186:80 ---映射算法--- 对应的pod中LoadBalancer类型的ServiceLoadBalancer和NodePort很相似目的都是向外部暴露一个端口区别在于LoadBalancer会在集群的外部再来做一个负载均衡设备而这个设备需要外部环境支持的外部服务发送到这个设备上的请求会被设备负载之后转发到集群中。ExternalName类型的ServiceExternalName类型的Service用于引入集群外部的服务它通过externalName属性指定外部一个服务的地址然后在集群内部访问此service就可以访问到外部的服务了。apiVersion: v1 kind: Service metadata: name: service-externalname namespace: dev spec: type: ExternalName # service类型 externalName: www.baidu.com #改成ip地址也可以# 创建service [rootmaster k8sYamlForCSDN]# kubectl apply -f service-externalname.yaml service/service-externalname created # 查看service [rootmaster k8sYamlForCSDN]# kubectl get svc service-externalname -n dev NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service-externalname ExternalName none www.baidu.com none 34s # 域名解析 [rootmaster k8sYamlForCSDN]# dig 10.96.0.10 service-externalname.dev.svc.cluster.local ...... ;; ANSWER SECTION: service-externalname.dev.svc.cluster.local. 30 IN CNAME www.baidu.com. www.baidu.com. 30 IN CNAME www.a.shifen.com. www.a.shifen.com. 30 IN A 180.101.49.12 www.a.shifen.com. 30 IN A 180.101.49.11......Ingress介绍Service对集群之外暴露服务的主要方式有两种NotePort和LoadBalancer但是这两种方式都有一定的缺点NodePort方式的缺点是会占用很多集群机器的端口那么当集群服务变多的时候这个缺点就愈发明显LB方式的缺点是每个service需要一个LB浪费、麻烦并且需要kubernetes之外设备的支持 基于这种现状kubernetes提供了Ingress资源对象Ingress只需要一个NodePort或者一个LB就可以满足暴露多个Service的需求。工作机制大致如下图表示实际上Ingress相当于一个7层的负载均衡器是kubernetes对反向代理的一个抽象它的工作原理类似于Nginx可以理解成在Ingress里建立诸多映射规则Ingress Controller通过监听这些配置规则并转化成Nginx的反向代理配置 , 然后对外部提供服务。在这里有两个核心概念ingresskubernetes中的一个对象作用是定义请求如何转发到service的规则ingress controller具体实现反向代理及负载均衡的程序对ingress定义的规则进行解析根据配置的规则来实现请求转发实现方式有很多比如Nginx, Contour, Haproxy等等Ingress以Nginx为例的工作原理如下用户编写Ingress规则说明哪个域名对应kubernetes集群中的哪个ServiceIngress控制器动态感知Ingress服务规则的变化然后生成一段对应的Nginx反向代理配置Ingress控制器会将生成的Nginx配置写入到一个运行着的Nginx服务中并动态更新到此为止其实真正在工作的就是一个Nginx了内部配置了用户定义的请求转发规则Ingress使用环境准备搭建ingress环境k8s安装2022新版ingress-nginx详细步骤注意了我们这里没有使用LoadBalancer所以要将上文yaml文件中的type改一下type: LoadBalancer #替换为NodePort type: NodePort# 创建ingress-nginx [rootmaster ingress-controller]# kubectl apply -f ingress-nginx.yaml # 查看ingress-nginx [rootmaster ingress-controller]# kubectl get pods -n ingress-nginx NAME READY STATUS RESTARTS AGE ingress-nginx-admission-create-gvjt4 0/1 Completed 0 16m ingress-nginx-admission-patch-695qk 0/1 Completed 0 16m ingress-nginx-controller-84c544699d-577kf 1/1 Running 0 16m # 查看service [rootmaster ingress-controller]# kubectl get svc -n ingress-nginx NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE ingress-nginx-controller NodePort 10.107.236.215 none 80:31726/TCP,443:31974/TCP 17m ingress-nginx-controller-admission ClusterIP 10.106.83.195 none 443/TCP 17m准备service和pod为了后面的实验比较方便创建如下图所示的模型创建tomcat-nginx.yaml# Deployment控制3个nginx apiVersion: apps/v1 kind: Deployment metadata: name: nginx-deployment namespace: dev spec: replicas: 3 selector: matchLabels: app: nginx-pod template: metadata: labels: app: nginx-pod spec: containers: - name: nginx image: nginx:1.17.1 ports: - containerPort: 80 --- # Deployment控制3个tomcat apiVersion: apps/v1 kind: Deployment metadata: name: tomcat-deployment namespace: dev spec: replicas: 3 selector: matchLabels: app: tomcat-pod template: metadata: labels: app: tomcat-pod spec: containers: - name: tomcat image: tomcat:8.5-jre10-slim ports: - containerPort: 8080 --- # nginx-service关联nginx apiVersion: v1 kind: Service metadata: name: nginx-service namespace: dev spec: selector: app: nginx-pod clusterIP: None type: ClusterIP ports: - port: 80 targetPort: 80 --- # nginx-tomcat关联tomcat apiVersion: v1 kind: Service metadata: name: tomcat-service namespace: dev spec: selector: app: tomcat-pod clusterIP: None type: ClusterIP ports: - port: 8080 targetPort: 8080# 创建 rootmaster k8sYamlForCSDN]# vi tomcat-nginx.yaml [rootmaster k8sYamlForCSDN]# kubectl create ns dev namespace/dev created [rootmaster k8sYamlForCSDN]# kubectl apply -f tomcat-nginx.yaml deployment.apps/nginx-deployment created deployment.apps/tomcat-deployment created service/nginx-service created service/tomcat-service created # 查看 [rootmaster k8sYamlForCSDN]# kubectl get svc -n dev NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE nginx-service ClusterIP None none 80/TCP 36s tomcat-service ClusterIP None none 8080/TCP 36sHttp 代理(ingress-http.yaml)创建ingress-http.yaml注意我们在 Ingress 资源对象中添加了一个 annotationskubernetes.io/ingress.class: “nginx”这就是指定让这个 Ingress 通过 ingress-nginx 来处理如果不添加则不会被ingress控制器所监控到apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: ingress-http namespace: dev annotations: kubernetes.io/ingress.class: nginx spec: rules: - host: nginx.itheima.com # 主机域名ip http: paths: - path: / # 路径 urlhost/path pathType: Prefix backend: service: name: nginx-service # 访问url会转到这个service的80端口上去 port: number: 80 - host: tomcat.itheima.com http: paths: - path: / # 路径 urlhost/path pathType: Prefix backend: service: name: tomcat-service # 访问url会转到这个service的80端口上去 port: number: 8080# 创建 [rootmaster k8sYamlForCSDN]# kubectl apply -f ingress-http.yaml ingress.networking.k8s.io/ingress-http created # 查看 [rootmaster k8sYamlForCSDN]# kubectl get ingress ingress-http -n dev NAME CLASS HOSTS ADDRESS PORTS AGE ingress-http none nginx.itheima.com,tomcat.itheima.com 80 36s # 查看详情 [rootmaster k8sYamlForCSDN]# kubectl get ingress ingress-http -n dev NAME CLASS HOSTS ADDRESS PORTS AGE ingress-http none nginx.itheima.com,tomcat.itheima.com 10.107.236.215 80 16m [rootmaster k8sYamlForCSDN]# kubectl describe ingress ingress-http -n dev Name: ingress-http Labels: none Namespace: dev Address: 10.107.236.215 Default backend: default-http-backend:80 (error: endpoints default-http-backend not found) Rules: Host Path Backends ---- ---- -------- nginx.itheima.com / nginx-service:80 (10.244.1.106:80,10.244.1.107:80,10.244.2.45:80) tomcat.itheima.com / tomcat-service:8080 (10.244.1.108:8080,10.244.2.43:8080,10.244.2.44:8080) Annotations: kubernetes.io/ingress.class: nginx Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Sync 15m (x2 over 16m) nginx-ingress-controller Scheduled for sync [rootmaster k8sYamlForCSDN]# # 接下来,在本地电脑上配置host文件,解析上面的两个域名到192.168.109.100(master)上 # 然后,就可以分别访问tomcat.itheima.com:31726和 nginx.itheima.com:31726查看效果了[rootmaster ingress-controller]# kubectl get pods,svc,ingress -n ingress-nginx NAME READY STATUS RESTARTS AGE pod/ingress-nginx-admission-create-gvjt4 0/1 Completed 0 20m pod/ingress-nginx-admission-patch-695qk 0/1 Completed 0 20m pod/ingress-nginx-controller-84c544699d-577kf 1/1 Running 0 20m NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service/ingress-nginx-controller NodePort 10.107.236.215 none 80:31726/TCP,443:31974/TCP 20m service/ingress-nginx-controller-admission ClusterIP 10.106.83.195 none 443/TCP 20m [rootmaster k8sYamlForCSDN]# kubectl get pods,svc,ingress -n dev NAME READY STATUS RESTARTS AGE pod/nginx-deployment-6756f95949-9zjrd 1/1 Running 0 17m pod/nginx-deployment-6756f95949-k6k7d 1/1 Running 0 17m pod/nginx-deployment-6756f95949-xk9jk 1/1 Running 0 17m pod/tomcat-deployment-76bccfb47c-2gc9j 1/1 Running 0 17m pod/tomcat-deployment-76bccfb47c-5k6lx 1/1 Running 0 17m pod/tomcat-deployment-76bccfb47c-wt7wv 1/1 Running 0 17m NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service/nginx-service ClusterIP None none 80/TCP 17m service/tomcat-service ClusterIP None none 8080/TCP 17m NAME CLASS HOSTS ADDRESS PORTS AGE ingress.networking.k8s.io/ingress-http none nginx.itheima.com,tomcat.itheima.com 10.107.236.215 80 17mHttps代理(ingress-https.yaml)创建证书# 生成证书 openssl req -x509 -sha256 -nodes -days 365 -newkey rsa:2048 -keyout tls.key -out tls.crt -subj /CCN/STBJ/LBJ/Onginx/CNitheima.com # 创建密钥 kubectl create secret tls tls-secret --key tls.key --cert tls.crt创建ingress-https.yamlapiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: ingress-https namespace: dev annotations: kubernetes.io/ingress.class: nginx spec: tls: - hosts: - nginx.itheima.com - tomcat.itheima.com secretName: tls-secret # 指定秘钥 rules: - host: nginx.itheima.com # 主机域名ip http: paths: - path: / # 路径 urlhost/path pathType: backend: service: name: nginx-service # 访问url会转到这个service的80端口上去 port: number: 80 - host: tomcat.itheima.com http: paths: - path: / # 路径 urlhost/path pathType: Prefix backend: service: name: tomcat-service # 访问url会转到这个service的80端口上去 port: number: 8080# 删除验证 [rootmaster k8sYamlForCSDN]#kubectl get validatingwebhookconfigurations ingress-nginx-admission kubectl delete -A ValidatingWebhookConfiguration ingress-nginx-admission # 创建 [rootmaster k8sYamlForCSDN]# kubectl apply -f ingress-https.yaml ingress.networking.k8s.io/ingress-https created # 查看 [rootmaster k8sYamlForCSDN]# kubectl get ing ingress-https -n dev NAME CLASS HOSTS ADDRESS PORTS AGE ingress-https none nginx.itheima.com,tomcat.itheima.com 10.107.236.215 80, 443 98s # 查看详情 [rootmaster k8sYamlForCSDN]# kubectl describe ing ingress-https -n dev Name: ingress-https Labels: none Namespace: dev Address: 10.107.236.215 Default backend: default-http-backend:80 (error: endpoints default-http-backend not found) TLS: tls-secret terminates nginx.itheima.com,tomcat.itheima.com Rules: Host Path Backends ---- ---- -------- nginx.itheima.com / nginx-service:80 (10.244.1.106:80,10.244.1.107:80,10.244.2.45:80) tomcat.itheima.com / tomcat-service:8080 (10.244.1.108:8080,10.244.2.43:8080,10.244.2.44:8080) Annotations: kubernetes.io/ingress.class: nginx Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Sync 103s (x2 over 118s) nginx-ingress-controller Scheduled for sync # 下面可以通过浏览器访问https://nginx.itheima.com:31974和 https://tomcat.itheima.com:31974来查看了