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:d8196e3bc1e72547c5dec66d6556c0ff92a23f6d0919b206be170bc90d5f9185image: k8s.gcr.io/ingress-nginx/kube-webhook-certgen:v1.1.1@sha256:64d8c73dca984af206adf9d6d7e46aa550362b1d7a01f3a0a91b20cc67868660image: 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-nginxlabels:app.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginx
---kind: ConfigMap
apiVersion: v1
metadata:name: nginx-configurationnamespace: ingress-nginxlabels:app.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginx---
kind: ConfigMap
apiVersion: v1
metadata:name: tcp-servicesnamespace: ingress-nginxlabels:app.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginx---
kind: ConfigMap
apiVersion: v1
metadata:name: udp-servicesnamespace: ingress-nginxlabels:app.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginx---
apiVersion: v1
kind: ServiceAccount
metadata:name: nginx-ingress-serviceaccountnamespace: ingress-nginxlabels:app.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginx---
apiVersion: rbac.authorization.k8s.io/v1beta1
kind: ClusterRole
metadata:name: nginx-ingress-clusterrolelabels:app.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginx
rules:- apiGroups:- ""resources:- configmaps- endpoints- nodes- pods- secretsverbs:- list- watch- apiGroups:- ""resources:- nodesverbs:- get- apiGroups:- ""resources:- servicesverbs:- get- list- watch- apiGroups:- "extensions"- "networking.k8s.io"resources:- ingressesverbs:- get- list- watch- apiGroups:- ""resources:- eventsverbs:- create- patch- apiGroups:- "extensions"- "networking.k8s.io"resources:- ingresses/statusverbs:- update---
apiVersion: rbac.authorization.k8s.io/v1beta1
kind: Role
metadata:name: nginx-ingress-rolenamespace: ingress-nginxlabels:app.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginx
rules:- apiGroups:- ""resources:- configmaps- pods- secrets- namespacesverbs:- get- apiGroups:- ""resources:- configmapsresourceNames:# 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:- configmapsverbs:- create- apiGroups:- ""resources:- endpointsverbs:- get---
apiVersion: rbac.authorization.k8s.io/v1beta1
kind: RoleBinding
metadata:name: nginx-ingress-role-nisa-bindingnamespace: ingress-nginxlabels:app.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginx
roleRef:apiGroup: rbac.authorization.k8s.iokind: Rolename: nginx-ingress-role
subjects:- kind: ServiceAccountname: nginx-ingress-serviceaccountnamespace: ingress-nginx---
apiVersion: rbac.authorization.k8s.io/v1beta1
kind: ClusterRoleBinding
metadata:name: nginx-ingress-clusterrole-nisa-bindinglabels:app.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginx
roleRef:apiGroup: rbac.authorization.k8s.iokind: ClusterRolename: nginx-ingress-clusterrole
subjects:- kind: ServiceAccountname: nginx-ingress-serviceaccountnamespace: ingress-nginx---apiVersion: apps/v1
kind: Deployment
metadata:name: nginx-ingress-controllernamespace: ingress-nginxlabels:app.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginx
spec:replicas: 1selector:matchLabels:app.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginxtemplate:metadata:labels:app.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginxannotations:prometheus.io/port: "10254"prometheus.io/scrape: "true"spec:serviceAccountName: nginx-ingress-serviceaccountcontainers:- name: nginx-ingress-controllerimage: 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.iosecurityContext:allowPrivilegeEscalation: truecapabilities:drop:- ALLadd:- NET_BIND_SERVICE# www-data -> 33runAsUser: 33env:- name: POD_NAMEvalueFrom:fieldRef:fieldPath: metadata.name- name: POD_NAMESPACEvalueFrom:fieldRef:fieldPath: metadata.namespaceports:- name: httpcontainerPort: 80- name: httpscontainerPort: 443livenessProbe:failureThreshold: 3httpGet:path: /healthzport: 10254scheme: HTTPinitialDelaySeconds: 10periodSeconds: 10successThreshold: 1timeoutSeconds: 10readinessProbe:failureThreshold: 3httpGet:path: /healthzport: 10254scheme: HTTPperiodSeconds: 10successThreshold: 1timeoutSeconds: 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-nginxnamespace: ingress-nginxlabels:app.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginx
spec:type: NodePortports:- name: httpport: 80targetPort: 80protocol: TCP- name: httpsport: 443targetPort: 443protocol: TCPselector:app.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginxexternalTrafficPolicy: 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: 2template:metadata:labels:name: nginxspec:containers:- name: nginximage: wangyanglinux/myapp:v1imagePullPolicy: IfNotPresentports:- containerPort: 80
---
apiVersion: v1
kind: Service
metadata:name: nginx-svc
spec:ports: - port: 80targetPort: 80protocol: TCPselector: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.comhttp:paths:- path: /backend:serviceName: nginx-svcservicePort: 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: 2template:metadata:labels:name: nginxspec:containers:- name: nginximage: wangyanglinux/myapp:v1imagePullPolicy: IfNotPresentports:- containerPort: 80
---
apiVersion: v1
kind: Service
metadata:name: svc-1
spec:ports: - port: 80targetPort: 80protocol: TCPselector: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: 2template:metadata:labels:name: nginx2spec:containers:- name: nginx2image: wangyanglinux/myapp:v2imagePullPolicy: IfNotPresentports:- containerPort: 80
---
apiVersion: v1
kind: Service
metadata:name: svc-2
spec:ports: - port: 80targetPort: 80protocol: TCPselector: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.comhttp:paths:- path: /backend:serviceName: svc-1servicePort: 80
---
apiVersion: extensions/v1beta1
kind: Ingress
metadata:name: ingress2
spec:rules:- host: www2.atguigu.comhttp:paths:- path: /backend:serviceName: svc-2servicePort: 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.comsecretName: tls-secretrules:- host: foo.bar.comhttp:paths:- path: /backend:serviceName: nginx-svcservicePort: 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: 2template:metadata:labels:name: nginx3spec:containers:- name: nginx3image: wangyanglinux/myapp:v3imagePullPolicy: IfNotPresentports:- containerPort: 80
---
apiVersion: v1
kind: Service
metadata:name: svc-3
spec:ports: - port: 80targetPort: 80protocol: TCPselector: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.comsecretName: tls-secretrules:- host: www3.atguigu.comhttp:paths:- path: /backend:serviceName: svc-3servicePort: 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-authannotations:nginx.ingress.kubernetes.io/auth-type: basicnginx.ingress.kubernetes.io/auth-secret: basic-authnginx.ingress.kubernetes.io/auth-realm: 'Authentication Required - foo'
spec:rules:- host: auth.atguigu.comhttp:paths:- path: /backend:serviceName: svc-1servicePort: 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-authannotations:nginx.ingress.kubernetes.io/auth-type: basicnginx.ingress.kubernetes.io/auth-secret: basic-authnginx.ingress.kubernetes.io/auth-realm: 'Authentication Required - foo'
spec:rules:- host: auth.atguigu.comhttp:paths:- path: /backend:serviceName: svc-1servicePort: 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-testannotations : nginx.ingress.kubernetes.io/rewrite-target: https://www3.atguigu.com:31526
spec:rules:- host: re.atguigu.comhttp:paths:- path: /backend:serviceName: svc-1servicePort: 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/

