Kubernetes 1.20.5实验记录--Service & Ingress

最新推荐文章于 2022-08-14 20:37:45 发布
最新推荐文章于 2022-08-14 20:37:45 发布
阅读量284 收藏 1
点赞数
分类专栏： Kubernetes 文章标签： kubernetes
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/mengshicheng1992/article/details/118002262
版权

Kubernetes 1.20.5实验记录–Service & Ingress

1.1 Service

1.1.1 Service Backend

1、创建Deployment：

文件deploy.yaml

apiVersion: apps/v1
kind: Deployment
metadata:
  name: deploy
spec:
  replicas: 6
  selector:
    matchLabels:
      run: deploy
  template:
    metadata:
      labels:
        run: deploy
    spec:
      containers:
      - name: deploy
        image: nginx

kubectl apply -f deploy.yaml

在这里插入图片描述

此Deployment作为以下Service Backend

1.1.2 ClusterIP

1、创建ClusterIP类型Service：

文件service-clusterip.yaml

apiVersion: v1
kind: Service
metadata:
  name: service-clusterip
spec:
  ports:
  - name: 8080-80
    port: 8080
    protocol: TCP
    targetPort: 80
  selector:
    run: deploy
  type: ClusterIP

kubectl apply -f service-clusterip.yaml

在这里插入图片描述

2、查看Service：

kubectl get service

在这里插入图片描述

3、查看Service与Pod的对应关系：

kubectl get endpoints service-clusterip

在这里插入图片描述

4、查看Service详细信息：

kubectl describe service service-clusterip

在这里插入图片描述

5、测试ClusterIP类型Service：

curl 10.107.209.147:8080

在这里插入图片描述

6、删除ClusterIP类型Service：

kubectl delete -f service-clusterip.yaml

在这里插入图片描述

1.1.3 NodePort

1、创建NodePort类型Service：

文件service-nodeport.yaml

apiVersion: v1
kind: Service
metadata:
  name: service-nodeport
spec:
  ports:
  - name: 8080-80
    port: 8080
    protocol: TCP
    targetPort: 80
    nodePort: 30303
  selector:
    run: deploy
  type: NodePort

kubectl apply -f service-nodeport.yaml

在这里插入图片描述

2、查看Service：

kubectl get service

在这里插入图片描述

3、查看Service与Pod的对应关系：

kubectl get endpoints service-nodeport

在这里插入图片描述

4、查看Service详细信息：

kubectl describe service service-nodeport

在这里插入图片描述

5、测试NodePort类型Service：

curl 192.168.0.11:30303

在这里插入图片描述

6、删除NodePort类型Service：

kubectl delete -f service-nodeport.yaml

在这里插入图片描述

1.1.4 Headless

1、创建Headless类型Service：

文件service-headless.yaml

apiVersion: v1
kind: Service
metadata:
  name: service-headless
spec:
  clusterIP: None
  selector:
    run: deploy
  type: ClusterIP

kubectl apply -f service-headless.yaml

在这里插入图片描述

2、查看Service：

kubectl get service

在这里插入图片描述

3、查看Service与Pod的对应关系：

kubectl get endpoints service-headless

在这里插入图片描述

4、查看Service详细信息：

kubectl describe service service-headless

在这里插入图片描述

5、测试Headless类型Service：

kubectl create -f https://k8s.io/examples/admin/dns/busybox.yaml

在这里插入图片描述

kubectl exec -it busybox -- nslookup service-headless

在这里插入图片描述

6、删除Headless类型Service：

kubectl delete -f service-headless.yaml

在这里插入图片描述

7、删除Deployment：

kubectl delete -f deploy.yaml

在这里插入图片描述

1.2 Ingress

1.2.1 Nginx Ingress（HTTP）

1、创建Deployment：

文件nginx-deploy.yaml

apiVersion: apps/v1
kind: Deployment
metadata: 
  labels:
    run: nginx-deploy
  name: nginx-deploy
