kubernetes--ingress

已于 2022-08-08 17:35:28 修改
阅读量2.1k 收藏 6
点赞数 2
分类专栏： kubernetes 文章标签： 运维 kubernetes docker
于 2022-08-08 15:42:46 首次发布
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/lovely_red_scarf/article/details/126224671
版权

Ingress

文章目录

一、Ingress

  • 文档: https://www.kubernetes.org.cn/ingress
  • Ingress 是 Kubernetes 的一种 API 对象，将集群内部的 Service 通过 HTTP/HTTPS 方式暴露到集群外部，并通过规则定义 HTTP/HTTPS 的路由

1.1:Ingress是什么？

通常情况下，service和pod的IP仅可在集群内部访问。集群外部的请求需要通过负载均衡转发到service在Node上暴露的NodePort上，然后再由kube-proxy将其转发给相关的Pod。

  • 而Ingress就是为进入集群的请求提供路由规则的集合，如下图所示
    internet
        |
   [ Ingress ]
   --|-----|--
   [ Services ]
  • ingress可以给service提供集群外部访问的URL、负载均衡、SSL终止、HTTP路由等。为了配置这些Ingress规则，集群管理员需要部署一个Ingress controller，它监听Ingress和service的变化，并根据规则配置负载均衡并提供访问入口。

1.2、nodeport和ingress对比:

  • 如果我们为每一个deployment配置了对应的nodeport类型的svc也是可以对外访问，但是那样配置太多了，如果我们都配置了ingress的话只需要对应暴漏出一个nodeport的ingress端口即可，方便管理

  • 比如nodeport类型的svc:(暴漏了这么多的nodeport端口)
    在这里插入图片描述

  • 而ingress只需要暴漏出ingress-controller一个nodeport即可

在这里插入图片描述

1.3、Ingress格式

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: test-ingress
spec:
  rules:
  - http:
      paths:
      - path: /testpath
        backend:
          serviceName: 要绑定的svc名
          servicePort: 80

1.4、ingress和svc关联

  • svc和pod是通过标签来一一对应的，而ingress是需要和service绑定，通过service的name来进行一一对应的

二、Ingress的安装

2.1、nginx-controller

ingress是由 ingress-controll 来统一分发的

  • ngress 可以给 Service 提供集群外部访问的 URL、负载均衡、SSL 终止、HTTP 路由等。为了配置这些 Ingress 规则，集群管理员需要部署一个 Ingress Controller，它监听 Ingress 和 Service 的变化，并根据规则配置负载均衡并提供访问入口。

  • 为了使得Nginx Ingress资源正常工作，集群中必须要有个Nginx Ingress Controller来解析Nginx Ingress的转发规则。Nginx Ingress Controller收到请求，匹配Nginx Ingress转发规则转发到后端Service所对应的Pod，由Pod处理请求。Kubernetes中Service、Nginx Ingress与Nginx Ingress Controller有着以下关系：

  • 1、Service是后端真实服务的抽象，一个Service可以代表多个相同的后端服务。
    2、Nginx Ingress是反向代理规则，用来规定HTTP/HTTPS请求应该被转发到哪个Service所对应的Pod上。例如根据请求中不同的Host和URL路径，让请求落到不同Service所对应的Pod上。
    3、Nginx Ingress Controller是一个反向代理程序，负责解析Nginx Ingress的反向代理规则。如果Nginx Ingress有增删改的变动，Nginx Ingress Controller会及时更新自己相应的转发规则，当Nginx Ingress Controller收到请求后就会根据这些规则将请求转发到对应Service的Pod上。

Nginx Ingress Controller通过API Server获取Ingress资源的变化，动态地生成Load Balancer（例如Nginx）所需的配置文件（例如nginx.conf），然后重新加载Load Balancer（例如执行nginx -s load重新加载Nginx）来生成新的路由转发规则。
在这里插入图片描述

2.2、安装ingress-controller

Ingress-Nginx github 地址：https://github.com/kubernetes/ingress-nginx
Ingress-Nginx 官方网站：https://kubernetes.github.io/ingress-nginx/

2.2.1、下载ingress-controller

  • 进入ingress-nginx官网:
  • 在这里插入图片描述
    找到这里下载:

在这里插入图片描述

  • 现在日期是20022-08-08现在官网显示的是V1.3.0版本的controller，因为我的kubernetes版本是v1.7但是官网最下面介绍了 ，k8s低于1.9的要使用的ingress-controller要是0.x

  • 在这里插入图片描述

  • 所以我的下载时0.49版本的ingress-controller

  • 下载ingress-controller

