k8s部署Ingress并創(chuàng)建規(guī)則的詳細(xì)介紹

更新時(shí)間：2022年03月28日 15:41:56 作者：suqinyi

這篇文章主要介紹了k8s部署Ingress并創(chuàng)建規(guī)則,本文通過(guò)圖文實(shí)例相結(jié)合給大家介紹的非常詳細(xì)，對(duì)大家的學(xué)習(xí)或工作具有一定的參考借鑒價(jià)值，需要的朋友可以參考下

一、Ingress介紹

Ingress由兩部分組成：Ingress controller和Ingress服務(wù)
通過(guò) Service 發(fā)現(xiàn) Pod 進(jìn)行關(guān)聯(lián)?；谟蛎L問(wèn)
通過(guò) Ingress Controller 實(shí)現(xiàn) Pod 負(fù)載均衡
支持 TCP/UDP 4 層負(fù)載均衡和 HTTP 7 層負(fù)載均衡
底層實(shí)現(xiàn)是nignx

在這里插入圖片描述

二、Ingress文件獲取

1.1 、說(shuō)明

官方地址：https://github.com/kubernetes/ingress-nginx

部署文件說(shuō)明

## 這個(gè)地址被墻,需要科學(xué)上網(wǎng)！??！
# mandatory.yaml為ingress所有資源yml文件的集合
# 若是單獨(dú)部署，需要分別下載configmap.yaml、namespace.yaml、rbac.yaml、service-nodeport.yaml、with-rbac.yaml
wget https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/static/mandatory.yaml
# service-nodeport.yaml為ingress通過(guò)nodeport對(duì)外提供服務(wù)，注意默認(rèn)nodeport暴露端口為隨機(jī)，可以編輯該文件自定義端口
wget https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/static/provider/baremetal/service-nodeport.yaml

1.2 、文件內(nèi)容

ingress-controller.yaml

apiVersion: v1
kind: Namespace
metadata:
  name: ingress-nginx
  labels:
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/part-of: ingress-nginx

---
kind: ConfigMap
  name: nginx-configuration
  namespace: ingress-nginx
  name: tcp-services
  name: udp-services
kind: ServiceAccount
  name: nginx-ingress-serviceaccount
apiVersion: rbac.authorization.k8s.io/v1beta1
kind: ClusterRole
  name: nginx-ingress-clusterrole
rules:
  - apiGroups:
      - ""
    resources:
      - configmaps
      - endpoints
      - nodes
      - pods
      - secrets
    verbs:
      - list
      - watch
      - get
      - services
      - "extensions"
      - ingresses
      - events
      - create
      - patch
      - ingresses/status
      - update
kind: Role
  name: nginx-ingress-role
      - namespaces
    resourceNames:
      # Defaults to "<election-id>-<ingress-class>"
      # Here: "<ingress-controller-leader>-<nginx>"
      # This has to be adapted if you change either parameter
      # when launching the nginx-ingress-controller.
      - "ingress-controller-leader-nginx"
kind: RoleBinding
  name: nginx-ingress-role-nisa-binding
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: Role
subjects:
  - kind: ServiceAccount
    name: nginx-ingress-serviceaccount
    namespace: ingress-nginx
kind: ClusterRoleBinding
  name: nginx-ingress-clusterrole-nisa-binding
  kind: ClusterRole
apiVersion: apps/v1
kind: DaemonSet 
  name: nginx-ingress-controller
spec:
  selector:
    matchLabels:
      app.kubernetes.io/name: ingress-nginx
      app.kubernetes.io/part-of: ingress-nginx
  template:
    metadata:
      labels:
        app.kubernetes.io/name: ingress-nginx
        app.kubernetes.io/part-of: ingress-nginx
      annotations:
        prometheus.io/port: "10254"
        prometheus.io/scrape: "true"
    spec:
      hostNetwork: true
      serviceAccountName: nginx-ingress-serviceaccount
      containers:
        - name: nginx-ingress-controller
          image: siriuszg/nginx-ingress-controller:0.20.0
          args:
            - /nginx-ingress-controller
            - --configmap=$(POD_NAMESPACE)/nginx-configuration
            - --tcp-services-configmap=$(POD_NAMESPACE)/tcp-services
            - --udp-services-configmap=$(POD_NAMESPACE)/udp-services
            - --publish-service=$(POD_NAMESPACE)/ingress-nginx
            - --annotations-prefix=nginx.ingress.kubernetes.io
          securityContext:
            allowPrivilegeEscalation: true
            capabilities:
              drop:
                - ALL
              add:
                - NET_BIND_SERVICE
            # www-data -> 33
            runAsUser: 33
          env:
            - name: POD_NAME
              valueFrom:
                fieldRef:
                  fieldPath: metadata.name
            - name: POD_NAMESPACE
                  fieldPath: metadata.namespace
          ports:
            - name: http
              containerPort: 80
            - name: https
              containerPort: 443
          livenessProbe:
            failureThreshold: 3
            httpGet:
              path: /healthz
              port: 10254
              scheme: HTTP
            initialDelaySeconds: 10
            periodSeconds: 10
            successThreshold: 1
            timeoutSeconds: 10
          readinessProbe:
kind: Service
  #type: NodePort
  ports:
  - name: http
    port: 80
    targetPort: 80
    protocol: TCP
  - name: https
    port: 443
    targetPort: 443

三、k8s應(yīng)用 ingress-controller.yaml

應(yīng)用

kubectl apply -f ingress-controller.yaml

如圖：

在這里插入圖片描述

查看是否完成

kubectl get pods --all-namespaces

在這里插入圖片描述

四、創(chuàng)建Ingress規(guī)則

如果沒(méi)有部署和服務(wù)==>查看k8s部署并映射tomcat8

查看自己創(chuàng)建的服務(wù)，以tomcat8為例

kubectl get all

自己創(chuàng)建文件 ingress-tomcat8.yaml

vi ingress-tomcat8.yaml

ingress-tomcat8.yaml規(guī)則內(nèi)容

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: web
spec:
  rules: 
  - host: k8s.tomcat8.com
    http:
      paths:
        - backend:
           serviceName: tomcat8
           servicePort: 80

如圖:

在這里插入圖片描述