当前位置： 首页 > news >正文

k8s ingress-nginx 学习

news 2025/10/12 6:44:48

ingress-nginx安装

  • 1. ingress-nginx介绍
  • 2. ingress-nginx安装
    • 2.1. 使用yaml资源方式安装
    • 2.2. 使用helm包管理工具安装

1. ingress-nginx介绍

https://kubernetes.io/zh-cn/docs/concepts/services-networking/ingress/#what-is-ingress

Ingress 提供从集群外部到集群内服务的 HTTP 和 HTTPS 路由。 流量路由由 Ingress 资源所定义的规则来控制。

下面是 Ingress 的一个简单示例，可将所有流量都发送到同一 Service：
在这里插入图片描述

ingress是上service上层的流量分发器，能感知协议配置的机制来解析 URI、主机名称、路径等 Web 概念， 让你的 HTTP（或 HTTPS）网络服务可被访问。

如 ingress-nginx 就是将svc作为后端服务器，通过虚拟机主机或者前缀来匹配后端。

2. ingress-nginx安装

参考官方文档：https://kubernetes.github.io/ingress-nginx/deploy，https://github.com/kubernetes/ingress-nginx/blob/main/docs/deploy/index.md

提供了helm包和yaml资源文件安装方式：

下面通过两种方式分别安装：

2.1. 使用yaml资源方式安装

判断与k8s兼容性：
https://github.com/kubernetes/ingress-nginx#supported-versions-table

本次我使用的是v1.34.0版本，使用Ingress-NGINX v1.13.3版本

下载资源文件：

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

默认在Service 中使用的type类型是LoadBalancer我们是实验环境没有云平台的lb，可以使用的类型可以是nodeport，或者主机网络等。

这里我们使用主机网络，参照官网提供的手册：

https://kubernetes.github.io/ingress-nginx/deploy/baremetal/#via-the-host-network

修改过的资源文件如下：