wget https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v0.49.0/deploy/static/provider/cloud/deploy.yaml

  • 下载的yaml格式如下；

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

---
# Source: ingress-nginx/templates/controller-serviceaccount.yaml
apiVersion: v1
kind: ServiceAccount
metadata:
  labels:
    helm.sh/chart: ingress-nginx-3.36.0
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/instance: ingress-nginx
    app.kubernetes.io/version: 0.49.0
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/component: controller
  name: ingress-nginx
  namespace: ingress-nginx
automountServiceAccountToken: true
---
# Source: ingress-nginx/templates/controller-configmap.yaml
apiVersion: v1
kind: ConfigMap
metadata:
  labels:
    helm.sh/chart: ingress-nginx-3.36.0
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/instance: ingress-nginx
    app.kubernetes.io/version: 0.49.0
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/component: controller
  name: ingress-nginx-controller
  namespace: ingress-nginx
data:
---
# Source: ingress-nginx/templates/clusterrole.yaml
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  labels:
    helm.sh/chart: ingress-nginx-3.36.0
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/instance: ingress-nginx
    app.kubernetes.io/version: 0.49.0
    app.kubernetes.io/managed-by: Helm
  name: 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:
      - extensions
      - networking.k8s.io   # k8s 1.14+
    resources:
      - ingresses
    verbs:
      - get
      - list
      - watch
  - apiGroups:
      - ''
    resources:
      - events
    verbs:
      - create
      - patch
  - apiGroups:
      - extensions
      - networking.k8s.io   # k8s 1.14+
    resources:
      - ingresses/status
    verbs:
      - update
  - apiGroups:
      - networking.k8s.io   # k8s 1.14+
    resources:
      - ingressclasses
    verbs:
      - get
      - list
      - watch
---
# Source: ingress-nginx/templates/clusterrolebinding.yaml
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  labels:
    helm.sh/chart: ingress-nginx-3.36.0
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/instance: ingress-nginx
    app.kubernetes.io/version: 0.49.0
    app.kubernetes.io/managed-by: Helm
  name: ingress-nginx
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: ingress-nginx
subjects:
  - kind: ServiceAccount
    name: ingress-nginx
    namespace: ingress-nginx
---
# Source: ingress-nginx/templates/controller-role.yaml
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
  labels:
    helm.sh/chart: ingress-nginx-3.36.0
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/instance: ingress-nginx
    app.kubernetes.io/version: 0.49.0
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/component: controller
  name: ingress-nginx
  namespace: ingress-nginx
rules:
  - apiGroups:
      - ''
    resources:
      - namespaces
    verbs:
      - get
  - apiGroups:
      - ''
    resources:
      - configmaps
      - pods
      - secrets
      - endpoints
    verbs:
      - get
      - list
      - watch
  - apiGroups:
      - ''
    resources:
      - services
    verbs:
      - get
      - list
      - watch
  - apiGroups:
      - extensions
      - networking.k8s.io   # k8s 1.14+
    resources:
      - ingresses
    verbs:
      - get
      - list
      - watch
  - apiGroups:
      - extensions
      - networking.k8s.io   # k8s 1.14+
    resources:
      - ingresses/status
    verbs:
      - update
  - apiGroups:
      - networking.k8s.io   # k8s 1.14+
    resources:
      - ingressclasses
    verbs:
      - get
      - list
      - watch
  - apiGroups:
      - ''
    resources:
      - configmaps
    resourceNames:
      - ingress-controller-leader-nginx
    verbs:
      - get
      - update
  - apiGroups:
      - ''
    resources:
      - configmaps
    verbs:
      - create
  - apiGroups:
      - ''
    resources:
      - events
    verbs:
      - create
      - patch
---
# Source: ingress-nginx/templates/controller-rolebinding.yaml
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
  labels:
    helm.sh/chart: ingress-nginx-3.36.0
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/instance: ingress-nginx
    app.kubernetes.io/version: 0.49.0
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/component: controller
  name: ingress-nginx
  namespace: ingress-nginx
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: Role
  name: ingress-nginx
subjects:
  - kind: ServiceAccount
    name: ingress-nginx
    namespace: ingress-nginx
---
# Source: ingress-nginx/templates/controller-service-webhook.yaml
apiVersion: v1
kind: Service
metadata:
  labels:
    helm.sh/chart: ingress-nginx-3.36.0
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/instance: ingress-nginx
    app.kubernetes.io/version: 0.49.0
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/component: controller
  name: ingress-nginx-controller-admission
  namespace: ingress-nginx