spec:
  replicas: 6
  selector: 
    matchLabels:
      run: nginx-deploy
  template:
    metadata:
      labels:
        run: nginx-deploy
    spec:
      containers:
      - name: nginx-deploy
        image: nginx 
        ports:
        - name: nginx
          containerPort: 80

kubectl apply -f nginx-deploy.yaml

在这里插入图片描述

2、查看Pod状态：

kubectl get pod -o wide

在这里插入图片描述

3、创建Service：

文件nginx-service.yaml

apiVersion: v1
kind: Service
metadata:
  name: nginx-service
spec:
  type: ClusterIP
  ports:
    - name: http
      port: 80
      targetPort: 80
      protocol: TCP
  selector:
    run: nginx-deploy

kubectl apply -f nginx-service.yaml

在这里插入图片描述

4、查看Service状态：

kubectl get service

在这里插入图片描述

5、创建Ingress控制器：

文件mandatory.yaml

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

---

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

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

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

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

---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  name: nginx-ingress-clusterrole
  labels:
    app.kubernetes.io/name: nginx-ingress
    app.kubernetes.io/part-of: nginx-ingress
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/v1
kind: Role
metadata:
  name: nginx-ingress-role
  namespace: nginx-ingress
  labels:
    app.kubernetes.io/name: nginx-ingress
    app.kubernetes.io/part-of: nginx-ingress
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/v1
kind: RoleBinding
metadata:
  name: nginx-ingress-role-nisa-binding
  namespace: nginx-ingress
  labels:
    app.kubernetes.io/name: nginx-ingress
    app.kubernetes.io/part-of: nginx-ingress
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: Role
  name: nginx-ingress-role
subjects:
  - kind: ServiceAccount
    name: nginx-ingress-serviceaccount
    namespace: nginx-ingress

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

---

apiVersion: apps/v1
kind: Deployment
metadata:
  name: nginx-ingress-controller
  namespace: nginx-ingress
  labels:
    app.kubernetes.io/name: nginx-ingress
    app.kubernetes.io/part-of: nginx-ingress
spec:
  replicas: 1
  selector:
    matchLabels:
      app.kubernetes.io/name: nginx-ingress
      app.kubernetes.io/part-of: nginx-ingress
  template:
    metadata:
      labels:
        app.kubernetes.io/name: nginx-ingress
        app.kubernetes.io/part-of: nginx-ingress
      annotations:
        prometheus.io/port: "10254"
        prometheus.io/scrape: "true"
    spec:
      # wait up to five minutes for the drain of connections
      terminationGracePeriodSeconds: 300
      serviceAccountName: nginx-ingress-serviceaccount
      nodeSelector:
        kubernetes.io/os: linux
      containers:
        - name: nginx-ingress-controller
          image: mengshicheng/nginx-ingress-controller:0.30.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)/nginx-ingress
            - --annotations-prefix=nginx.ingress.kubernetes.io
          securityContext:
            allowPrivilegeEscalation: true
            capabilities:
              drop:
                - ALL
              add:
                - NET_BIND_SERVICE
            # www-data -> 101
            runAsUser: 101
          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
          readinessProbe:
            failureThreshold: 3
            httpGet:
              path: /healthz
              port: 10254
              scheme: HTTP
            periodSeconds: 10
            successThreshold: 1
            timeoutSeconds: 10
          lifecycle:
            preStop:
              exec:
                command:
                  - /wait-shutdown

---

apiVersion: v1
kind: LimitRange
metadata:
  name: nginx-ingress
  namespace: nginx-ingress
  labels:
    app.kubernetes.io/name: nginx-ingress
    app.kubernetes.io/part-of: nginx-ingress
spec:
  limits:
  - min:
      memory: 90Mi
      cpu: 100m
    type: Container

kubectl apply -f mandatory.yaml

在这里插入图片描述

6、查看Ingress控制器状态：

kubectl get pod -o wide -n nginx-ingress

在这里插入图片描述

7、创建Ingress转发规则：