apiVersion: v1
kind: Namespace
metadata:labels:app.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxname: ingress-nginx
---
apiVersion: v1
automountServiceAccountToken: true
kind: ServiceAccount
metadata:labels:app.kubernetes.io/component: controllerapp.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginxapp.kubernetes.io/version: 1.13.3name: ingress-nginxnamespace: ingress-nginx
---
apiVersion: v1
automountServiceAccountToken: true
kind: ServiceAccount
metadata:labels:app.kubernetes.io/component: admission-webhookapp.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginxapp.kubernetes.io/version: 1.13.3name: ingress-nginx-admissionnamespace: ingress-nginx
---
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:labels:app.kubernetes.io/component: controllerapp.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginxapp.kubernetes.io/version: 1.13.3name: ingress-nginxnamespace: ingress-nginx
rules:
- apiGroups:- ""resources:- namespacesverbs:- get
- apiGroups:- ""resources:- configmaps- pods- secrets- endpointsverbs:- get- list- watch
- apiGroups:- ""resources:- servicesverbs:- get- list- watch
- apiGroups:- networking.k8s.ioresources:- ingressesverbs:- get- list- watch
- apiGroups:- networking.k8s.ioresources:- ingresses/statusverbs:- update
- apiGroups:- networking.k8s.ioresources:- ingressclassesverbs:- get- list- watch
- apiGroups:- coordination.k8s.ioresourceNames:- ingress-nginx-leaderresources:- leasesverbs:- get- update
- apiGroups:- coordination.k8s.ioresources:- leasesverbs:- create
- apiGroups:- ""resources:- eventsverbs:- create- patch
- apiGroups:- discovery.k8s.ioresources:- endpointslicesverbs:- list- watch- get
---
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:labels:app.kubernetes.io/component: admission-webhookapp.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginxapp.kubernetes.io/version: 1.13.3name: ingress-nginx-admissionnamespace: ingress-nginx
rules:
- apiGroups:- ""resources:- secretsverbs:- get- create
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:labels:app.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginxapp.kubernetes.io/version: 1.13.3name: ingress-nginx
rules:
- apiGroups:- ""resources:- configmaps- endpoints- nodes- pods- secrets- namespacesverbs:- list- watch
- apiGroups:- coordination.k8s.ioresources:- leasesverbs:- list- watch
- apiGroups:- ""resources:- nodesverbs:- get
- apiGroups:- ""resources:- servicesverbs:- get- list- watch
- apiGroups:- networking.k8s.ioresources:- ingressesverbs:- get- list- watch
- apiGroups:- ""resources:- eventsverbs:- create- patch
- apiGroups:- networking.k8s.ioresources:- ingresses/statusverbs:- update
- apiGroups:- networking.k8s.ioresources:- ingressclassesverbs:- get- list- watch
- apiGroups:- discovery.k8s.ioresources:- endpointslicesverbs:- list- watch- get
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:labels:app.kubernetes.io/component: admission-webhookapp.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginxapp.kubernetes.io/version: 1.13.3name: ingress-nginx-admission
rules:
- apiGroups:- admissionregistration.k8s.ioresources:- validatingwebhookconfigurationsverbs:- get- update
---
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:labels:app.kubernetes.io/component: controllerapp.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginxapp.kubernetes.io/version: 1.13.3name: ingress-nginxnamespace: ingress-nginx
roleRef:apiGroup: rbac.authorization.k8s.iokind: Rolename: ingress-nginx
subjects:
- kind: ServiceAccountname: ingress-nginxnamespace: ingress-nginx
---
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:labels:app.kubernetes.io/component: admission-webhookapp.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginxapp.kubernetes.io/version: 1.13.3name: ingress-nginx-admissionnamespace: ingress-nginx
roleRef:apiGroup: rbac.authorization.k8s.iokind: Rolename: ingress-nginx-admission
subjects:
- kind: ServiceAccountname: ingress-nginx-admissionnamespace: ingress-nginx
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:labels:app.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginxapp.kubernetes.io/version: 1.13.3name: ingress-nginx
roleRef:apiGroup: rbac.authorization.k8s.iokind: ClusterRolename: ingress-nginx
subjects:
- kind: ServiceAccountname: ingress-nginxnamespace: ingress-nginx
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:labels:app.kubernetes.io/component: admission-webhookapp.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginxapp.kubernetes.io/version: 1.13.3name: ingress-nginx-admission
roleRef:apiGroup: rbac.authorization.k8s.iokind: ClusterRolename: ingress-nginx-admission
subjects:
- kind: ServiceAccountname: ingress-nginx-admissionnamespace: ingress-nginx
---
apiVersion: v1
data: null
kind: ConfigMap
metadata:labels:app.kubernetes.io/component: controllerapp.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginxapp.kubernetes.io/version: 1.13.3name: ingress-nginx-controllernamespace: ingress-nginx
---
apiVersion: v1
kind: Service
metadata:labels:app.kubernetes.io/component: controllerapp.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginxapp.kubernetes.io/version: 1.13.3name: ingress-nginx-controllernamespace: ingress-nginx
spec:externalTrafficPolicy: LocalipFamilies:- IPv4ipFamilyPolicy: SingleStackports:- appProtocol: httpname: httpport: 80protocol: TCPtargetPort: http- appProtocol: httpsname: httpsport: 443protocol: TCPtargetPort: httpsselector:app.kubernetes.io/component: controllerapp.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxtype: LoadBalancer
---
apiVersion: v1
kind: Service
metadata:labels:app.kubernetes.io/component: controllerapp.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginxapp.kubernetes.io/version: 1.13.3name: ingress-nginx-controller-admissionnamespace: ingress-nginx
spec:ports:- appProtocol: httpsname: https-webhookport: 443targetPort: webhookselector:app.kubernetes.io/component: controllerapp.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxtype: ClusterIP
---
apiVersion: apps/v1
kind: DaemonSet				# 使用DS控制器，由于使用的是主机网络避免多个POD端口冲突
metadata:labels:app.kubernetes.io/component: controllerapp.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginxapp.kubernetes.io/version: 1.13.3name: ingress-nginx-controllernamespace: ingress-nginx
spec:minReadySeconds: 0revisionHistoryLimit: 10selector:matchLabels:app.kubernetes.io/component: controllerapp.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxupdateStrategy:			# DS的滚动更新配置需要修改rollingUpdate:maxUnavailable: 1type: RollingUpdatetemplate:metadata:labels:app.kubernetes.io/component: controllerapp.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginxapp.kubernetes.io/version: 1.13.3spec:tolerations:				# 添加master容忍- key: "node-role.kubernetes.io/control-plane"operator: "Exists"effect: "NoSchedule"hostNetwork: true			# POD使用主机网络dnsPolicy: ClusterFirstWithHostNet		# 优先使用主机网络，然后是集群网络automountServiceAccountToken: true		containers:- args:- /nginx-ingress-controller- --publish-service=$(POD_NAMESPACE)/ingress-nginx-controller- --election-id=ingress-nginx-leader- --controller-class=k8s.io/ingress-nginx- --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/keyenv:- name: POD_NAMEvalueFrom:fieldRef:fieldPath: metadata.name- name: POD_NAMESPACEvalueFrom:fieldRef:fieldPath: metadata.namespace- name: LD_PRELOADvalue: /usr/local/lib/libmimalloc.soimage: registry.cn-hangzhou.aliyuncs.com/google_containers/nginx-ingress-controller:v1.13.3	# 使用国内镜像imagePullPolicy: IfNotPresentlifecycle:preStop:exec:command:- /wait-shutdownlivenessProbe:failureThreshold: 5httpGet:path: /healthzport: 10254scheme: HTTPinitialDelaySeconds: 10periodSeconds: 10successThreshold: 1timeoutSeconds: 1name: controllerports:- containerPort: 80name: httpprotocol: TCP- containerPort: 443name: httpsprotocol: TCP- containerPort: 8443name: webhookprotocol: TCPreadinessProbe:failureThreshold: 3httpGet:path: /healthzport: 10254scheme: HTTPinitialDelaySeconds: 10periodSeconds: 10successThreshold: 1timeoutSeconds: 1resources:requests:cpu: 100mmemory: 90MisecurityContext:allowPrivilegeEscalation: falsecapabilities:add:- NET_BIND_SERVICEdrop:- ALLreadOnlyRootFilesystem: falserunAsGroup: 82runAsNonRoot: truerunAsUser: 101seccompProfile:type: RuntimeDefaultvolumeMounts:- mountPath: /usr/local/certificates/name: webhook-certreadOnly: truednsPolicy: ClusterFirstnodeSelector:kubernetes.io/os: linuxserviceAccountName: ingress-nginxterminationGracePeriodSeconds: 300volumes:- name: webhook-certsecret:secretName: ingress-nginx-admission
---
apiVersion: batch/v1
kind: Job
metadata:labels:app.kubernetes.io/component: admission-webhookapp.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginxapp.kubernetes.io/version: 1.13.3name: ingress-nginx-admission-createnamespace: ingress-nginx
spec:template:metadata:labels:app.kubernetes.io/component: admission-webhookapp.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginxapp.kubernetes.io/version: 1.13.3name: ingress-nginx-admission-createspec:automountServiceAccountToken: truecontainers:- args:- create- --host=ingress-nginx-controller-admission,ingress-nginx-controller-admission.$(POD_NAMESPACE).svc- --namespace=$(POD_NAMESPACE)- --secret-name=ingress-nginx-admissionenv:- name: POD_NAMESPACEvalueFrom:fieldRef:fieldPath: metadata.namespaceimage: registry.cn-hangzhou.aliyuncs.com/google_containers/kube-webhook-certgen:v1.6.3	# 镜像修改为国内镜像imagePullPolicy: IfNotPresentname: createsecurityContext:allowPrivilegeEscalation: falsecapabilities:drop:- ALLreadOnlyRootFilesystem: truerunAsGroup: 65532runAsNonRoot: truerunAsUser: 65532seccompProfile:type: RuntimeDefaultnodeSelector:kubernetes.io/os: linuxrestartPolicy: OnFailureserviceAccountName: ingress-nginx-admissionttlSecondsAfterFinished: 0
---
apiVersion: batch/v1
kind: Job
metadata:labels:app.kubernetes.io/component: admission-webhookapp.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginxapp.kubernetes.io/version: 1.13.3name: ingress-nginx-admission-patchnamespace: ingress-nginx
spec:template:metadata:labels:app.kubernetes.io/component: admission-webhookapp.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginxapp.kubernetes.io/version: 1.13.3name: ingress-nginx-admission-patchspec:automountServiceAccountToken: truecontainers:- args:- patch- --webhook-name=ingress-nginx-admission- --namespace=$(POD_NAMESPACE)- --patch-mutating=false- --secret-name=ingress-nginx-admission- --patch-failure-policy=Failenv:- name: POD_NAMESPACEvalueFrom:fieldRef:fieldPath: metadata.namespaceimage: registry.cn-hangzhou.aliyuncs.com/google_containers/kube-webhook-certgen:v1.6.3	# 镜像修改为国内镜像imagePullPolicy: IfNotPresentname: patchsecurityContext:allowPrivilegeEscalation: falsecapabilities:drop:- ALLreadOnlyRootFilesystem: truerunAsGroup: 65532runAsNonRoot: truerunAsUser: 65532seccompProfile:type: RuntimeDefaultnodeSelector:kubernetes.io/os: linuxrestartPolicy: OnFailureserviceAccountName: ingress-nginx-admissionttlSecondsAfterFinished: 0
---
apiVersion: networking.k8s.io/v1
kind: IngressClass
metadata:labels:app.kubernetes.io/component: controllerapp.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginxapp.kubernetes.io/version: 1.13.3name: nginxannotations:			# 添加注释将nginx作为默认 ingressingressclass.kubernetes.io/is-default-class: "true"
spec:controller: k8s.io/ingress-nginx
---
apiVersion: admissionregistration.k8s.io/v1
kind: ValidatingWebhookConfiguration
metadata:labels:app.kubernetes.io/component: admission-webhookapp.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginxapp.kubernetes.io/version: 1.13.3name: ingress-nginx-admission
webhooks:
- admissionReviewVersions:- v1clientConfig:service:name: ingress-nginx-controller-admissionnamespace: ingress-nginxpath: /networking/v1/ingressesport: 443failurePolicy: FailmatchPolicy: Equivalentname: validate.nginx.ingress.kubernetes.iorules:- apiGroups:- networking.k8s.ioapiVersions:- v1operations:- CREATE- UPDATEresources:- ingressessideEffects: None

