k8s教程05（Kubernetes Ingress）

已于 2022-06-02 16:58:10 修改
阅读量381 收藏
点赞数 1
分类专栏： kubernetes 文章标签： kubernetes nginx docker
于 2022-06-02 15:03:32 首次发布
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/DDJ_TEST/article/details/125100987
版权

Kubernetes Ingress

资料信息

Ingress-Nginx github地址： https://github.com/kubernetes/ingress-nginx
Ingress-Nginx官方网站： https://kubernetes.github.io/ingress-nginx/
在这里插入图片描述
在这里插入图片描述

部署Ingress-Nginx

kubectl apply -f mandatory.yaml
kubectl apply -f service-nodeport.yaml

[root@k8s-master01 ~]# cd /usr/local/install-k8s/plugin/
[root@k8s-master01 plugin]# ls
flannel
[root@k8s-master01 plugin]# mkdir ingress
[root@k8s-master01 plugin]# cd ingress/
[root@k8s-master01 ingress]#

在这里插入图片描述
在这里插入图片描述
kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.2.0/deploy/static/provider/cloud/deploy.yaml

[root@k8s-master01 ingress]# wget https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.2.0/deploy/static/provider/cloud/deploy.yaml
[root@k8s-master01 ingress]# cat deploy.yaml | grep image:
        image: k8s.gcr.io/ingress-nginx/controller:v1.2.0@sha256:d8196e3bc1e72547c5dec66d6556c0ff92a23f6d0919b206be170bc90d5f9185
        image: k8s.gcr.io/ingress-nginx/kube-webhook-certgen:v1.1.1@sha256:64d8c73dca984af206adf9d6d7e46aa550362b1d7a01f3a0a91b20cc67868660
        image: k8s.gcr.io/ingress-nginx/kube-webhook-certgen:v1.1.1@sha256:64d8c73dca984af206adf9d6d7e46aa550362b1d7a01f3a0a91b20cc67868660

上面是新版本
下面使用的是老版本的vi mandatory.yaml
wget https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/static/mandatory.yaml此链接已失效
新地址：https://gitee.com/WeiboGe2012/ingress-nginx/blob/nginx-0.25.0/deploy/static/mandatory.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
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:
      - "extensions"
      - "networking.k8s.io"
    resources:
      - ingresses
    verbs:
      - get
      - list
      - watch
  - apiGroups:
      - ""
    resources:
      - events
    verbs:
      - create
      - patch
  - 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: Deployment
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:
      serviceAccountName: nginx-ingress-serviceaccount
      containers:
        - name: nginx-ingress-controller
          image: quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.25.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
            - name: https
              containerPort: 443
          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

docker镜像安装完成后

[root@k8s-master01 ingress]# kubectl apply -f mandatory.yaml 
namespace/ingress-nginx created
configmap/nginx-configuration created
configmap/tcp-services created
configmap/udp-services created
serviceaccount/nginx-ingress-serviceaccount created
clusterrole.rbac.authorization.k8s.io/nginx-ingress-clusterrole created
role.rbac.authorization.k8s.io/nginx-ingress-role created
rolebinding.rbac.authorization.k8s.io/nginx-ingress-role-nisa-binding created
clusterrolebinding.rbac.authorization.k8s.io/nginx-ingress-clusterrole-nisa-binding created
deployment.apps/nginx-ingress-controller created
[root@k8s-master01 ingress]# kubectl get pod -n ingress-nginx
NAME                                        READY   STATUS    RESTARTS   AGE
nginx-ingress-controller-7995bd9c47-25md9   1/1     Running   0          38s

wget https://githubusercontent.com/kubernetes/ingress-nginx/master/deploy/static/provider/baremetal/service-nodeport.yaml此链接已失效
新地址：https://gitee.com/WeiboGe2012/ingress-nginx/blob/nginx-0.25.0/deploy/baremetal/service-nodeport.yaml
vi service-nodeport.yaml

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
    - name: https
      port: 443
      targetPort: 443
      protocol: TCP
  selector:
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/part-of: ingress-nginx
  externalTrafficPolicy: Cluster

