建站快车的功能介绍,设备外贸用哪个网站,网站设计任务,网页设计旅游网站前言Ingress 1、Ingress概念2、 pod和ingress的关系3、 Ingress的工作流程4、 使用步骤5、对外暴露应用实战5.1 创建nginx应用#xff0c;对外暴露端口使用NodePort5.2 部署ingress controller5.3 创建ingress规则5.4 访问 1、Ingress概念 k8s 对外暴露服务#xff08;service对外暴露端口使用NodePort5.2 部署ingress controller5.3 创建ingress规则5.4 访问 1、Ingress概念 k8s 对外暴露服务service主要有两种方式NotePort, LoadBalance。但是当集群服务很多的时候NodePort方式最大的缺点是会占用很多集群机器的端口LB方式最大的缺点则是每个service一个LB又有点浪费和麻烦并且需要k8s之外的支持 而ingress则只需要一个NodePort或者一个LB就可以满足所有service对外服务的需求。 ingress相当于一个7层的负载均衡器是k8s对反向代理的一个抽象。大概的工作原理也确实类似于Nginx可以理解成在 Ingress 里建立一个个映射规则 , ingress Controller 通过监听 Ingress这个api对象里的配置规则并转化成 Nginx 的配置kubernetes声明式API和控制循环 , 然后对外部提供服务。 ingress controller核心是一个deployment实现方式有很多比如nginx, Contour, Haproxy, trafik, Istio需要编写的yaml有Deployment, Service, ConfigMap, ServiceAccountAuth其中service的类型可以是NodePort或者LoadBalancer。 ingress resources这个就是一个类型为Ingress的k8s api对象了这部分则是面向开发人员。 解决的问题实际过程中访问都是通过域名的方式实现根据不同域名跳转到不同的端口服务中去Ingress解决的是新的服务加入后域名和服务的对应问题基本上是一个ingress的对象通过yaml进行创建和更新进行加载
2、 pod和ingress的关系
pod和ingress是通过service进行关联的Ingress作为一个统一的入口然后通过不同的域名寻找service下关联的pod进行负载均衡
3、 Ingress的工作流程
详细参考该博客写的不错
4、 使用步骤 1、部署Ingress Contorller 2、创建Ingress规则 本文使用官方维护的nginx控制器进行部署
5、对外暴露应用实战
5.1 创建nginx应用对外暴露端口使用NodePort
[rootmaster ~]# kubectl create deployment web --imagenginx
deployment.apps/web created
[rootmaster ~]# kubectl expose deployment web --port80 --target-port80 --typeNodePort
service/web exposed
[rootmaster ~]# kubectl get pod
NAME READY STATUS RESTARTS AGE
web-96d5df5c8-zcshb 1/1 Running 0 47s
[rootmaster ~]# kubectl get svc
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
kubernetes ClusterIP 10.96.0.1 none 443/TCP 65d
web NodePort 10.96.63.223 none 80:31281/TCP 9s
5.2 部署ingress controller
[rootmaster ingress]# wget https://raw.githubusercontent.com/kubernetes/ingress-nginx/nginx-0.30.0/deploy/static/mandatory.yaml -O nginx-ingress-controller.yaml ##官方下载ingress controller文件
[rootmaster ingress]# docker pull lizhenliang/nginx-ingress-controller:0.30.0 ##官方的镜像下载不下来可以更换为docker拉取[rootmaster ingress]# cat ingress-controller.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:- resources:- eventsverbs:- create- patch- apiGroups:- extensions- networking.k8s.ioresources:- ingressesverbs:- get- list- watch- apiGroups:- extensions- networking.k8s.ioresources:- 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-nginxverbs:- 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: 10254prometheus.io/scrape: truespec:hostNetwork: true# wait up to five minutes for the drain of connectionsterminationGracePeriodSeconds: 300serviceAccountName: nginx-ingress-serviceaccountnodeSelector:kubernetes.io/os: linuxcontainers:- name: nginx-ingress-controllerimage: lizhenliang/nginx-ingress-controller:0.30.0args:- /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-prefixnginx.ingress.kubernetes.iosecurityContext:allowPrivilegeEscalation: truecapabilities:drop:- ALLadd:- NET_BIND_SERVICE# www-data - 101runAsUser: 101env:- name: POD_NAMEvalueFrom:fieldRef:fieldPath: metadata.name- name: POD_NAMESPACEvalueFrom:fieldRef:fieldPath: metadata.namespaceports:- name: httpcontainerPort: 80protocol: TCP- name: httpscontainerPort: 443protocol: TCPlivenessProbe:failureThreshold: 3httpGet:path: /healthzport: 10254scheme: HTTPinitialDelaySeconds: 10periodSeconds: 10successThreshold: 1timeoutSeconds: 10readinessProbe:failureThreshold: 3httpGet:path: /healthzport: 10254scheme: HTTPperiodSeconds: 10successThreshold: 1timeoutSeconds: 10lifecycle:preStop:exec:command:- /wait-shutdown---apiVersion: v1
kind: LimitRange
metadata:name: ingress-nginxnamespace: ingress-nginxlabels:app.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginx
spec:limits:- min:memory: 90Micpu: 100mtype: Container[rootmaster ingress]# kubectl apply -f nginx-ingress-controller.yaml
[rootmaster ingress]# kubectl get pods -n ingress-nginx ##部署成功
NAME READY STATUS RESTARTS AGE
nginx-ingress-controller-5dc64b58f-5pd9d 1/1 Running 0 102s
5.3 创建ingress规则
## 规则示例文件具体要求可以通过官网进行查看
[rootmaster ingress]# cat ingress01.yaml
apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:name: example-ingress
spec:rules:- host: example.ingredemo.comhttp:paths:- path: /backend:serviceName: web ##绑定serviceservicePort: 80
[rootmaster ingress]# kubectl apply -f ingress01.yaml
Warning: networking.k8s.io/v1beta1 Ingress is deprecated in v1.19, unavailable in v1.22; use networking.k8s.io/v1 Ingress
ingress.networking.k8s.io/example-ingress created
[rootmaster ingress]# kubectl get ing #查看规则文件
NAME CLASS HOSTS ADDRESS PORTS AGE
example-ingress none example.ingredemo.com 80 17s
5.4 访问
通过域名访问需要在windows下的hosts文件中添加域名和IP。添加完成后访问如下图。