创建ingress-nginx控制器

/kube-webhook-certgen镜像是负责证书的创建，只有证书创建完成后nginx-ingress-controller控制器才会被集群信任，并正常工作。

kubectl apply -f  deploy.yaml

查看证书是否创建：

kubectl get secrets -n ingress-nginx

NAME                      TYPE     DATA   AGE
ingress-nginx-admission   Opaque   3      41m

查看pod是否正常创建：

kubectl get pod -n ingress-nginx

NAME                             READY   STATUS    RESTARTS   AGE
ingress-nginx-controller-6x468   1/1     Running   0          22m
ingress-nginx-controller-7g86s   1/1     Running   0          23m
ingress-nginx-controller-cnmh6   1/1     Running   0          22m

查看端口是否绑定：

192.169.100.131 | CHANGED | rc=0 >>
LISTEN 0      4096         0.0.0.0:443        0.0.0.0:*
LISTEN 0      4096         0.0.0.0:443        0.0.0.0:*
LISTEN 0      4096         0.0.0.0:80         0.0.0.0:*
LISTEN 0      4096         0.0.0.0:80         0.0.0.0:*
192.169.100.132 | CHANGED | rc=0 >>
LISTEN 0      4096         0.0.0.0:80         0.0.0.0:*
LISTEN 0      4096         0.0.0.0:80         0.0.0.0:*
LISTEN 0      4096         0.0.0.0:443        0.0.0.0:*
LISTEN 0      4096         0.0.0.0:443        0.0.0.0:*
192.169.100.130 | CHANGED | rc=0 >>
LISTEN 0      4096           0.0.0.0:80         0.0.0.0:*
LISTEN 0      4096           0.0.0.0:80         0.0.0.0:*
LISTEN 0      4096           0.0.0.0:443        0.0.0.0:*
LISTEN 0      4096           0.0.0.0:443        0.0.0.0:*
LISTEN 0      4096   192.169.100.130:2380       0.0.0.0:*

