k8s 部署 Ingress 及使用

一：下载Ingress-controller.yaml 文件

在k8s master 机器上执行以下载命令

wget https://raw.githubusercontent.com/kubernetes/ingress-Nginx/Nginx-0.20.0/deploy/mandatory.yaml

或者 官网默认下载最新的yaml：

• 　　　　wget https://raw.githubusercontent.com/kubernetes/ingress-Nginx/master/deploy/mandatory.yaml

如果下载不成功，不慌，我这有现成的，直接复制粘贴

----------------mandatory.yaml start------------------------------------------

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

---

kind: ConfigMap
apiVersion: v1
Metadata:
  name: Nginx-configuration
  namespace: ingress-Nginx
  labels:
    app.kubernetes.io/name: ingress-Nginx
    app.kubernetes.io/part-of: ingress-Nginx

---
kind: ConfigMap
apiVersion: v1
Metadata:
  name: tcp-services
  namespace: ingress-Nginx
  labels:
    app.kubernetes.io/name: ingress-Nginx
    app.kubernetes.io/part-of: ingress-Nginx

---
kind: ConfigMap
apiVersion: v1
Metadata:
  name: udp-services
  namespace: ingress-Nginx
  labels:
    app.kubernetes.io/name: ingress-Nginx
    app.kubernetes.io/part-of: ingress-Nginx

---
apiVersion: v1
kind: ServiceAccount
Metadata:
  name: nginx-ingress-serviceaccount
  namespace: ingress-Nginx
  labels:
    app.kubernetes.io/name: ingress-Nginx
    app.kubernetes.io/part-of: ingress-Nginx

---
apiVersion: rbac.authorization.k8s.io/v1beta1
kind: ClusterRole
Metadata:
  name: nginx-ingress-clusterrole
  labels:
    app.kubernetes.io/name: ingress-Nginx
    app.kubernetes.io/part-of: ingress-Nginx
rules:
  - apiGroups:
      - ""
    resources:
      - configmaps
      - endpoints
      - nodes
      - pods
      - secrets
    verbs:
      - list
      - watch
  - apiGroups:
      - ""
    resources:
      - nodes
    verbs:
      - get
  - apiGroups:
      - ""
    resources:
      - services
    verbs:
      - get
      - list
      - watch
  - apiGroups:
      - ""
    resources:
      - events
    verbs:
      - create
      - patch
  - apiGroups:
      - "extensions"
      - "networking.k8s.io"
    resources:
      - ingresses
    verbs:
      - get
      - list
      - watch
  - apiGroups:
      - "extensions"
      - "networking.k8s.io"
    resources:
      - ingresses/status
    verbs:
      - update

---
apiVersion: rbac.authorization.k8s.io/v1beta1
kind: Role
Metadata:
  name: nginx-ingress-role
  namespace: ingress-Nginx
  labels:
    app.kubernetes.io/name: ingress-Nginx
    app.kubernetes.io/part-of: ingress-Nginx
rules:
  - apiGroups:
      - ""
    resources:
      - configmaps
      - pods
      - secrets
      - namespaces
    verbs:
      - get
  - apiGroups:
      - ""
    resources:
      - configmaps
    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"
    verbs:
      - get
      - update
  - apiGroups:
      - ""
    resources:
      - configmaps
    verbs:
      - create
  - apiGroups:
      - ""
    resources:
      - endpoints
    verbs:
      - get

---
apiVersion: rbac.authorization.k8s.io/v1beta1
kind: RoleBinding
Metadata:
  name: nginx-ingress-role-nisa-binding
  namespace: ingress-Nginx
  labels:
    app.kubernetes.io/name: ingress-Nginx
    app.kubernetes.io/part-of: ingress-Nginx
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: Role
  name: nginx-ingress-role
subjects:
  - kind: ServiceAccount
    name: nginx-ingress-serviceaccount
    namespace: ingress-Nginx