spec:
  type: ClusterIP
  ports:
    - name: https-webhook
      port: 443
      targetPort: webhook
  selector:
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/instance: ingress-nginx
    app.kubernetes.io/component: controller
---
# Source: ingress-nginx/templates/controller-service.yaml
apiVersion: v1
kind: Service
metadata:
  annotations:
  labels:
    helm.sh/chart: ingress-nginx-3.36.0
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/instance: ingress-nginx
    app.kubernetes.io/version: 0.49.0
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/component: controller
  name: ingress-nginx-controller
  namespace: ingress-nginx
spec:
  type: NodePort
  ports:
    - name: http
      port: 80
      protocol: TCP
      targetPort: http
    - name: https
      port: 443
      protocol: TCP
      targetPort: https
  selector:
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/instance: ingress-nginx
    app.kubernetes.io/component: controller
---
# Source: ingress-nginx/templates/controller-deployment.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  labels:
    helm.sh/chart: ingress-nginx-3.36.0
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/instance: ingress-nginx
    app.kubernetes.io/version: 0.49.0
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/component: controller
  name: ingress-nginx-controller
  namespace: ingress-nginx
spec:
  selector:
    matchLabels:
      app.kubernetes.io/name: ingress-nginx
      app.kubernetes.io/instance: ingress-nginx
      app.kubernetes.io/component: controller
  revisionHistoryLimit: 10
  minReadySeconds: 0
  template:
    metadata:
      labels:
        app.kubernetes.io/name: ingress-nginx
        app.kubernetes.io/instance: ingress-nginx
        app.kubernetes.io/component: controller
    spec:
      dnsPolicy: ClusterFirst
      containers:
        - name: controller
          image: k8s.gcr.io/ingress-nginx/controller:v0.49.0@sha256:e9707504ad0d4c119036b6d41ace4a33596139d3feb9ccb6617813ce48c3eeef
          imagePullPolicy: IfNotPresent
          lifecycle:
            preStop:
              exec:
                command:
                  - /wait-shutdown
          args:
            - /nginx-ingress-controller
            - --election-id=ingress-controller-leader
            - --ingress-class=nginx
            - --configmap=$(POD_NAMESPACE)/ingress-nginx-controller
            - --validating-webhook=:8443
            - --validating-webhook-certificate=/usr/local/certificates/cert
            - --validating-webhook-key=/usr/local/certificates/key
          securityContext:
            capabilities:
              drop:
                - ALL
              add:
                - NET_BIND_SERVICE
            runAsUser: 101
            allowPrivilegeEscalation: true
          env:
            - name: POD_NAME
              valueFrom:
                fieldRef:
                  fieldPath: metadata.name
            - name: POD_NAMESPACE
              valueFrom:
                fieldRef:
                  fieldPath: metadata.namespace
            - name: LD_PRELOAD
              value: /usr/local/lib/libmimalloc.so
          livenessProbe:
            failureThreshold: 5
            httpGet:
              path: /healthz
              port: 10254
              scheme: HTTP
            initialDelaySeconds: 10
            periodSeconds: 10
            successThreshold: 1
            timeoutSeconds: 1
          readinessProbe:
            failureThreshold: 3
            httpGet:
              path: /healthz
              port: 10254
              scheme: HTTP
            initialDelaySeconds: 10
            periodSeconds: 10
            successThreshold: 1
            timeoutSeconds: 1
          ports:
            - name: http
              containerPort: 80
              protocol: TCP
            - name: https
              containerPort: 443
              protocol: TCP
            - name: webhook
              containerPort: 8443
              protocol: TCP
          volumeMounts:
            - name: webhook-cert
              mountPath: /usr/local/certificates/
              readOnly: true
          resources:
            requests:
              cpu: 100m
              memory: 90Mi
      nodeSelector:
        kubernetes.io/os: linux
      serviceAccountName: ingress-nginx
      terminationGracePeriodSeconds: 300
      volumes:
        - name: webhook-cert
          secret:
            secretName: ingress-nginx-admission
---
# Source: ingress-nginx/templates/admission-webhooks/validating-webhook.yaml
# before changing this value, check the required kubernetes version
# https://kubernetes.io/docs/reference/access-authn-authz/extensible-admission-controllers/#prerequisites
apiVersion: admissionregistration.k8s.io/v1
kind: ValidatingWebhookConfiguration
metadata:
  labels:
    helm.sh/chart: ingress-nginx-3.36.0
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/instance: ingress-nginx
    app.kubernetes.io/version: 0.49.0
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/component: admission-webhook
  name: ingress-nginx-admission
