使用ingress 暴露springcloud服務
k8s 集羣搭建成功了,也能部署應用了,但是不可能每次去訪問服務的時候都要去查一下運行的node和nodePort吧,即使查好node和nodePort ,避免不了重啓k8s或者 ReplicationController,node 和 nodeport 又會改變,K8s 提供了 Ingress 來解決這個問題。
1.生成一個默認的後端
生成一個默認的後端,如果遇到解析不到的URL就轉發到默認後端頁面
[root@master ingress]# cat default-backend.yaml
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
name: default-http-backend
labels:
k8s-app: default-http-backend
namespace: default
spec:
replicas: 1
template:
metadata:
labels:
k8s-app: default-http-backend
spec:
terminationGracePeriodSeconds: 60
containers:
- name: default-http-backend
# Any image is permissable as long as:
# 1. It serves a 404 page at /
# 2. It serves 200 on a /healthz endpoint
image: docker.io/cdchen/defaultbackend:1.0
livenessProbe:
httpGet:
path: /healthz
port: 8080
scheme: HTTP
initialDelaySeconds: 30
timeoutSeconds: 5
ports:
- containerPort: 8080
resources:
limits:
cpu: 10m
memory: 20Mi
requests:
cpu: 10m
memory: 20Mi
---
apiVersion: v1
kind: Service
metadata:
name: default-http-backend
namespace: default
labels:
k8s-app: default-http-backend
spec:
ports:
- port: 80
targetPort: 8080
selector:
k8s-app: default-http-backend
[root@master ingress]# kubectl create -f default-backend.yaml
deployment "default-http-backend" created
service "default-http-backend" created
2.部署Ingress Controller
[root@master ingress]# cat nginx-ingress-controller.yaml
apiVersion: v1
kind: ReplicationController
metadata:
name: nginx-ingress-lb
labels:
name: nginx-ingress-lb
namespace: default
spec:
replicas: 1
template:
metadata:
labels:
name: nginx-ingress-lb
annotations:
prometheus.io/port: '10254'
prometheus.io/scrape: 'true'
spec:
terminationGracePeriodSeconds: 60
hostNetwork: true
containers:
- image: docker.io/cdchen/nginx-ingress-controller:0.9.0-beta.12
name: nginx-ingress-lb
readinessProbe:
httpGet:
path: /healthz
port: 10254
scheme: HTTP
livenessProbe:
httpGet:
path: /healthz
port: 10254
scheme: HTTP
initialDelaySeconds: 10
timeoutSeconds: 1
ports:
- containerPort: 80
hostPort: 80
- containerPort: 443
hostPort: 443
env:
- name: POD_NAME
valueFrom:
fieldRef:
fieldPath: metadata.name
- name: POD_NAMESPACE
valueFrom:
fieldRef:
fieldPath: metadata.namespace
- name: KUBERNETES_MASTER
value: http://192.168.6.150:8080
args:
- /nginx-ingress-controller
- --default-backend-service=$(POD_NAMESPACE)/default-http-backend
- --apiserver-host=http://192.168.6.45:8080
記得修改 - –apiserver-host=http://192.168.6.45:8080
[root@master ingress]# kubectl create -f nginx-ingress-controller.yaml
replicationcontroller "nginx-ingress-lb" created
3.配置ingress
貼一個k8s dashboard 的 ingress配置
[root@master ingress]# cat k8s-dashboard.yaml
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
name: k8s-dashboard-ingress
namespace: kube-system
spec:
rules:
- host: k8s.webui
http:
paths:
- path: /
backend:
serviceName: kubernetes-dashboard
servicePort: 80
[root@master ingress]# kubectl create -f k8s-dashboard.yaml
ingress "k8s-dashboard-ingress" created
理解如下:
- host指虛擬出來的域名,具體地址(我理解應該是Ingress-controller那臺Pod所在的主機的地址)應該加入/etc/hosts中,這樣所有去k8s.webui的請求都會發到nginx
- path:/console匹配後面的應用路徑
- servicePort主要是定義服務的時候的端口,不是NodePort.
- path:/ 匹配後面dashboard應用的路徑
在 node 節點中docker ps 查看是否存在ingress Controller,然後把對應的ip添加進本機host,
在瀏覽器內訪問 http://k8s.webui/
如下圖:
貼一個前一篇博客介紹的多應用的部署的ingress 配置文件
[root@master ingress]# cat cloud-vue.yaml
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
name: cloud-vue-api
namespace: default
spec:
rules:
- host: cloud.vue.api
http:
paths:
- path: /console
backend:
serviceName: helloworldsvc
servicePort: 7001
- path: /
backend:
serviceName: cloud-simple-server
servicePort: 8081
- host: cloud.vue.eureka
http:
paths:
- path: /
backend:
serviceName: cloud-eureka-server
servicePort: 8888
- host: cloud.vue.config
http:
paths:
- path: /
backend:
serviceName: cloud-config-server
servicePort: 1111
- host: cloud.vue.zipkin
http:
paths:
- path: /
backend:
serviceName: cloud-zipkin-server
servicePort: 9012
注:已經使用ingress暴露服務了,再部署的時候service的類型可以選擇internal了 ,不再需要external。還有https的配置,請參考 http://www.cnblogs.com/ericnie/p/6965091.html