[root@k8s-master01 ingress]# kubectl apply -f service-nodeport.yaml
service/ingress-nginx created
[root@k8s-master01 ingress]# kubectl get svc -n ingress-nginx
NAME            TYPE       CLUSTER-IP     EXTERNAL-IP   PORT(S)                      AGE
ingress-nginx   NodePort   10.107.32.66   <none>        80:32113/TCP,443:31526/TCP   8s

Ingress HTTP代理访问

deployment、Service、 Ingress Yaml文件
vi ingress.http.yaml

apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: nginx-dm
spec:
  replicas: 2
  template:
    metadata:
      labels:
        name: nginx
    spec:
      containers:
        - name: nginx
          image: wangyanglinux/myapp:v1
          imagePullPolicy: IfNotPresent
          ports:
            - containerPort: 80
---
apiVersion: v1
kind: Service
metadata:
  name: nginx-svc
spec:
  ports: 
    - port: 80
      targetPort: 80
      protocol: TCP
  selector:
    name: nginx

创建

[root@k8s-master01 ~]# kubectl apply -f ingress.http.yaml
deployment.extensions/nginx-dm created
service/nginx-svc created
[root@k8s-master01 ~]# kubectl get svc
NAME         TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)   AGE
kubernetes   ClusterIP   10.96.0.1      <none>        443/TCP   65m
nginx-svc    ClusterIP   10.103.0.192   <none>        80/TCP    6s
[root@k8s-master01 ~]# curl 10.103.0.192
Hello MyApp | Version: v1 | <a href="hostname.html">Pod Name</a>

删除操作（报错的话才使用）

[root@k8s-master01 ~]# kubectl delete svc --all
service "kubernetes" deleted
service "my-service-1" deleted
service "myapp" deleted
service "myapp-headless" deleted
service "nginx-svc" deleted
[root@k8s-master01 ~]# kubectl delete deployment --all
deployment.extensions "myapp-deploy" deleted
deployment.extensions "nginx-dm" deleted
[root@k8s-master01 ~]# kubectl delete deployment --all
deployment.extensions "nginx-dm" deleted
[root@k8s-master01 ~]# kubectl get deployment         
No resources found.

vi ingress1.yaml

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: nginx-test
spec:
  rules:
    - host: www1.atguigu.com
      http:
        paths:
        - path: /
          backend:
            serviceName: nginx-svc
            servicePort: 80

[root@k8s-master01 ~]# kubectl apply -f ingress1.yaml
ingress.extensions/nginx-test created
[root@k8s-master01 ~]# kubectl get svc -n ingress-nginx
NAME            TYPE       CLUSTER-IP     EXTERNAL-IP   PORT(S)                      AGE
ingress-nginx   NodePort   10.107.32.66   <none>        80:32113/TCP,443:31526/TCP   4m35s

打开浏览器访问：http://www1.atguigu.com:32113/
在这里插入图片描述

案例

在这里插入图片描述

[root@k8s-master01 ~]# kubectl get svc
NAME         TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)   AGE
kubernetes   ClusterIP   10.96.0.1      <none>        443/TCP   3h3m
nginx-svc    ClusterIP   10.103.0.192   <none>        80/TCP    117m
[root@k8s-master01 ~]# kubectl delete svc nginx-svc
service "nginx-svc" deleted
[root@k8s-master01 ~]# kubectl get svc
NAME         TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)   AGE
kubernetes   ClusterIP   10.96.0.1    <none>        443/TCP   3h5m
[root@k8s-master01 ~]# kubectl get deployment
NAME       READY   UP-TO-DATE   AVAILABLE   AGE
nginx-dm   2/2     2            2           120m
[root@k8s-master01 ~]# kubectl delete deployment --all
deployment.extensions "nginx-dm" deleted
[root@k8s-master01 ~]# kubectl get pod
No resources found.

[root@k8s-master01 ~]# mkdir ingress-vh
[root@k8s-master01 ~]# cd ingress-vh/
[root@k8s-master01 ingress-vh]# vi deployment1.yaml

vi deployment1.yaml

apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: deployment1
spec:
  replicas: 2
  template:
    metadata:
      labels:
        name: nginx
    spec:
      containers:
        - name: nginx
          image: wangyanglinux/myapp:v1
          imagePullPolicy: IfNotPresent
          ports:
            - containerPort: 80