webhooks:
  - name: validate.nginx.ingress.kubernetes.io
    matchPolicy: Equivalent
    rules:
      - apiGroups:
          - networking.k8s.io
        apiVersions:
          - v1beta1
        operations:
          - CREATE
          - UPDATE
        resources:
          - ingresses
    failurePolicy: Fail
    sideEffects: None
    admissionReviewVersions:
      - v1
      - v1beta1
    clientConfig:
      service:
        namespace: ingress-nginx
        name: ingress-nginx-controller-admission
        path: /networking/v1beta1/ingresses
---
# Source: ingress-nginx/templates/admission-webhooks/job-patch/serviceaccount.yaml
apiVersion: v1
kind: ServiceAccount
metadata:
  name: ingress-nginx-admission
  namespace: ingress-nginx
  annotations:
    helm.sh/hook: pre-install,pre-upgrade,post-install,post-upgrade
    helm.sh/hook-delete-policy: before-hook-creation,hook-succeeded
  labels:
    helm.sh/chart: ingress-nginx-3.36.0
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/instance: ingress-nginx
    app.kubernetes.io/version: 0.49.0
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/component: admission-webhook
---
# Source: ingress-nginx/templates/admission-webhooks/job-patch/clusterrole.yaml
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  name: ingress-nginx-admission
  annotations:
    helm.sh/hook: pre-install,pre-upgrade,post-install,post-upgrade
    helm.sh/hook-delete-policy: before-hook-creation,hook-succeeded
  labels:
    helm.sh/chart: ingress-nginx-3.36.0
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/instance: ingress-nginx
    app.kubernetes.io/version: 0.49.0
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/component: admission-webhook
rules:
  - apiGroups:
      - admissionregistration.k8s.io
    resources:
      - validatingwebhookconfigurations
    verbs:
      - get
      - update
---
# Source: ingress-nginx/templates/admission-webhooks/job-patch/clusterrolebinding.yaml
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: ingress-nginx-admission
  annotations:
    helm.sh/hook: pre-install,pre-upgrade,post-install,post-upgrade
    helm.sh/hook-delete-policy: before-hook-creation,hook-succeeded
  labels:
    helm.sh/chart: ingress-nginx-3.36.0
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/instance: ingress-nginx
    app.kubernetes.io/version: 0.49.0
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/component: admission-webhook
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: ingress-nginx-admission
subjects:
  - kind: ServiceAccount
    name: ingress-nginx-admission
    namespace: ingress-nginx
---
# Source: ingress-nginx/templates/admission-webhooks/job-patch/role.yaml
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
  name: ingress-nginx-admission
  namespace: ingress-nginx
  annotations:
    helm.sh/hook: pre-install,pre-upgrade,post-install,post-upgrade
    helm.sh/hook-delete-policy: before-hook-creation,hook-succeeded
  labels:
    helm.sh/chart: ingress-nginx-3.36.0
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/instance: ingress-nginx
    app.kubernetes.io/version: 0.49.0
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/component: admission-webhook
rules:
  - apiGroups:
      - ''
    resources:
      - secrets
    verbs:
      - get
      - create
---
# Source: ingress-nginx/templates/admission-webhooks/job-patch/rolebinding.yaml
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
  name: ingress-nginx-admission
  namespace: ingress-nginx
  annotations:
    helm.sh/hook: pre-install,pre-upgrade,post-install,post-upgrade
    helm.sh/hook-delete-policy: before-hook-creation,hook-succeeded
  labels:
    helm.sh/chart: ingress-nginx-3.36.0
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/instance: ingress-nginx
    app.kubernetes.io/version: 0.49.0
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/component: admission-webhook
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: Role
  name: ingress-nginx-admission
subjects:
  - kind: ServiceAccount
    name: ingress-nginx-admission
    namespace: ingress-nginx