创建资源文件测试：
my-nginx.yaml:

---
apiVersion: apps/v1
kind: Deployment
metadata:labels:app: my-nginxname: my-nginx
spec:replicas: 3selector:matchLabels:app: my-nginxtemplate:metadata:labels:app: my-nginxspec:containers:- name: my-nginximage: nginx:latestimagePullPolicy: IfNotPresentports:- containerPort: 80
---
apiVersion: v1
kind: Service
metadata:labels:app: my-nginxname: my-nginx
spec:ports:- name: my-nginxport: 80targetPort: 80selector:app: my-nginxtype: ClusterIP
---
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:name: my-nginx-ingress
spec:#ingressClassName: nginx	# 使用nginx-ingress作为 ingressrules:- host: k8s-master01		# 指定虚拟机主机，这里我使用的是master主机名http:paths:- backend:service:name: my-nginx			# 访问k8s-master01 时代理到my-nginx svc的80端口port:number: 80path: /								pathType: Prefix

创建资源：

kubectl apply -f my-nginx

访问k8s-master01测试：

curl k8s-master01

<!DOCTYPE html>
<html>
<head>
<title>Welcome to nginx!</title>
<style>
html { color-scheme: light dark; }
body { width: 35em; margin: 0 auto;
font-family: Tahoma, Verdana, Arial, sans-serif; }
</style>
</head>
<body>
<h1>Welcome to nginx!</h1>
<p>If you see this page, the nginx web server is successfully installed and
working. Further configuration is required.</p><p>For online documentation and support please refer to
<a href="http://nginx.org/">nginx.org</a>.<br/>
Commercial support is available at
<a href="http://nginx.com/">nginx.com</a>.</p><p><em>Thank you for using nginx.</em></p>
</body>
</html>