---
apiVersion: rbac.authorization.k8s.io/v1beta1
kind: ClusterRoleBinding
Metadata:
  name: nginx-ingress-clusterrole-nisa-binding
  labels:
    app.kubernetes.io/name: ingress-Nginx
    app.kubernetes.io/part-of: ingress-Nginx
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: nginx-ingress-clusterrole
subjects:
  - kind: ServiceAccount
    name: nginx-ingress-serviceaccount
    namespace: ingress-Nginx

---

apiVersion: apps/v1
kind: DaemonSet
Metadata:
  name: nginx-ingress-controller
  namespace: ingress-Nginx
  labels:
    app.kubernetes.io/name: ingress-Nginx
    app.kubernetes.io/part-of: ingress-Nginx
spec:
 # replicas: 1
  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
      # wait up to five minutes for the drain of connections
      terminationGracePeriodSeconds: 300
      serviceAccountName: nginx-ingress-serviceaccount
      containers:
        - name: nginx-ingress-controller
          image: registry.cn-qingdao.aliyuncs.com/kubernetes_xingej/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
              valueFrom:
                fieldRef:
                  fieldpath: Metadata.namespace
          ports:
            - name: http
              containerPort: 80
              protocol: TCP
            - name: https
              containerPort: 443
              protocol: TCP
          livenessProbe:
            failureThreshold: 3
            httpGet:
              path: /healthz
              port: 10254
              scheme: HTTP
            initialDelaySeconds: 10
            periodSeconds: 10
            successthreshold: 1
            timeoutSeconds: 10

---

apiVersion: v1
kind: Service
Metadata:
  name: ingress-Nginx
  namespace: ingress-Nginx
  labels:
    app.kubernetes.io/name: ingress-Nginx
    app.kubernetes.io/part-of: ingress-Nginx
spec:
  type: NodePort
  ports:
    - name: http
      port: 80
      targetPort: 80
      protocol: TCP
      nodePort: 32080
    - name: https
      port: 443
      targetPort: 443
      protocol: TCP
      nodePort: 32443
  selector:
    app.kubernetes.io/name: ingress-Nginx
    app.kubernetes.io/part-of: ingress-Nginx

---

----------------mandatory.yaml end------------------------------------------

二：下载nginx-ingress-controller:2.0镜像

docker pull  registry.cn-qingdao.aliyuncs.com/kubernetes_xingej/nginx-ingress-controller:0.20.0

三：执行mandatory.yaml 文件

kubectl apply -f mandatory.yaml

查看是否安装成功     kubectl get pods ‐n ingress‐Nginx ‐o wide

如果有安装Dashboard（没有请跳过） 可以直接在页面上看到 nginx-ingress-controller  的运行状态！

创建测试pod 、service

四：执行ingress-Nginx.ymal 文件（ingress 规则）

@H_67_404@

apiVersion: extensions/v1beta1
kind: Ingress
Metadata:
  name: ingress-Nginx
  namespace: htcf
  annotations:
    # use the shared ingress-Nginx
    kubernetes.io/ingress.class: "Nginx"
    # 开启use-regex，启用path的正则匹配
    Nginx.ingress.kubernetes.io/use-regex: "true"
spec:
  rules:
  - host: Nginx.kube.com
    http:
      paths:
      - path: /
        backend:
          serviceName: k8snode2
          servicePort: 80
     

@H_67_404@ 查看生效的ingress规则：    kubectl get ing

 serviceName  对应 service 

 servicePort  对应  

五：

在访问机器配置host，win10客户机在目录：C:\Windows\System32\drivers\etc，在host里增加如下 10.168.0.173   Nginx.kube.com 或 10.168.0.125   Nginx.kube.com host(ingress部署的机器ip对应访问的域名)

配置完后直接在客户机浏览器访问 http://Nginx.kube.com/ ，能正常访问Nginx。 没写全，随后有空在更新！！！！！！