---
# Source: ingress-nginx/templates/admission-webhooks/job-patch/job-createSecret.yaml
apiVersion: batch/v1
kind: Job
metadata:
  name: ingress-nginx-admission-create
  namespace: ingress-nginx
  annotations:
    helm.sh/hook: pre-install,pre-upgrade
    helm.sh/hook-delete-policy: before-hook-creation,hook-succeeded
  labels:
    helm.sh/chart: ingress-nginx-3.36.0
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/instance: ingress-nginx
    app.kubernetes.io/version: 0.49.0
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/component: admission-webhook
spec:
  template:
    metadata:
      name: ingress-nginx-admission-create
      labels:
        helm.sh/chart: ingress-nginx-3.36.0
        app.kubernetes.io/name: ingress-nginx
        app.kubernetes.io/instance: ingress-nginx
        app.kubernetes.io/version: 0.49.0
        app.kubernetes.io/managed-by: Helm
        app.kubernetes.io/component: admission-webhook
    spec:
      containers:
        - name: create
          image: docker.io/jettech/kube-webhook-certgen:v1.5.1
          imagePullPolicy: IfNotPresent
          args:
            - create
            - --host=ingress-nginx-controller-admission,ingress-nginx-controller-admission.$(POD_NAMESPACE).svc
            - --namespace=$(POD_NAMESPACE)
            - --secret-name=ingress-nginx-admission
          env:
            - name: POD_NAMESPACE
              valueFrom:
                fieldRef:
                  fieldPath: metadata.namespace
      restartPolicy: OnFailure
      serviceAccountName: ingress-nginx-admission
      nodeSelector:
        kubernetes.io/os: linux
      securityContext:
        runAsNonRoot: true
        runAsUser: 2000
---
# Source: ingress-nginx/templates/admission-webhooks/job-patch/job-patchWebhook.yaml
apiVersion: batch/v1
kind: Job
metadata:
  name: ingress-nginx-admission-patch
  namespace: ingress-nginx
  annotations:
    helm.sh/hook: post-install,post-upgrade
    helm.sh/hook-delete-policy: before-hook-creation,hook-succeeded
  labels:
    helm.sh/chart: ingress-nginx-3.36.0
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/instance: ingress-nginx
    app.kubernetes.io/version: 0.49.0
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/component: admission-webhook
spec:
  template:
    metadata:
      name: ingress-nginx-admission-patch
      labels:
        helm.sh/chart: ingress-nginx-3.36.0
        app.kubernetes.io/name: ingress-nginx
        app.kubernetes.io/instance: ingress-nginx
        app.kubernetes.io/version: 0.49.0
        app.kubernetes.io/managed-by: Helm
        app.kubernetes.io/component: admission-webhook
    spec:
      containers:
        - name: patch
          image: docker.io/jettech/kube-webhook-certgen:v1.5.1
          imagePullPolicy: IfNotPresent
          args:
            - patch
            - --webhook-name=ingress-nginx-admission
            - --namespace=$(POD_NAMESPACE)
            - --patch-mutating=false
            - --secret-name=ingress-nginx-admission
            - --patch-failure-policy=Fail
          env:
            - name: POD_NAMESPACE
              valueFrom:
                fieldRef:
                  fieldPath: metadata.namespace
      restartPolicy: OnFailure
      serviceAccountName: ingress-nginx-admission
      nodeSelector:
        kubernetes.io/os: linux
      securityContext:
        runAsNonRoot: true
        runAsUser: 2000
  • 下载完毕 直接kubectl apply -f 运行
  • 然后直接就帮我们建立了一个ingress-nginx的名称空间
    在这里插入图片描述

2.2.2、 修改ingress-controller的暴漏端口

但是这个时候的ingress-controll启动的svc端口不是nodeport的 我们要将它改为nodeport类型的

在这里插入图片描述
下载0.4.9版本

wget https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v0.49.0/deploy/static/provider/baremetal/deploy.yaml

  • 然后再次kubectl apply -f 运行

这个时候查看ingress-controller的暴漏端口

在这里插入图片描述

  • 记住暴漏的端口 后面要使用

三、Ingree的使用

1.单服务Ingress

首先将svc和pod关联上，ingress再关联svc

nginx-deploy.yaml

apiVersion: apps/v1
kind: Deployment
metadata:
  name: nginx-deployment
spec:
  selector:
    matchLabels:
      app: nginx
  replicas: 2
  template:
    metadata:
      labels:  # 标签
        app: nginx
        release: stabel
    spec:
      containers:
      - name: nginx
        image: 192.168.25.69/overseas/nginx:v1   # 对应的镜像仓库地址 如果是想设置公版本的可以设置 wangyanglinux/myapp:v2
        ports:
        - containerPort: 80

nginx-service.yaml

apiVersion: v1
kind: Service
metadata:
  name: nginx-deployment
  namespace: default