2.2. 使用helm包管理工具安装

官网参考链接：https://github.com/kubernetes/ingress-nginx/blob/main/docs/deploy/index.md#quick-start

添加ingress-nginx仓库：

helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx

查看所有chat包：

可以看出ingress-nginx当前版本是 1.13.3

helm search repo ingress-nginx

NAME                            CHART VERSION   APP VERSION     DESCRIPTION
ingress-nginx/ingress-nginx     4.13.3          1.13.3          Ingress controller for Kubernetes using NGINX a...

下载Chart压缩包到本地进行修改：

helm pull ingress-nginx/ingress-nginx --untar

注释掉values.yaml文件中的digest开头的内容，并把仓库都设置成阿里云。

sed -i 's/^[[:space:]]*digest/#&/' values.yaml
sed -i 's/registry.k8s.io/registry.cn-hangzhou.aliyuncs.com/g' values.yaml

创建my-ingress-values.yaml文件,添加如下内容：

下面使用NodePort 作为 外部访问方式；

global:image:registry: registry.cn-hangzhou.aliyuncs.com		# 配置仓库名
controller:replicaCount: 2		# 指定副本数量image:repository: registry.cn-hangzhou.aliyuncs.com/google_containers/nginx-ingress-controller	# 指定镜像名称tag: "v1.13.3"	# 指定镜像版本admissionWebhooks:enabled: truepatch:image:repository: registry.cn-hangzhou.aliyuncs.com/google_containers/kube-webhook-certgen	# 指定镜像名称tag: "v1.6.3"			# 指定镜像版本ingressClassResource:default: trueservice:type: NodePort			# 设置service模式nodePorts:				# 绑定主机地址：80:30080 443:30443http: "30080"https: "30443"

使用修改后的my-ingress-values.yaml文件来实现自定义配置安装，其他配置默认使用values.yaml：

helm upgrade --install ingress-nginx ./ingress-nginx \--namespace ingress-nginx \--create-namespace \-f my-ingress-values.yaml

查看pod：

kubectl get pod -n ingress-nginx -o wide

NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
ingress-nginx-controller-565fd766cb-gf6n8 1/1 Running 0 21m 10.224.58.247 k8s-node02
ingress-nginx-controller-565fd766cb-n24mp 1/1 Running 0 11m 10.224.85.199 k8s-node01