---
apiVersion: v1
kind: Service
metadata:
  name: svc-1
spec:
  ports: 
    - port: 80
      targetPort: 80
      protocol: TCP
  selector:
    name: nginx

[root@k8s-master01 ingress-vh]# kubectl apply -f deployment1.yaml 
deployment.extensions/deployment1 created
service/svc-1 created
[root@k8s-master01 ingress-vh]# kubectl get svc
NAME         TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)   AGE
kubernetes   ClusterIP   10.96.0.1        <none>        443/TCP   3h15m
svc-1        ClusterIP   10.108.221.228   <none>        80/TCP    111s
[root@k8s-master01 ingress-vh]# curl 10.108.221.228
Hello MyApp | Version: v1 | <a href="hostname.html">Pod Name</a>

[root@k8s-master01 ingress-vh]# cp -a deployment1.yaml deployment2.yaml 
[root@k8s-master01 ingress-vh]# vi deployment2.yaml

vi deployment2.yaml

apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: deployment2
spec:
  replicas: 2
  template:
    metadata:
      labels:
        name: nginx2
    spec:
      containers:
        - name: nginx2
          image: wangyanglinux/myapp:v2
          imagePullPolicy: IfNotPresent
          ports:
            - containerPort: 80
---
apiVersion: v1
kind: Service
metadata:
  name: svc-2
spec:
  ports: 
    - port: 80
      targetPort: 80
      protocol: TCP
  selector:
    name: nginx2

[root@k8s-master01 ingress-vh]# kubectl apply -f deployment2.yaml 
deployment.extensions/deployment2 configured
service/svc-2 created
[root@k8s-master01 ingress-vh]# kubectl get svc                   
NAME         TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)   AGE
kubernetes   ClusterIP   10.96.0.1        <none>        443/TCP   3h24m
svc-1        ClusterIP   10.108.221.228   <none>        80/TCP    11m
svc-2        ClusterIP   10.100.152.109   <none>        80/TCP    5s
[root@k8s-master01 ingress-vh]# curl 10.100.152.109
Hello MyApp | Version: v2 | <a href="hostname.html">Pod Name</a>

vi ingressrule.yaml

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: ingress1
spec:
  rules:
    - host: www1.atguigu.com
      http:
        paths:
        - path: /
          backend:
            serviceName: svc-1
            servicePort: 80
---
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: ingress2
spec:
  rules:
    - host: www2.atguigu.com
      http:
        paths:
        - path: /
          backend:
            serviceName: svc-2
            servicePort: 80

[root@k8s-master01 ingress-vh]# kubectl apply -f ingressrule.yaml 
ingress.extensions/ingress1 created
ingress.extensions/ingress2 created
[root@k8s-master01 ingress-vh]# kubectl get pod
NAME                           READY   STATUS    RESTARTS   AGE
deployment1-7d967c7ff5-dqnc9   1/1     Running   0          17m
deployment1-7d967c7ff5-rjlkn   1/1     Running   0          17m
deployment2-659cdb8b84-rm4lb   1/1     Running   0          5m58s
deployment2-659cdb8b84-vnrzw   1/1     Running   0          5m58s
[root@k8s-master01 ingress-vh]# kubectl get pod -n ingress-nginx
NAME                                        READY   STATUS    RESTARTS   AGE
nginx-ingress-controller-7995bd9c47-25md9   1/1     Running   0          3h1m
[root@k8s-master01 ingress-vh]# kubectl exec nginx-ingress-controller-7995bd9c47-25md9 -n ingress-nginx -it -- /bin/bash
www-data@nginx-ingress-controller-7995bd9c47-25md9:/etc/nginx$ cat nginx.conf | grep 'start server'
        ## start server _
        ## start server www1.atguigu.com
        ## start server www2.atguigu.com
www-data@nginx-ingress-controller-7995bd9c47-25md9:/etc/nginx$ exit
exit
[root@k8s-master01 ingress-vh]#

在这里插入图片描述

[root@k8s-master01 ingress-vh]# kubectl get svc -n ingress-nginx
NAME            TYPE       CLUSTER-IP     EXTERNAL-IP   PORT(S)                      AGE
ingress-nginx   NodePort   10.107.32.66   <none>        80:32113/TCP,443:31526/TCP   154m