spec:
  type: ClusterIP
  selector: #匹配选择器
    app: nginx   #对应的pod的deployment中的app标签名
    release: stabel
  ports:
  - name: http
    port: 80
    targetPort: 80

nginx-ingress.yaml

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: nginx-deployment
spec:
  rules:
    - host: www.xxoo.com
      http:
        paths:
        - path: /
          backend:
            serviceName: nginx-deployment  # svc的名称
            servicePort: 80
  • 因为域名是我随便搞得 所以本地访问要绑定hosts 地址因为是http形式的所以要带上http的端口： www.xxoo.com:32369
  • 注意当我们的请求报503时，curl -v 当问下svc的地址看看是否和pod相通，如果svc请求正常还是503 那就是ingress和svc绑定出错

3.2、单服务Ingress–http模式

nginx-dm.yaml

apiVersion: apps/v1
kind: Deployment
metadata:
  name: nginx-dm
spec:
  selector:
    matchLabels:
      app: nginx-dm
  replicas: 2
  template:
    metadata:
      labels:  # 标签
        app: nginx-dm
        release: stabel
    spec:
      containers:
      - name: nginx-dm
        image: wangyanglinux/myapp:v1   # 对应的镜像仓库地址 如果是想设置公版本的可以设置 wangyanglinux/myapp:v2
        ports:
        - containerPort: 80

nginx-dm-service.yaml



apiVersion: v1
kind: Service
metadata:
  name: nginx-dm
  namespace: default
spec:
  type: ClusterIP
  selector: #匹配选择器
    app: nginx-dm   #对应的pod的deployment中的app标签名
    release: stabel
  ports:
  - name: http
    port: 80
    targetPort: 80

nginx-dm-ingress.yaml

apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:
  name: nginx-dm
spec:
  rules:
    - host: www.nginx-dm.com
      http:
        paths:
        - path: /
          backend:
            serviceName: nginx-dm
            servicePort: 80

3.2、单服务Ingress–https模式

首先要去自己创建一个https的证书

openssl req -x509 -sha256 -nodes -days 365 -newkey rsa:2048 -keyout tls.key -out tls.crt -subj “/CN=nginxsvc/O=nginxsvc”

  • 再执行

kubectl create secret tls tls-secret --key tls.key --cert tls.crt

3.2.1、yaml

nginx-dm.yaml

apiVersion: apps/v1
kind: Deployment
metadata:
  name: deplpyment-3
spec:
  selector:
    matchLabels:
      app: dm-3
  replicas: 2
  template:
    metadata:
      labels:  # 标签
        app: dm-3
        release: stabel
    spec:
      containers:
      - name: dm-3
        image: wangyanglinux/myapp:v3   # 对应的镜像仓库地址 如果是想设置公版本的可以设置 wangyanglinux/myapp:v2
        ports:
        - containerPort: 80

nginx-dm-service.yaml

apiVersion: v1
kind: Service
metadata:
  name: dm-3
  namespace: default
spec:
  type: ClusterIP
  selector: #匹配选择器
    app: dm-3   #对应的pod的deployment中的app标签名
    release: stabel
  ports:
  - name: http
    port: 80
    targetPort: 80

nginx-dm-ingress.yaml

apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:
  name: nginx-dm
spec:
  tls:
   - hosts:
     - www.dm-3.com
     secretName: tls-secret  # 加密方式
  rules:
    - host: www.dm-3.com
      http:
        paths:
        - path: /
          backend:
            serviceName: dm-3
            servicePort: 80

3.3 多域名配置ingress

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: nginx-deployment
spec:
  rules:
  - host: www.xxoo.com  
    http:
      paths:
      - backend:
          serviceName: nginx-deployment
          servicePort: 80
        path: /
  - host: www.nginx-dm.com
    http:
      paths:
      - backend:
          serviceName: nginx-dm
          servicePort: 80
        path: /

3.4 单个ingress绑定到不同的url

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: nginx-deployment
spec:
  rules:
  - host: www.xxoo.com
    http:
      paths:
      - path: /one
        backend:
          serviceName: nginx-deployment
          servicePort: 80
      - path: /two
        backend:
          serviceName: nginx-dm
          servicePort: 80

3.4、查看ing

ress-nginx的配置

  • 当我们配置完毕后可以查看 ingress-controller为我们自动添加的路径

  • 查看ngress-nginx 下的pod