文件nginx-ingress.yaml

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: nginx-ingress
  annotations: 
    kubernetes.io/ingress.class: "nginx"
spec:
  rules:
  - host: mengshicheng.io 
    http:
      paths:
      - path: /
        pathType: Prefix
        backend:
          service:
            name: nginx-service
            port:
              number: 80

kubectl apply -f nginx-ingress.yaml

在这里插入图片描述

8、查看Ingress状态：

kubectl get ingress

在这里插入图片描述

9、创建Ingress Service：

文件ingress-service.yaml

apiVersion: v1
kind: Service
metadata:
  name: ingress-service
  namespace: nginx-ingress
  labels:
    app.kubernetes.io/name: nginx-ingress
    app.kubernetes.io/part-of: nginx-ingress
spec:
  type: NodePort
  ports:
    - name: http
      port: 80
      targetPort: 80
      protocol: TCP
  selector:
    app.kubernetes.io/name: nginx-ingress
    app.kubernetes.io/part-of: nginx-ingress

kubectl apply -f ingress-service.yaml

在这里插入图片描述

10、查看Ingress Service：

kubectl get service -n nginx-ingress

在这里插入图片描述

11、测试Ingress：

在这里插入图片描述

12、删除Ingress Service：

kubectl delete -f ingress-service.yaml

在这里插入图片描述

13、删除Ingress转发规则：

kubectl delete -f nginx-ingress.yaml

在这里插入图片描述

14、删除Ingress控制器：

kubectl delete -f mandatory.yaml

在这里插入图片描述

15、删除Service：

kubectl delete -f nginx-service.yaml

在这里插入图片描述

16、删除Deployment：

kubectl delete -f nginx-deploy.yaml

在这里插入图片描述

1.2.2 Nginx Ingress（HTTPS）

1、创建HTTPS证书

openssl genrsa -out tls.key 2048

在这里插入图片描述

openssl req -new -x509 -key tls.key -out tls.crt -subj /C=CN/ST=Beijing/L=Beijing/O=K8S/CN=mengshicheng.io

在这里插入图片描述

kubectl create secret tls nginx-ingress-secret --cert=tls.crt --key=tls.key

在这里插入图片描述

kubectl get secret

在这里插入图片描述

kubectl describe secret nginx-ingress-secret

在这里插入图片描述

2、创建Deployment：

文件nginx-deploy.yaml

apiVersion: apps/v1
kind: Deployment
metadata: 
  labels:
    run: nginx-deploy
  name: nginx-deploy
spec:
  replicas: 6
  selector: 
    matchLabels:
      run: nginx-deploy
  template:
    metadata:
      labels:
        run: nginx-deploy
    spec:
      containers:
      - name: nginx-deploy
        image: nginx 
        ports:
        - name: nginx
          containerPort: 80

kubectl apply -f nginx-deploy.yaml

在这里插入图片描述

3、查看Pod状态：

kubectl get pod -o wide

在这里插入图片描述

4、创建Service：

文件nginx-service.yaml

apiVersion: v1
kind: Service
metadata:
  name: nginx-service
spec:
  type: ClusterIP
  ports:
    - name: http
      port: 80
      targetPort: 80
      protocol: TCP
  selector:
    run: nginx-deploy

kubectl apply -f nginx-service.yaml

在这里插入图片描述

4、查看Service状态：

kubectl get service

在这里插入图片描述

5、创建Ingress控制器：

文件mandatory.yaml

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

---

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

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

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

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

---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  name: nginx-ingress-clusterrole
  labels:
    app.kubernetes.io/name: nginx-ingress
    app.kubernetes.io/part-of: nginx-ingress
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/v1
kind: Role
metadata:
  name: nginx-ingress-role
  namespace: nginx-ingress
  labels:
    app.kubernetes.io/name: nginx-ingress
    app.kubernetes.io/part-of: nginx-ingress
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/v1
kind: RoleBinding
metadata:
  name: nginx-ingress-role-nisa-binding
  namespace: nginx-ingress
  labels:
    app.kubernetes.io/name: nginx-ingress
    app.kubernetes.io/part-of: nginx-ingress
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: Role
  name: nginx-ingress-role