查看nodeport是否生效：

kubectl get svc -n  ingress-nginx

NAME                                 TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)                      AGE
ingress-nginx-controller             NodePort    10.110.163.168   <none>        80:30080/TCP,443:30443/TCP   2m27s

创建资源文件测试：
my-nginx:

---
apiVersion: apps/v1
kind: Deployment
metadata:labels:app: my-nginxname: my-nginx
spec:replicas: 3selector:matchLabels:app: my-nginxtemplate:metadata:labels:app: my-nginxspec:containers:- name: my-nginximage: nginx:latestimagePullPolicy: IfNotPresentports:- containerPort: 80
---
apiVersion: v1
kind: Service
metadata:labels:app: my-nginxname: my-nginx
spec:ports:- name: my-nginxport: 80targetPort: 80selector:app: my-nginxtype: ClusterIP
---
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:name: my-nginx-ingress
spec:
#  ingressClassName: nginxrules:- host: k8s-master01http:paths:- backend:service:name: my-nginxport:number: 80path: /pathType: Prefix

kubectl apply -f  my-nginx

访问测试：

curl k8s-master01:30080

<!DOCTYPE html>
<html>
<head>
<title>Welcome to nginx!</title>
<style>
html { color-scheme: light dark; }
body { width: 35em; margin: 0 auto;
font-family: Tahoma, Verdana, Arial, sans-serif; }
</style>
</head>
<body>
<h1>Welcome to nginx!</h1>
<p>If you see this page, the nginx web server is successfully installed and
working. Further configuration is required.</p><p>For online documentation and support please refer to
<a href="http://nginx.org/">nginx.org</a>.<br/>
Commercial support is available at
<a href="http://nginx.com/">nginx.com</a>.</p><p><em>Thank you for using nginx.</em></p>
</body>
</html>

主机模式和NodePort模式对比：
主机模式：
优点：使用主机的网络，性能最佳，可以获取客户端地址
缺点：POD共享主机网络，隔离性差、并且使用主机端口资源，可能存在端口冲突

NortPort模式：
优点：使用dnat模式转发到后端服务、端口可以使用非80 443端口，与主机存在网络栈隔离

缺点：经过一层nat性能有所损耗、并且默认所有的客户端ip都是主机地址

http://www.dtcms.com/a/469452.html

相关文章：

  • 【含文档+PPT+源码】基于springboot的旅游路线推荐系统的设计与实现
  • 嘉兴seo网站优化竞价托管的注意事项
  • K8S 概念、安装与核心工作机制详解
  • 做网站需要公司有哪些网站最新点击量排名
  • VUE 开发实例 一则
  • jmeter使用之--MD5加密
  • ESim电工仿真APP使用说明书
  • 【碎片化学习】 Apache JMeter 取样器指南：从入门到精通
  • 【无标题】生活琐记（7）
  • 苍穹外卖day04总结
  • Java Redis “核心基础”面试清单（含超通俗生活案例与深度理解）
  • jmeter中使用正则表达式提取器传递参数
  • 基于大数据的学习资源推送系统的设计与实现 _django
  • 朝阳双桥网站建设竞争对手网站分析
  • 江阴招聘网站建设学徒黄页网页的推广网站
  • C 语言11：输入方法全解析
  • ASP Session详解
  • 如何在 Linux_Ubuntu 上安装 Qt 5：详细教程
  • 前端学习 JavaScript（3）json初识
  • StartAllBack(Win11开始菜单增强工具) 绿色版
  • 大雾天气下摄像头图像去雾技术详解
  • MySQL数据库基础(2)
  • 大模型文生图技术解析：从语言到视觉的智能跨越
  • 水安建设集团网站做任务换流量的网站
  • 【自适应滤波】自适应UKF，基于新息自适应调节Q和R，场景为雷达跟踪与滤波、MATLAB实现
  • C语言文件管理
  • 【解决】Unable to locate configuration file
  • 计算机视觉（opencv）——仿射变换（Affine Transformation）
  • Hadess入门到实战(11) - 如何导入Nexus制品，实现平滑迁移
  • Spring内置功能