打开浏览器访问：www1.atguigu.com:32113
在这里插入图片描述
打开浏览器访问：www2.atguigu.com:32113
在这里插入图片描述

[root@k8s-master01 ingress-vh]# kubectl get ingress
NAME         HOSTS              ADDRESS   PORTS   AGE
ingress1     www1.atguigu.com             80      10m
ingress2     www2.atguigu.com             80      10m
nginx-test   www1.atguigu.com             80      153m
[root@k8s-master01 ingress-vh]# kubectl delete ingress nginx-test
ingress.extensions "nginx-test" deleted
[root@k8s-master01 ingress-vh]# kubectl get ingress
NAME       HOSTS              ADDRESS   PORTS   AGE
ingress1   www1.atguigu.com             80      88m
ingress2   www2.atguigu.com             80      88m

Ingress HTTPS代理访问

创建证书，以及cert存储方式
案例参考代码

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

deployment、Service、 Ingress Yaml文件

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: nginx-test
spec:
  tls:
    - hosts:
      - foo.bar.com
      secretName: tls-secret
  rules:
    - host: foo.bar.com
      http:
        paths:
        - path: /
          backend:
            serviceName: nginx-svc
            servicePort: 80

案例开始

[root@k8s-master01 ~]# mkdir https
[root@k8s-master01 ~]# cd https/
[root@k8s-master01 https]# openssl req -x509 -sha256 -nodes -days 365 -newkey rsa:2048 -keyout tls.key -out tls.crt -subj "/CN=nginxsvc/O=nginxsvc"
Generating a 2048 bit RSA private key
...................................................................................................................+++
.............+++
writing new private key to 'tls.key'
-----
[root@k8s-master01 https]# ls
tls.crt  tls.key
[root@k8s-master01 https]# kubectl create secret tls tls-secret --key tls.key --cert tls.crt
secret/tls-secret created

[root@k8s-master01 https]# cp ../ingress-vh/deployment1.yaml . 
[root@k8s-master01 https]# ls
deployment1.yaml  tls.crt  tls.key

[root@k8s-master01 https]# vi deployment1.yaml

vi deployment1.yaml

apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: deployment3
spec:
  replicas: 2
  template:
    metadata:
      labels:
        name: nginx3
    spec:
      containers:
        - name: nginx3
          image: wangyanglinux/myapp:v3
          imagePullPolicy: IfNotPresent
          ports:
            - containerPort: 80
---
apiVersion: v1
kind: Service
metadata:
  name: svc-3
spec:
  ports: 
    - port: 80
      targetPort: 80
      protocol: TCP
  selector:
    name: nginx3

[root@k8s-master01 https]# kubectl get pod
NAME                           READY   STATUS    RESTARTS   AGE
deployment1-7d967c7ff5-7sfn2   1/1     Running   0          12m
deployment1-7d967c7ff5-87t6s   1/1     Running   0          12m
deployment2-659cdb8b84-64lxg   1/1     Running   0          11m
deployment2-659cdb8b84-pfvbk   1/1     Running   0          11m
[root@k8s-master01 https]# kubectl get deployment
NAME          READY   UP-TO-DATE   AVAILABLE   AGE
deployment1   2/2     2            2           12m
deployment2   2/2     2            2           11m
[root@k8s-master01 https]# kubectl get svc
NAME         TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)   AGE
kubernetes   ClusterIP   10.96.0.1        <none>        443/TCP   14m
svc-1        ClusterIP   10.106.164.106   <none>        80/TCP    12m
svc-2        ClusterIP   10.101.111.202   <none>        80/TCP    11m
[root@k8s-master01 https]# kubectl apply -f deployment.yaml 
deployment.extensions/deployment3 created
service/svc-3 created
[root@k8s-master01 https]# kubectl get svc
NAME         TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)   AGE
kubernetes   ClusterIP   10.96.0.1        <none>        443/TCP   14m
svc-1        ClusterIP   10.106.164.106   <none>        80/TCP    13m
svc-2        ClusterIP   10.101.111.202   <none>        80/TCP    12m
svc-3        ClusterIP   10.105.96.244    <none>        80/TCP    7s
[root@k8s-master01 https]# curl 10.105.96.244
Hello MyApp | Version: v3 | <a href="hostname.html">Pod Name</a>