subjects:
  - kind: ServiceAccount
    name: nginx-ingress-serviceaccount
    namespace: nginx-ingress

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

---

apiVersion: apps/v1
kind: Deployment
metadata:
  name: nginx-ingress-controller
  namespace: nginx-ingress
  labels:
    app.kubernetes.io/name: nginx-ingress
    app.kubernetes.io/part-of: nginx-ingress
spec:
  replicas: 1
  selector:
    matchLabels:
      app.kubernetes.io/name: nginx-ingress
      app.kubernetes.io/part-of: nginx-ingress
  template:
    metadata:
      labels:
        app.kubernetes.io/name: nginx-ingress
        app.kubernetes.io/part-of: nginx-ingress
      annotations:
        prometheus.io/port: "10254"
        prometheus.io/scrape: "true"
    spec:
      # wait up to five minutes for the drain of connections
      terminationGracePeriodSeconds: 300
      serviceAccountName: nginx-ingress-serviceaccount
      nodeSelector:
        kubernetes.io/os: linux
      containers:
        - name: nginx-ingress-controller
          image: mengshicheng/nginx-ingress-controller:0.30.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)/nginx-ingress
            - --annotations-prefix=nginx.ingress.kubernetes.io
          securityContext:
            allowPrivilegeEscalation: true
            capabilities:
              drop:
                - ALL
              add:
                - NET_BIND_SERVICE
            # www-data -> 101
            runAsUser: 101
          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
          readinessProbe:
            failureThreshold: 3
            httpGet:
              path: /healthz
              port: 10254
              scheme: HTTP
            periodSeconds: 10
            successThreshold: 1
            timeoutSeconds: 10
          lifecycle:
            preStop:
              exec:
                command:
                  - /wait-shutdown

---

apiVersion: v1
kind: LimitRange
metadata:
  name: nginx-ingress
  namespace: nginx-ingress
  labels:
    app.kubernetes.io/name: nginx-ingress
    app.kubernetes.io/part-of: nginx-ingress
spec:
  limits:
  - min:
      memory: 90Mi
      cpu: 100m
    type: Container

kubectl apply -f mandatory.yaml

在这里插入图片描述

6、查看Ingress控制器状态：

kubectl get pod -o wide -n nginx-ingress

在这里插入图片描述

7、创建Ingress转发规则：

文件nginx-ingress-tls.yaml

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: nginx-ingress-tls
  annotations: 
    kubernetes.io/ingress.class: "nginx"
spec:
  tls:
  - hosts:
    - mengshicheng.io
    secretName: nginx-ingress-secret
  rules:
  - host: mengshicheng.io 
    http:
      paths:
      - path: /
        pathType: Prefix
        backend:
          service:
            name: nginx-service
            port:
              number: 80

kubectl apply -f nginx-ingress-tls.yaml

在这里插入图片描述

8、查看Ingress状态：

kubectl get ingress

在这里插入图片描述

9、创建Ingress Service：

文件ingress-service.yaml

apiVersion: v1
kind: Service
metadata:
  name: ingress-service
  namespace: nginx-ingress
  labels:
    app.kubernetes.io/name: nginx-ingress
    app.kubernetes.io/part-of: nginx-ingress
spec:
  type: NodePort
  ports:
    - name: https
      port: 443
      targetPort: 443
      protocol: TCP
  selector:
    app.kubernetes.io/name: nginx-ingress
    app.kubernetes.io/part-of: nginx-ingress

kubectl apply -f ingress-service.yaml

在这里插入图片描述

10、查看Ingress Service：

kubectl get service -n nginx-ingress

在这里插入图片描述

11、测试Ingress：

在这里插入图片描述

12、删除Ingress Service：

kubectl delete -f ingress-service.yaml

在这里插入图片描述

