1、service详解
1.1 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(轮询)的策略,将请求分发到其中一个pod上去
# 这个规则会同时在集群内的所有节点上都生成,所以在任何一个节点上访问都可以。
[root@node1 ~]# ipvsadm -Ln
IP Virtual Server version 1.2.1 (size=4096)
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 0
kube-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
[root@k8smaster ~]# yum install ipvsadm
# 此模式必须安装ipvs内核模块,否则会降级为iptables
# 开启ipvs 修改mode: "ipvs"
[root@k8smaster ~]# kubectl edit cm kube-proxy -n kube-system
configmap/kube-proxy edited
[root@k8smaster ~]# kubectl delete pod -l k8s-app=kube-proxy -n kube-system
pod "kube-proxy-9gpj9" deleted
pod "kube-proxy-jv67d" deleted
pod "kube-proxy-k97jk" deleted
[root@k8smaster ~]# 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:32759 rr
TCP 192.168.12.131:30149 rr
TCP 192.168.12.131:32759 rr
TCP 10.96.0.1:443 rr
-> 192.168.12.131:6443 Masq 1 0 0
TCP 10.96.0.10:53 rr
-> 10.244.0.10:53 Masq 1 0 0
-> 10.244.0.11:53 Masq 1 0 0
TCP 10.96.0.10:9153 rr
-> 10.244.0.10:9153 Masq 1 0 0
-> 10.244.0.11:9153 Masq 1 0 0
TCP 10.97.148.108:8000 rr
-> 10.244.0.12:8000 Masq 1 0 0
TCP 10.97.225.71:443 rr
-> 10.244.0.13:8443 Masq 1 0 0
TCP 10.104.14.192:80 rr
TCP 10.104.106.225:443 rr
-> 192.168.12.133:443 Masq 1 0 0
TCP 10.104.191.140:80 rr
TCP 10.244.0.0:30149 rr
TCP 10.244.0.0:32759 rr
TCP 10.244.0.1:30149 rr
TCP 10.244.0.1:32759 rr
TCP 127.0.0.1:30149 rr
TCP 127.0.0.1:32759 rr
TCP 172.17.0.1:30149 rr
UDP 10.96.0.10:53 rr
-> 10.244.0.10:53 Masq 1 0 0
-> 10.244.0.11:53 Masq 1 0 0
1.2 Service类型
Service的资源清单文件:
kind: Service # 资源类型
apiVersion: v1 # 资源版本
metadata: # 元数据
name: service # 资源名称
namespace: dev # 命名空间
spec: # 描述
selector: # 标签选择器,用于确定当前service代理哪些pod
app: nginx
type: # Service类型,指定service的访问方式
clusterIP: # 虚拟服务的ip地址
sessionAffinity: # session亲和性,支持ClientIP、None两个选项(如同一个客户端到同一个pod)
ports: # 端口信息
- protocol: TCP
port: 3017 # service端口
targetPort: 5003 # pod端口
nodePort: 31122 # 主机端口
service的type:
- ClusterIP:默认值,它是Kubernetes系统自动分配的虚拟IP,只能在集群内部访问
- NodePort:将Service通过指定的Node上的端口暴露给外部,通过此方法,就可以在集群外部访问服务
- LoadBalancer:使用外接负载均衡器完成到服务的负载分发,注意此模式需要外部云环境支持
- ExternalName: 把集群外部的服务引入集群内部,直接使用
1.3 service的使用
1)实验环境准备
在使用service之前,首先利用Deployment创建出3个pod,注意要为pod设置app=nginx-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:1.17.1
ports:
- containerPort: 80
[root@k8smaster k8s]# kubectl create -f deployment.yaml
deployment.apps/pc-deployment created
# 查看pod详情
[root@k8smaster k8s]# kubectl get pod -n dev -o wide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
pc-deployment-7d7dd5499b-bcxbp 1/1 Running 0 48s 10.244.1.43 k8snode2 <none> <none>
pc-deployment-7d7dd5499b-cpnqs 1/1 Running 0 48s 10.244.1.42 k8snode2 <none> <none>
pc-deployment-7d7dd5499b-k2nhj 1/1 Running 0 48s 10.244.2.85 k8snode1 <none> <none>
# 为了方便后面的测试,修改下三台nginx的index.html页面(三台修改的IP地址不一致)
# kubectl exec -it pc-deployment-7d7dd5499b-bcxbp -n dev /bin/sh
# echo "10.244.1.43" > /usr/share/nginx/html/index.html
#修改完毕之后,访问测试
[root@k8smaster k8s]# curl 10.244.1.43
10.244.1.43
[root@k8smaster k8s]# curl 10.244.1.42
10.244.1.42
[root@k8smaster k8s]# curl 10.244.2.85
10.244.2.85
2)ClusterIP类型的Service
创建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
[root@k8smaster k8s]# kubectl create -f service-clusterip.yaml
service/service-clusterip created
# 查看service
[root@k8smaster k8s]# 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 61s app=nginx-pod
# 查看service的详细信息
# 在这里有一个Endpoints列表,里面就是当前service可以负载到的服务入口
[root@k8smaster k8s]# kubectl describe svc service-clusterip -n dev
Name: service-clusterip
Namespace: dev
Labels: <none>
Annotations: <none>
Selector: app=nginx-pod
Type: ClusterIP
IP: 10.97.97.97
Port: <unset> 80/TCP
TargetPort: 80/TCP
Endpoints: 10.244.1.42:80,10.244.1.43:80,10.244.2.85:80
Session Affinity: None
Events: <none>
# 查看ipvs的映射规则
[root@k8smaster k8s]# ipvsadm -Ln
TCP 10.97.97.97:80 rr
-> 10.244.1.42:80 Masq 1 0 0
-> 10.244.1.43:80 Masq 1 0 0
-> 10.244.2.85:80 Masq 1 0 0
# 访问10.97.97.97:80观察效果
[root@k8smaster k8s]# curl 10.97.97.97:80
10.244.2.85
Endpoint
Endpoint是kubernetes中的一个资源对象,存储在etcd中,用来记录一个service对应的所有pod的访问地址,它是根据service配置文件中selector描述产生的。
一个Service由一组Pod组成,这些Pod通过Endpoints暴露出来,Endpoints是实现实际服务的端点集合。换句话说,service和pod之间的联系是通过endpoints实现的。
[root@k8smaster k8s]# kubectl get endpoints -n dev
NAME ENDPOINTS AGE
service-clusterip 10.244.1.42:80,10.244.1.43:80,10.244.2.85:80 6m13s
负载分发策略
对Service的访问被分发到了后端的Pod上去,目前kubernetes提供了两种负载分发策略:
- 如果不定义,默认使用kube-proxy的策略,比如随机、轮询
- 基于客户端地址的会话保持模式,即来自同一个客户端发起的所有请求都会转发到固定的一个Pod上此模式可以使在spec中添加sessionAffinity:ClientIP选项
# 查看ipvs的映射规则【rr 轮询】
[root@k8smaster k8s]# ipvsadm -Ln
TCP 10.97.97.97:80 rr
-> 10.244.1.42:80 Masq 1 0 0
-> 10.244.1.43:80 Masq 1 0 0
-> 10.244.2.85:80 Masq 1 0
# 循环访问测试
[root@k8smaster k8s]# while true;do curl 10.97.97.97:80; sleep 5; done;
10.244.2.85
10.244.1.42
10.244.1.43
10.244.2.85
10.244.1.42
10.244.1.43
# 修改分发策略----sessionAffinity:ClientIP
# 查看ipvs规则【persistent 代表持久】
[root@k8smaster k8s]# ipvsadm -Ln
TCP 10.97.97.97:80 rr persistent 10800
-> 10.244.1.42:80 Masq 1 0 0
-> 10.244.1.43:80 Masq 1 0 0
-> 10.244.2.85:80 Masq 1 0 1
# 循环访问测试
[root@k8smaster ~]# while true;do curl 10.97.97.97; sleep 5; done;
10.244.2.85
10.244.2.85
# 删除service
[root@k8smaster k8s]# kubectl delete -f service-clusterip.yaml
service "service-clusterip" deleted
3)HeadLiness类型的Service
在某些场景中,开发人员可能不想使用Service提供的负载均衡功能,而希望自己来控制负载均衡策略,针对这种情况,kubernetes提供了HeadLiness Service,这类Service不会分配Cluster IP,如果想要访问service,只能通过service的域名进行查询。
创建service-headliness.yaml
apiVersion: 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
[root@k8smaster k8s]# kubectl create -f service-headliness.yaml
service/service-headliness created
# 获取service, 发现CLUSTER-IP未分配
[root@k8smaster k8s]# kubectl get svc service-headliness -n dev -o wide
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE SELECTOR
service-headliness ClusterIP None <none> 80/TCP 33s app=nginx-pod
# 查看service详情
[root@k8smaster k8s]# kubectl describe svc service-headliness -n dev
Name: service-headliness
Namespace: dev
Labels: <none>
Annotations: <none>
Selector: app=nginx-pod
Type: ClusterIP
IP: None
Port: <unset> 80/TCP
TargetPort: 80/TCP
Endpoints: 10.244.1.42:80,10.244.1.43:80,10.244.2.85:80
Session Affinity: None
Events: <none>
[root@k8smaster k8s]# kubectl get pods -n dev
NAME READY STATUS RESTARTS AGE
pc-deployment-7d7dd5499b-bcxbp 1/1 Running 0 111m
pc-deployment-7d7dd5499b-cpnqs 1/1 Running 0 111m
pc-deployment-7d7dd5499b-k2nhj 1/1 Running 0 111m
# 查看域名的解析情况
[root@k8smaster k8s]# kubectl exec -it pc-deployment-7d7dd5499b-bcxbp -n dev /bin/sh
kubectl exec [POD] [COMMAND] is DEPRECATED and will be removed in a future version. Use kubectl kubectl exec [POD] -- [COMMAND] instead.
# cat /etc/resolv.conf
nameserver 10.96.0.10
search dev.svc.cluster.local svc.cluster.local cluster.local
options ndots:5
# 安装dig命令
[root@k8smaster k8s]# yum -y install bind-utils
# 域名解析
[root@k8smaster k8s]# dig @10.96.0.10 service-headliness.dev.svc.cluster.local
service-headliness.dev.svc.cluster.local. 30 IN A 10.244.2.85
service-headliness.dev.svc.cluster.local. 30 IN A 10.244.1.42
service-headliness.dev.svc.cluster.local. 30 IN A 10.244.1.43
# 域名解析
[root@k8smaster k8s]# nslookup service-headliness.dev.svc.cluster.local 10.96.0.10
Server: 10.96.0.10
Address: 10.96.0.10#53
Name: service-headliness.dev.svc.cluster.local
Address: 10.244.2.85
Name: service-headliness.dev.svc.cluster.local
Address: 10.244.1.42
Name: service-headliness.dev.svc.cluster.local
Address: 10.244.1.43
使用场景:
-
服务端负载:正常的service 下面挂的是Endpoints(podIP数组),通过iptables规则转发到实际的POD上
-
客户端负载:Headless Services不会分配ClusterIP,而是将Endpoints(即podIP数组)返回,也就将服务端的所有节点地址返回,让客户端自行要通过负载策略完成负载均衡。
4)NodePort类型的Service
在之前的样例中,创建的Service的ip地址只有集群内部才可以访问,如果希望将Service暴露给集群外部使用,那么就要使用到另外一种类型的Service,称为NodePort类型。NodePort的工作原理其实就是将service的端口映射到Node的一个端口上,然后就可以通过NodeIp:NodePort来访问service了。
创建service-nodeport.yaml
apiVersion: v1
kind: Service
metadata:
name: service-nodeport
namespace: dev
spec:
selector:
app: nginx-pod
type: NodePort # service类型
ports:
- port: 80
nodePort: 30002 # 指定绑定的node的端口(默认的取值范围是:30000-32767), 如果不指定,会默认分配
targetPort: 80
# 创建service
[root@k8smaster k8s]# kubectl create -f service-nodeport.yaml
service/service-nodeport created
# 查看service
[root@k8smaster k8s]# kubectl get svc -n dev -o wide
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE SELECTOR
service-nodeport NodePort 10.103.56.244 <none> 80:30002/TCP 20s app=nginx-pod
# 接下来可以通过电脑主机的浏览器去访问集群中任意一个nodeip的30002端口,即可访问到pod
5)LoadBalancer类型的Service
LoadBalancer和NodePort很相似,目的都是向外部暴露一个端口,区别在于LoadBalancer会在集群的外部再来做一个负载均衡设备,而这个设备需要外部环境支持的,外部服务发送到这个设备上的请求,会被设备负载之后转发到集群中。
6)ExternalName类型的Service
ExternalName类型的Service用于引入集群外部的服务,它通过externalName属性指定外部一个服务的地址,然后在集群内部访问此service就可以访问到外部的服务了。
service-externalname.yaml
apiVersion: v1
kind: Service
metadata:
name: service-externalname
namespace: dev
spec:
type: ExternalName # service类型
externalName: www.baidu.com #改成ip地址也可以
# 创建service
[root@k8snode1 ~]# kubectl create -f service-externalname.yaml
service/service-externalname created
[root@k8snode1 ~]# kubectl get svc service-externalname -n dev -o wide
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE SELECTOR
service-externalname ExternalName <none> www.baidu.com <none> 20s <none>
# 域名解析
[root@k8smaster k8s]# dig @10.96.0.10 service-externalname.dev.svc.cluster.local
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 183.232.231.172
www.a.shifen.com. 30 IN A 183.232.231.174
1.4 Ingress介绍
Service对集群之外暴露服务的主要方式有两种:NotePort和LoadBalancer,但是这两种方式,都有一定的缺点:
- NodePort方式的缺点是会占用很多集群机器的端口,那么当集群服务变多的时候,这个缺点就愈发明显
- LB方式的缺点是每个service需要一个LB,浪费、麻烦,并且需要kubernetes之外设备的支持
基于这种现状,kubernetes提供了Ingress资源对象,Ingress只需要一个NodePort或者一个LB就可以满足暴露多个Service的需求。工作机制大致如下图表示:
实际上,Ingress相当于一个7层的负载均衡器,是kubernetes对反向代理的一个抽象,它的工作原理类似于Nginx,可以理解成在Ingress里建立诸多映射规则,Ingress Controller通过监听这些配置规则并转化成Nginx的反向代理配置 , 然后对外部提供服务。在这里有两个核心概念:
- ingress:kubernetes中的一个对象,作用是定义请求如何转发到service的规则
- ingress controller:具体实现反向代理及负载均衡的程序,对ingress定义的规则进行解析,根据配置的规则来实现请求转发,实现方式有很多,比如Nginx, Contour, Haproxy等等
Ingress(以Nginx为例)的工作原理如下:
- 用户编写Ingress规则,说明哪个域名对应kubernetes集群中的哪个Service
- Ingress控制器动态感知Ingress服务规则的变化,然后生成一段对应的Nginx反向代理配置
- Ingress控制器会将生成的Nginx配置写入到一个运行着的Nginx服务中,并动态更新
- 到此为止,其实真正在工作的就是一个Nginx了,内部配置了用户定义的请求转发规则
1.5 Ingress使用
1)环境准备
搭建ingress环境
# 创建文件夹
[root@k8smaster k8s]# mkdir ingress-controller
[root@k8smaster k8s]# cd ingress-controller/
# 获取ingress-nginx,本次案例使用的是0.30版本
[root@k8smaster ingress-controller]# wget https://raw.githubusercontent.com/kubernetes/ingress-nginx/nginx-0.30.0/deploy/static/mandatory.yaml
[root@k8smaster ingress-controller]# wget https://raw.githubusercontent.com/kubernetes/ingress-nginx/nginx-0.30.0/deploy/static/provider/baremetal/service-nodeport.yaml
# 修改mandatory.yaml文件中的仓库
# 修改(可不修改)quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.30.0
# 为quay-mirror.qiniu.com/kubernetes-ingress-controller/nginx-ingress-controller:0.30.0
# 创建ingress-nginx
[root@k8smaster ingress-controller]# kubectl apply -f ./
# 查看ingress-nginx
[root@k8smaster ingress-controller]# kubectl get pod -n ingress-nginx
NAME READY STATUS RESTARTS AGE
nginx-ingress-controller-5bb8fb4bb6-5ltwm 1/1 Running 0 74s
# 查看service
[root@k8smaster ingress-controller]# kubectl get svc -n ingress-nginx
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
ingress-nginx NodePort 10.110.73.70 <none> 80:32516/TCP,443:31279/TCP 4m34s
准备service和pod
为了后面的实验比较方便,创建如下图所示的模型
创建tomcat-nginx.yaml
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
---
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
---
apiVersion: v1
kind: Service
metadata:
name: nginx-service
namespace: dev
spec:
selector:
app: nginx-pod
clusterIP: None
type: ClusterIP
ports:
- port: 80
targetPort: 80
---
apiVersion: v1
kind: Service
metadata:
name: tomcat-service
namespace: dev
spec:
selector:
app: tomcat-pod
clusterIP: None
type: ClusterIP
ports:
- port: 8080
# 创建
[root@k8smaster k8s]# kubectl create -f tomcat-nginx.yaml
deployment.apps/nginx-deployment created
deployment.apps/tomcat-deployment created
service/nginx-service created
service/tomcat-service created
# 查看
[root@k8smaster k8s]# kubectl get svc -n dev
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
nginx-service ClusterIP None <none> 80/TCP 18s
tomcat-service ClusterIP None <none> 8080/TCP 18s
2)Http代理
创建ingress-http.yaml
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
name: ingress-http
namespace: dev
spec:
rules:
- host: nginx.slfx.com
http:
paths:
- path: /
backend:
serviceName: nginx-service
servicePort: 80
- host: tomcat.slfx.com
http:
paths:
- path: /
backend:
serviceName: tomcat-service
servicePort: 8080
# 创建
[root@k8smaster k8s]# kubectl create -f ingress-http.yaml
ingress.extensions/ingress-http created
# 查看
[root@k8smaster k8s]# kubectl get ing -n dev
NAME CLASS HOSTS ADDRESS PORTS AGE
ingress-http <none> nginx.slfx.com,tomcat.slfx.com 10.110.73.70 80 21s
# 查看详情
[root@k8smaster k8s]# kubectl describe ing ingress-http -n dev
Name: ingress-http
Namespace: dev
Address: 10.110.73.70
Default backend: default-http-backend:80 (<error: endpoints "default-http-backend" not found>)
Rules:
Host Path Backends
---- ---- --------
nginx.slfx.com
/ nginx-service:80 (10.244.1.48:80,10.244.1.49:80,10.244.2.92:80)
tomcat.slfx.com
/ tomcat-service:8080 (10.244.1.51:8080,10.244.2.90:8080,10.244.2.91:8080)
Annotations: <none>
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal CREATE 58s nginx-ingress-controller Ingress dev/ingress-http
Normal UPDATE 54s nginx-ingress-controller Ingress dev/ingress-http
# 查看ingress提供的端口
[root@k8smaster k8s]# kubectl get svc -n ingress-nginx
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
ingress-nginx NodePort 10.110.73.70 <none> 80:32516/TCP,443:31279/TCP 2d21h
# 接下来,在本地电脑上配置host文件,解析上面的两个域名到192.168.12.131(master)上
C:\Windows\System32\drivers\etc
192.168.12.131 tomcat.slfx.com
192.168.12.131 nginx.slfx.com
# 然后,就可以分别访问tomcat.slfx.com:32516 和 nginx.slfx.com:32516 查看效果了
3)Https代理
创建证书
# 生成证书
openssl req -x509 -sha256 -nodes -days 365 -newkey rsa:2048 -keyout tls.key -out tls.crt -subj "/C=CN/ST=BJ/L=BJ/O=nginx/CN=slfx.com"
# 创建密钥
kubectl create secret tls tls-secret --key tls.key --cert tls.crt
创建ingress-https.yaml
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
name: ingress-https
namespace: dev
spec:
tls:
- hosts:
- nginx.slfx.com
- tomcat.slfx.com
secretName: tls-secret # 指定秘钥
rules:
- host: nginx.slfx.com
http:
paths:
- path: /
backend:
serviceName: nginx-service
servicePort: 80
- host: tomcat.slfx.com
http:
paths:
- path: /
backend:
serviceName: tomcat-service
servicePort: 8080
# 创建
[root@k8smaster k8s]# kubectl create -f ingress-https.yaml
ingress.extensions/ingress-https created
# 查看
[root@k8smaster k8s]# kubectl get ing ingress-https -n dev
NAME CLASS HOSTS ADDRESS PORTS AGE
ingress-https <none> nginx.slfx.com,tomcat.slfx.com 10.99.188.23 80, 443 84s
# 查看详情
[root@k8smaster k8s]# kubectl describe ing ingress-https -n dev
Name: ingress-https
Namespace: dev
Address: 10.99.188.23
Default backend: default-http-backend:80 (<error: endpoints "default-http-backend" not found>)
TLS:
tls-secret terminates nginx.slfx.com,tomcat.slfx.com
Rules:
Host Path Backends
---- ---- --------
nginx.slfx.com
/ nginx-service:80 (10.244.1.54:80,10.244.1.55:80,10.244.2.93:80)
tomcat.slfx.com
/ tomcat-service:8080 (10.244.1.53:8080,10.244.2.94:8080,10.244.2.95:8080)
Annotations: <none>
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal CREATE 12s nginx-ingress-controller Ingress dev/ingress-https
Normal UPDATE 2s nginx-ingress-controller Ingress dev/ingress-https
[root@k8smaster k8s]# kubectl get svc -n ingress-nginx
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
ingress-nginx NodePort 10.99.188.23 <none> 80:31366/TCP,443:32155/TCP 14m
# 下面可以通过浏览器访问https://nginx.slfx.com:32155 和 https://tomcat.slfx.com:32155来查看了