vi https.ingress.yaml

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: https
spec:
  tls:
    - hosts:
      - www3.atguigu.com
      secretName: tls-secret
  rules:
    - host: www3.atguigu.com
      http:
        paths:
        - path: /
          backend:
            serviceName: svc-3
            servicePort: 80

[root@k8s-master01 https]# kubectl apply -f https.ingress.yaml 
ingress.extensions/https created
[root@k8s-master01 https]# kubectl get svc
NAME         TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)   AGE
kubernetes   ClusterIP   10.96.0.1        <none>        443/TCP   20m
svc-1        ClusterIP   10.106.164.106   <none>        80/TCP    19m
svc-2        ClusterIP   10.101.111.202   <none>        80/TCP    18m
svc-3        ClusterIP   10.105.96.244    <none>        80/TCP    6m6s
[root@k8s-master01 https]# kubectl get svc -n ingress-nginx
NAME            TYPE       CLUSTER-IP     EXTERNAL-IP   PORT(S)                      AGE
ingress-nginx   NodePort   10.107.32.66   <none>        80:32113/TCP,443:31526/TCP   4h6m

在这里插入图片描述
打开浏览器访问：https://www3.atguigu.com:31526
在这里插入图片描述
在这里插入图片描述
在这里插入图片描述

Nginx进行BasicAuth

参考代码

yum -y install httpd
htpasswd -c auth foo
kubectl create secret generic basic-auth --from-file=auth

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: ingress-with-auth
  annotations:
    nginx.ingress.kubernetes.io/auth-type: basic
    nginx.ingress.kubernetes.io/auth-secret: basic-auth
    nginx.ingress.kubernetes.io/auth-realm: 'Authentication Required - foo'
spec:
  rules:
  - host: auth.atguigu.com
    http:
      paths:
      - path: /
        backend:
          serviceName: svc-1
          servicePort: 80

在这里插入图片描述

案例开始

[root@k8s-master01 ~]# cd 
[root@k8s-master01 ~]# mkdir basic-auth
[root@k8s-master01 ~]# cd basic-auth/
[root@k8s-master01 basic-auth]# htpasswd -c auth foo
New password: 		# 密码要记住 1111
Re-type new password:    # 密码要记住 1111
Adding password for user foo
[root@k8s-master01 basic-auth]# kubectl create secret generic basic-auth --from-file=auth
secret/basic-auth created
[root@k8s-master01 basic-auth]# vi ingress.yaml

vi ingress.yaml

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: ingress-with-auth
  annotations:
    nginx.ingress.kubernetes.io/auth-type: basic
    nginx.ingress.kubernetes.io/auth-secret: basic-auth
    nginx.ingress.kubernetes.io/auth-realm: 'Authentication Required - foo'
spec:
  rules:
  - host: auth.atguigu.com
    http:
      paths:
      - path: /
        backend:
          serviceName: svc-1
          servicePort: 80

[root@k8s-master01 basic-auth]# kubectl apply -f ingress.yaml 
ingress.extensions/ingress-with-auth created

在这里插入图片描述

[root@k8s-master01 basic-auth]# kubectl get svc -n ingress-nginx
NAME            TYPE       CLUSTER-IP     EXTERNAL-IP   PORT(S)                      AGE
ingress-nginx   NodePort   10.107.32.66   <none>        80:32113/TCP,443:31526/TCP   4h28m

打开浏览器访问：http://auth.atguigu.com:32113
在这里插入图片描述
在这里插入图片描述

Nginx进行重写

名称描述值
nginx.ingress.kubernetes.io/rewrite-target必须重定向流量的目标URI串
nginx.ingress.kubernetes.io/ssl-redirect指示位置部分是否仅可访问SSL (当Ingress包含证书时默认为True)布尔
nginx.ingress.kubernetes.io/force-ssl-redirect即便Ingress未启用TLS，也强制重定向到HTTPS布尔
nginx.ingress.kubernetes.io/app-root定义Controller必须重定向的应用程序根，如果它在/'上下文中串
nginx.ingress.kubernetes.io/use-regex指示Ingress.上定义的路径是否使用正则表达式布尔