13、删除Ingress转发规则：

kubectl delete -f nginx-ingress-tls.yaml

在这里插入图片描述

14、删除Ingress控制器：

kubectl delete -f mandatory.yaml

在这里插入图片描述

15、删除Service：

kubectl delete -f nginx-service.yaml

在这里插入图片描述

16、删除Deployment：

kubectl delete -f nginx-deploy.yaml

在这里插入图片描述

17、删除HTTPS证书

kubectl delete secret nginx-ingress-secret

在这里插入图片描述

mengshicheng1992
关注
  • 0
    点赞
  • 踩
  • 1
    收藏
    觉得还不错? 一键收藏
  • 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
k8s教程（service篇）-ingress 7层路由机制
梦想起飞的地方.........
04-17 1716
一个ingress资源对象的定义如下：metadata:spec:rules:http:paths:backend:service:port:Ingress资源主要用于定义路由转发规则，可以包含多条转发规则的定义，通​​进行设置。下面对其中的关键配置进行说明。
kubernetes1.20 Ingress配置方式
运维那些事儿
06-06 2985
Ingress 是什么？ Ingress 公开了从集群外部到集群内服务的 HTTP 和 HTTPS 路由。 流量路由由 Ingress 资源上定义的规则控制。 下面是一个将所有流量都发送到同一 Service 的简单 Ingress 示例： 可以将 Ingress 配置为服务提供外部可访问的 URL、负载均衡流量、终止 SSL/TLS，以及提供基于名称的虚拟主机等能力。 Ingress 控制器 通常负责通过负载均衡器来实现 Ingress，尽管它也可以配置边缘路由器或其他前端来帮助处理流量。 Ingres
Kubernetes K8S之Ingress详解与示例
踏歌行的专栏
09-23 1万+
K8S之Ingress概述与说明，并详解Ingress常用示例
k8s 裸机安装 nginx1.19 ingrass
技术博客
11-05 1012
k8s 裸机安装 nginx1.19 ingrass deploy.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-
k8s.gcr.io-ingress-nginx-controller-v0.41.2.tar
02-08
k8s.gcr.io-ingress-nginx-controller-v0.41.2.tar
Kubernetes 1.19.4安装Nginx-Ingress-Controller
12-17
Kubernetes 1.19.4安装Nginx-Ingress-Controller全套资源 包含以下内容： deploy.yml jettech-kube-webhook-certgen-v1.5.0.tar k8s.gcr.io-ingress-nginx-controller-v0.41.2.tar nginx-1.19.5.tar
ingress-nginx-controller-1.9.yaml
最新发布
10-18
三处image需要修改（若官方deplo.yaml中的image可以拉取，则不需要改image），另两个文件是测试ingress规则是否生效的yaml。
NGINX Ingress Controller:用于 Kubernetes 的 NGINX 入口控制器-开源
08-08
ingress-nginx 是 Kubernetes 的入口控制器，使用 NGINX 作为反向代理和负载均衡器。 它围绕 Kubernetes Ingress 资源构建，使用 ConfigMap 来存储 NGINX 配置。 这个 Ingress 控制器的目标是组装一个配置文件...
kubernetes-1-20:展示在Kubernetes 1.20上使用Container Ingress Services与BIGIP集成的示例
04-05
kubernetes-1-20 展示在Kubernetes 1.20上使用Container Ingress Services与BIGIP集成的示例
Kubernetes--Service详解
Hud的博客
04-26 746
在kubernetes中，pod是应用程序的载体，我们可以通过pod的ip来访问应用程序，但是pod的ip地址不是固定的，这也就意味着不方便直接采用pod的ip对服务进行访问。 为了解决这个问题，kubernetes提供了Service资源，Service会对提供同一个服务的多个pod进行聚合，并且提供一个统一的入口地址。通过访问Service的入口地址就能访问到后面的pod服务。 Service在很多情况下只是一个概念，真正起作用的其实是kube-proxy服务进程，每个Node节点上都运行.
rke部署k8s_v1.20.15高可用
planck
03-01 2124
使用的镜像： rancher/mirrored-coreos-etcd:v3.4.15-rancher1 rancher/rke-tools:v0.1.78 rancher/mirrored-cluster-proportional-autoscaler:1.8.1 rancher/mirrored-coredns-coredns:1.8.0 rancher/hyperkube:v1.20.12-rancher1 rancher/mirrored-calico-node:v3.17.2 ran
kubernetes-v1.20.4 二进制部署-rancher-v2.5.1、harbor
人走茶良的博客
07-09 1083
一、部署ingress-nginx 一、部署ingress-nginx 获取最新更新以及文章用到的软件包，请移步点击：查看更新 　　rancher默认使用ingress暴露UI到集群外部供用户访问，所以需要自行部署ingress-controller，以部署ingress-nginx-controller为例。 　　1、安装helm version=v3.3.1 #从华为开源镜像站下载 curl -LO curl -LO https://repo.huaweicloud.com/hel...
【云原生】DevOps（七）：Kubernetes编排工具
Hello大家好，我是Dream，如果帮得到你，那我深感荣幸！
08-14 1885
【云原生】DevOps（七）：Kubernetes编排工具
kubernetes1.20搭建ingress遇到failed calling webhook “validate.nginx.ingress.kubernetes.io“
Ackerly Xu的博客
01-10 2100
kubernetes1.20搭建ingress遇到failed calling webhook "validate.nginx.ingress.kubernetes.io" 原因在:https://blog.51cto.com/juestnow/2493608,需要改为ipv6。 但由于没有ipFamily属性,原来service现在有个属性ipFamilyPolicy:https://kubernetes.io/docs/concepts/services-networking/dual-stack/
k8s 对外服务之ingress
热门推荐
yrx420909的博客
04-24 5万+
1. ingress概述 k8s 对外暴露服务（service）主要有两种方式：NotePort, LoadBalance， 此外externalIPs也可以使各类service对外提供服务，但是当集群服务很多的时候，NodePort方式最大的缺点是会占用很多集群机器的端口；LB方式最大的缺点则是每个service一个LB又有点浪费和麻烦，并且需要k8s之外的支持； 而ingress则只需要一个N...
K8s系列之：部署ingress
zhengzaifeidelushang的博客
03-28 1799
kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.1.2/deploy/static/provider/cloud/deploy.yaml #GENERATED FOR K8S 1.20 apiVersion: v1 kind: Namespace metadata: labels: app.kubernetes.io/instance: ingress-nginx
本地搭建K8s环境，并配置Ingress代理（1）
dotNET跨平台
09-01 565
书接上文，上回说到了在Linux系统搭建K8s环境，通过脚本一键处理，具体可参考《入门K8s：一键脚本搭建Linux服务器集群》。虽然Linux系统很不错，而且也推荐都买一个做练习，但是不...
apiVersion: v1 kind: Service metadata: labels: app.kubernetes.io/component: controller app.kubernetes.io/instance: ingress-nginx app.kubernetes.io/name: ingress-nginx app.kubernetes.io/part-of: ingress-nginx app.kubernetes.io/version: 1.6.4 name: ingress-nginx-controller namespace: ingress-nginx spec: externalTrafficPolicy: Local ipFamilies: - IPv4 ipFamilyPolicy: SingleStack ports: - appProtocol: http name: http port: 80 protocol: TCP targetPort: http - appProtocol: https name: https port: 443 protocol: TCP targetPort: https selector: app.kubernetes.io/component: controller app.kubernetes.io/instance: ingress-nginx app.kubernetes.io/name: ingress-nginx type: NodePort 指定targetPort
06-06
在上述配置中，targetPort 是用来指定 Service 要代理的后端 Pod 的端口号。在这个例子中，Service 会将请求代理到后端 Pod 的 80 端口（targetPort: http）或 443 端口（targetPort: https）。这里的 targetPort 要...

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

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

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

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

余额充值