k8s教程05（Kubernetes Ingress）相关推荐

1. （2022版）一套教程搞定k8s安装到实战 | Ingress

   视频来源:B站<(2022版)最新.最全.最详细的Kubernetes(K8s)教程,从K8s安装到实战一套搞定> 一边学习一边整理老师的课程内容及试验笔记,并与大家分享,侵权即删,谢谢支 ...

2. Kubernetes(k8s)集群部署七、k8s网络通信+service扩展ingress（TLS，认证，地址重写）calico网络插件（允许指定pod访问服务，禁止其他namespace访问服务）

   k8s网络通信 k8s网络通信 1.容器间通信 2.pod之间的通信 2.1同一节点的pod 2.2不同节点的pod之间的通信 flannel网络原理 flannel支持多种后端: 3.pod和ser ...

3. 宅家学习，如何进行Kubernetes Ingress控制器的技术选型？

   导语:在Kubernetes的实践.部署中,为了解决 Pod 迁移.Node Pod 端口.域名动态分配等问题,需要开发人员选择合适的 Ingress 解决方案.面对市场上众多Ingress产品,开发 ...

4. K8S部署Traefik与Ingress、IngressRoute——筑梦之路

   两种方式: Traefik+Ingress 官方文档:Kubernetes Ingress Routing Configuration - Traefik Traefik+IngressRoute 官 ...