vi re.yaml

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: nginx-test
  annotations : 
    nginx.ingress.kubernetes.io/rewrite-target: https://www3.atguigu.com:31526
spec:
  rules:
  - host: re.atguigu.com
    http:
      paths:
      - path: /
        backend:
          serviceName: svc-1
          servicePort: 80

[root@k8s-master01 re]# kubectl apply -f re.yaml 
ingress.extensions/nginx-test created

在这里插入图片描述
打开浏览器访问：http://re.atguigu.com:32113重定向到了https://www3.atguigu.com:31526/
在这里插入图片描述

已无测试机
关注
  • 1
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
k8s nginx-ingress灰度测试
qq_19757081的博客
04-14 2004
部署 pod1 自动产生service1 部署ingress1 部署pod2 自动产生service2 部署ingress2（基于header） 测试：正常访问打开pod1的nginx页面； 添加header头，打开pod2的nginx页面 基于权重的 基于cookie ...
k8s.zip kubernetes分享
03-30
Kubernetes，通常缩写为k8s，是一种流行的开源容器编排系统，用于自动化容器化应用程序的部署、扩展和管理。这个“k8s.zip kubernetes分享”提供的资源显然是一个全面的Kubernetes学习资料，旨在帮助用户从初学者...
入门级实操教程！从概念到部署，全方位了解K8S Ingress！
Rancher
12-13 1145
Ingress是Kubernetes中的重要组件。本文是一篇非常全面的入门级教程！从Ingress和Ingress Controller的概念开始，介绍了一些常用的Ingress controller，同时还给出架构图以帮助你理解ingress在K8s上的设置。最后手把手教你如何使用Nginx Ingress Controller在Kubernetes中设置Ingress。
k8s安装nginx Ingress超详细指南
最新发布
一览无遗
04-29 4437
在本全面的Ingress指南中，您将学习如何在 Kubernetes上并使用 DNS 配置 Ingress。目前有两种 Nginx Ingress 控制器。我们将使用 Kubernetes 社区 Nginx 控制器。Ingress & Nginx Ingress 控制器架构下面是使用 Nginx Ingress 控制器的 Kubernetes Ingress 的高级架构。在本指南中，我们将学习如何在体系结构中构建设置。​先决条件。
【云原生】k8s之Ingress
qq_62462797的博客
01-09 4505
service的作用体现在两个方面，对集群内部，它不断跟踪pod的变化，更新endpoint中对应pod的对象，提供了ip不断变化的pod的服务发现机制；对集群外部，他类似负载均衡器，可以在集群内外部对pod进行访问。在Kubernetes中，Pod的IP地址和service的ClusterIP仅可以在集群网络内部使用，对于集群外的应用是不可见的。
k8s ingress入门与实战
愿你的微笑化成风的专栏
09-26 1041
介绍了k8s(kubernetes) 中ingress、ingress-controller、ingress-nginx-controller的基础概念与基本使用
K8S(kubernetes)学习指南
03-19
Kubernetes（简称K8s）是Google开源的一种容器编排系统，用于自动化容器化的应用程序部署、扩展和管理。K8s以其强大的功能和易用性在云原生领域中占据了核心地位。以下是一份详细的K8S学习指南，涵盖多个关键知识点...
Kubernetes Ingress日志分析最佳实践.pptx
10-11
"Kubernetes Ingress日志分析最佳实践" Kubernetes Ingress日志分析是云原生应用程序的重要组件之一。随着容器化和微服务架构的普及，Kubernetes成为企业级容器编排的主要选择。然而，在Kubernetes集群中，日志分析...
Kubernetes Tutorials ｜ k8s 教程
11-21
k8s完整教程讲解： ...所以如果你对容器和 k8s 的基础理论知识不甚了解的话，建议先从 [官网文档](https://kubernetes.io/zh-cn/docs/home/) 或者其它教程获取基础理论知识，再通过实战加深对知识的掌握！
K8s外部网络访问之Ingress附件
10-25
在Kubernetes（K8s）集群中，Ingress是一种用于管理外部访问服务的重要机制，它提供了统一的入口点，使得外部网络可以方便地与内部运行的应用进行交互。本篇文章将详细探讨Kubernetes Ingress及其附件，帮助你理解...
如何使用K8S的Ingress
LegendHonor的博客
03-21 2142
如何使用K8S的Ingress Ingress的好处与特点我就没有必要再说一次了，本文主要说明的是使用方法 准备条件 请先完成K8S的安装，安装ingress，它包括一个defaulebackend，与nginx-ingress-control,并pull下需要的docker image 注意 这里请注意一点，为了方便，我们希望在部署ingress的时候，将部署文件Ymal中的一个条目修改 修改y...
【一起来学kubernetes】7、k8s中的ingress详解
技术人集结地
11-25 4086
通常情况下，Ingress部署在所有的Node节点上，可以配置提供服务外部访问的URL、负载均衡、终止SSL，并提供基于域名的虚拟主机，但它不会暴露任意端口或协议。需要注意的是，Nginx类型的Ingress实现可以通过扩展Nginx Ingress Controller来实现更多的功能，比如认证、限流、重定向等。需要注意的是，Ingress的实现方案可能会因所选的Ingress控制器而有所不同。需要注意的是，Istio类型的Ingress实现具有强大的流量管理和安全功能，但也需要更多的配置和维护工作。
云原生K8S之Ingress的使用
tianlong1569的专栏
02-22 1145
1、官方Ingress介绍 Ingress | KubernetesFEATURE STATE: Kubernetes v1.19 [stable] An API object that manages external access to the services in a cluster, typically HTTP. aka: tags: - networking - architecture - extension --- -- Ingress 是对集群中服务的外部访问进行管理的 API 对象.
【K8S系列】第十三讲：Ingress详解
热门推荐
颜淡慕潇
12-23 2万+
NotePortIngressNodePort方式：最大的缺点是会占用很多集群机器的端口，而且需要在外部搭建额外的负载均衡；LB方式：最大的缺点则是每个service一个LB，有点浪费，并且需要k8s之外的支持，【eg:cloud provider】；ingress： Ingress就是为了解决1,2两种方式的限制，只需要一个NodePort或者一个LB就可以满足所有service对外服务的需求。
小笔记-简单但够用系列_K8S快速入门-Ingress安装使用
迷途小羔羊--NYTWTYN的博客
08-04 590
文章目录安装 Ingress安装 ingress-nginx创建 ingress-nginx 规则文件应用 ingress-nginx 规则查看 ingress-nginx 相关信息删除规则一些问题 安装 Ingress Ingress 是非 k8s 内置的服务，可完成服务暴露，使可通过访问域名的方式连接pod。Ingress是k8s集群的一个API资源对象，相当于一个集群网关，可设置自定义路由规则进行转发、管理、暴露服务等。 Ingress有多个类型版本，以官方维护的 Ingress-nginx 为例。
有了这个网络安全面试题，面试就像开了挂！（附PDF）
lvaolan的博客
02-26 606
还有兄弟不知道网络安全面试可以提前刷题吗？费时一周整理的160+网络安全面试题，金九银十，做网络安全面试里的显眼包！王岚嵚工程师面试题（附答案），只能帮兄弟们到这儿了！如果你能答对70%，找一个安全工作，问题不大。对于有1-3年工作经验，想要跳槽的朋友来说，也是很好的温习资料！【完整版领取方式在文末！！​​​​内容实在太多，不一一截图了。
（2022版）一套教程搞定k8s安装到实战 | Ingress
COCO_gsta的博客
08-20 5612
视频来源：B站《（2022版）最新、最全、最详细的（K8s）教程，从K8s安装到实战一套搞定》
k8s 测试七 Ingress
王佳宇的个人博客
03-08 1418
Ingress 官网： https://kubernetes.github.io/ingress-nginx/deploy/ kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/nginx-0.30.0/deploy/static/mandatory.yaml kubectl ...
k8s部署nginx-ingress
10-13
要在k8s上部署nginx-ingress，可以按照以下步骤进行： 1. 安装helm：`curl https://raw.githubusercontent.com/kubernetes/helm/master/scripts/get > get_helm.sh`，`chmod 700 get_helm.sh`，`./get_helm.sh` 2....
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值