kubectl get pod -n ingress-nginx
在这里插入图片描述

  • 找到ingress-nginx-controller 这个pod 然后进入其中

kubectl exec pod名称 -n 名称空间 -it – /bin//bash
eg:
kubectl exec ingress-nginx-controller-6bf5f5c696-sw958 -n ingress-nginx -it – /bin//bash

  • 进入pod找到ngin.conf既可看到controller为我们自动配置的信息

在这里插入图片描述

参考: https://www.kubernetes.org.cn/ingress

总结

提示：这里对文章进行总结：

Lovely_red_scarf
关注
  • 2
    点赞
  • 踩
  • 6
    收藏
    觉得还不错? 一键收藏
  • 打赏
    打赏
  • 0
    评论
专栏目录
quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.20.0镜像包
03-06
kubernetes的quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.20.0镜像包，版本为v0.20.0。文件先解压，之后得到nginx-ingress-controller.0.20.0.tar
ingress 多个path_使用Ingress来负载分发微服务
weixin_39613561的博客
12-27 5084
目录使用Ingress来负载分发微服务Demo规划准备Demo并完成部署创建部署(Deployment)资源创建服务(Service)资源创建Ingress资源并配置转发规则 使用Ingress来负载分发微服务NodePort Service存在太多缺陷，不适合生产环境。LoadBlancer Service则不太灵活，比如针对微服务架构，那么不同服务是否需要多个负...
k8s-ingress-实操
最新发布
little_startoo的博客
02-04 712
k8s-ingress-实操
kubernetes-ingress：适用于K8的HAProxy入口控制器
02-04
HAProxy Kubernetes入口控制器 描述 入口控制器是Kubernetes资源，可将流量从群集外部路由到群集内的服务。 详细文档可在找到。 您还可以在此存储库中找到所有可用的的列表。 用法 Docker镜像在Docker Hub上可用： 如果您更喜欢从源使用构建它 docker build -t haproxytech/kubernetes-ingress -f build/Dockerfile . 可以使用以下示例环境创建 deploy/kind/create.sh 请参阅以获取控制器图像的所有可用参数。 可用的自定义在进行了描述 文件中描述了运行控制器的基本设置。
aws-eks-kubernetes-masterclass:AWS EKS Kubernetes-大师班| DevOps，微服务
03-19
AWS EKS-Elastic Kubernetes服务-大师班 课程模块 序号 AWS服务名称 1。 使用eksctl CLI创建AWS EKS集群 2。 3。 4， 带有AWS EBS CSI驱动程序的EKS存储 5， Kubernetes应用程序部署的重要概念 5.1 Kubernetes-秘密 5.2 Kubernetes-初始化容器 5.3 Kubernetes-活力与就绪性探针 5.4 Kubernetes-请求和限制 5.5 Kubernetes-命名空间，限制范围和资源配额 6， 带有AWS RDS MySQL数据库的EKS存储 7 使用CLB和NLB进行负载平衡 7.1 使用CLB的负载平衡-AWS Classic Load Balancer 7.2 使用NLB进行负载平衡-AWS Network Load Balancer 8。 使用ALB的负载平衡-A
kubernetes-sample：kubernetes-sample
02-28
Kubernetesのお勉强 リソースの种类 Podとは・ ・ ・最小単位，同一环境で动作するDockerコンテナの集合１つのPodには复数のコンテナを设定できる。 ReplicaSetとは・ ・ ・ Podの集合，Podをスケールできる。 展开とは・ ・ ・ ReplicaSetの集合，ReplicaSetの世代管理ができる 服务・ ・ ・外部公开，名前解决，L4ロードバランサー ConfigMapとは・ ・ ・ Kubernetes上で利用する设定情报 秘密とは・ ・ ・ Kubernetes上で利用する机微情报 PersistentVolume（PV）・ PersistentVolumeCliam（PVC）とは・ ・ ・ PVが永続データの実体，PVCが永続データの要求 StatefulSetとは・ ・ ・ Podの集合，Podをスケールする际の名前が一定 Ingressとは・
k8s部署ingress-controller实战，以及path前缀配置的问题
qq_37437704的博客
12-13 4825
ingress与ingress-controller ingress与ingress-controller的相关简介就不多介绍了，本文只写实战环节 docker镜像准备 镜像下载 docker pull registry.cn-beijing.aliyuncs.com/google_registry/nginx-ingress-controller:0.30.0 有私有仓库的，可以重命名push到私有仓库。 部署ingress-controller pod及相关资源 给节点打赏标签 ku
ingress配置多域名
云深海阔专栏
06-27 828
通过调用nginx.ingress.kubernetes.io/server-alias接口，配置多个域名。kuboard配置如下图。
ingress实现同一域名加不同上下文实现两个服务的代理
wlh525的博客
03-21 1122
ingress配置同一域名不同上下文代理两个不同的业务
CC00166.CloudKubernetes——|KuberNetes&服务发布.V17|——|ingress.v05|创建多级域名ingress.pod|
yanqi_vip
03-30 500
一、创建一个多域名ingress ### --- 创建多域名ingress.yaml配置文件 [root@k8s-master01 ~]# vim ingress-mulDomain.yaml apiVersion: networking.k8s.io/v1beta1 # networking.k8s.io/v1 / extensions/v1beta1 kind: Ing...
kubernetes-ingress
03-08
Ingress是Kubernetes资源，可让您为在Kubernetes上运行的应用程序（由一个或多个表示）配置HTTP负载平衡器。 这样的负载平衡器对于将这些应用程序交付给Kubernetes集群之外的客户端是必需的。 Ingress资源支持以下...
k8s中通过ingress暴露多端口deployment
novice的博客
03-13 1495
项目中有一个notify微服务，业务逻辑上，需要在web界面上操作发送模板（微服务）、和推送（websocket），因此需要将后端的微服务和websocket同时对外暴露，前端web界面操作时需要走外网，同时实现微服务内部之间和notify访问，仍然走内网。
Kubernetes Ingress Nginx使用
weixin_34025151的博客
01-03 1387
在此我们不讲述如何部署ingress-controller，只演示如何使用ingress之nginx使用。主要演示如何使用ingress nginx实现我们nginx的多样化配置，从而达到使用ingress nginx如同使用手动部署nginx同样的便利。在此使用以下几个案例作讲解：案例1（基本转发，https配置与annotations基础使用）案例2（通过annotati...
K8S实战Day6-用Ingress配置服务发现
weixin_47315354的博客
12-29 759
文章目录前言一、Ingress是什么？二、Ingress安装1.Mandatoy.yaml总结 前言 一、Ingress是什么？ Ingress是管理外部网咯访问K8S集群中Service的API对象（典型就是HTTP），它可以提供负载均衡、SSL终端以及基于名字的虚拟host。简单点来说它就是外网访问集群应用的媒介。 +----------+ Ingress +---------+ | internet | ---------> | Service | +----------+
K8S通过Ingress用域名的方式对外网提供服务
lsysafe的博客
05-24 8899
1、环境准备： KBS已经部署了DNS插件，私有仓库等 2、编辑好如下配置文件，注意标红的部份 [root@k8s1 deploy]# cat namespace.yaml apiVersion: v1 kind: Namespace metadata: name: ingress-nginx [root@k8s1 deploy]# cat default-backend.yaml ...
1W字长文：K8S Ingress 原理和实操
架构师尼恩
03-29 1761
SVC、Ingress原理和实操，是云原生的基础知识。这里尼恩给大家 调优，做一下Ingress 的系统化、体系化的梳理，并收入尼恩的《K8S学习圣经》。
Ingress — Path
Jay_Fred的博客
02-06 400
Ingress — Path 语法规则及例子
Kubernetes：（十六）Ingress的概念和原理
ver_mouth__的博客
08-09 1657
ingress controller是一个pod服务，封装了一个web前端负载均衡器，同时在其基础上实现了动态感知ingress并根据ingress的定义生成前端web负载均衡器的配置文件，ingress-nginx-controller本质上就是一个nginx，只不过它能根据ingress资源定义的动态生成nginx的配置文件，然后动态reload。个人觉得ingress controller的重大作用是将前端负载均衡器和k8s完美地结合起来，一方面在云、容器平台下方便配置管理，另一方面实现了。...
nginx-ingress-controller
06-06
### 回答1： nginx-ingress-controller是一种用于Kubernetes集群的Ingress控制器，它使用Nginx作为反向代理来管理入站流量。它可以自动将Ingress资源转换为Nginx配置，并将流量路由到正确的后端服务。它还支持SSL终止、负载均衡、基于URI的路由和HTTP头的修改等功能。nginx-ingress-controller是Kubernetes社区中最受欢迎的Ingress控制器之一。

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

Lovely_red_scarf

你的鼓励将是我创作的最大动力

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付：¥1
获取中
扫码支付

您的余额不足，请更换扫码支付或充值

打赏作者

实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值