5. 图解 K8S（05）：调度利器之标签与选择器（分组调度）

   本系列教程目录(已发布): 图解 K8S(01):基于ubuntu 部署最新版 k8s 集群 图解 K8S(02):认识 K8S 中的资源对象 图解 K8S(03):从 Pause 容器理解 Pod ...

6. 【B站、西瓜抖音视频课件】Docker K8S教程

   title: Docker&K8S教程 date: 2023-03-13 18:33:19 tags: [K8S,Docker] categories: [K8S] 网络策略 1.3开始提供 ...

7. Kubernetes Ingress 控制器的技术选型技巧

   作者:厉辉,腾讯云中间件API网关核心研发成员 在 Kubernetes 的实践.部署中,为了解决 Pod 迁移.Node Pod 端口.域名动态分配等问题,需要开发人员选择合适的 Ingress 解 ...

8. k8s教程（Volume篇）-PVC详解

   文章目录 01 引言 02 PVC详解 2.1 参数配置 2.1.1 资源请求(Resources) 2.1.2 访问模式 (Access Modes) 2.1.3 存储卷模式(Volume Mode ...

9. k8s教程（Volume篇）-PV详解

   文章目录 01 引言 02 PV详解 2.1 示例配置详解 2.1.1 存储容量 (Capacity) 2.1.2 存储卷模式 (Volume Modes) 2.1.3 访问模式 (Access Mo ...

最新文章

1. Python 文件 close() 方法
2. Python编程基础：第二十节 函数Function
3. gettimeofday函数
4. P2801-教主的魔法【分块,二分】
5. [html] 使用svg画一个爱心
6. mysql允许两个用户远程连接,配置MySQL服务允许用户远程连接
7. vim莫名假死的解决办法
8. Ubuntu切换用户su和su-的区别
9. nodejs-日志组件log4js的使用方法
10. Residual Attention Network--2017-【论文理解】
11. Python就是为了方便生活，比如看VIP电影
12. MCMC算法原理及其实例
13. R语言介绍及软件安装
14. 常用字体对照表和常用命名
15. 干货! IT项目管理过程详解(资料下载)
16. java加载dll文件失败
17. 前世今生只愿得一人心
18. c语言屏幕输出函数相关题,C语言上机考试题目
19. 无法启动此程序，因为计算机中丢失MSVCRTD.dll(MFC42D.dll, MFCO42D.dll)
20. 【微服务】配置了端口号却还是在 8080端口启动的原因

热门文章

1. 关于JavaScriptInterface的一系列问题
2. STM32系统学习——EXTI（外部中断）
3. XT.COM 直播间第100期 | CRB XT.COM AMA 专场
4. 悬壶济众生，公益也先行——郭俊海主任
5. python编写双人游戏
6. 企业改革与管理杂志企业改革与管理杂志社企业改革与管理编辑部2023年第12期目录查阅
7. Android NDK如何访问底层接口
8. 企业发展理论(七)：产权理论
9. 【宝塔】宝塔一键安装项目模块, 数据为空时的默认提示
10. 高等代数_证明_两个矩阵乘积为0，则两个矩阵的秩之和小于等于n