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

2024年还会封城吗,网络优化属于什么部门,wordpress插件WZone,1688会提供网站建设1、ingress介绍 Ingress 提供从集群外部到集群内服务的 HTTP 和 HTTPS 路由。 流量路由由 Ingress 资源所定义的规则来控制。 Ingress 是对集群中服务的外部访问进行管理的 API 对象#xff0c;典型的访问方式是 HTTP。 Ingress 可以提供负载均衡、SSL 终结和基于名称的虚拟…1、ingress介绍 Ingress 提供从集群外部到集群内服务的 HTTP 和 HTTPS 路由。 流量路由由 Ingress 资源所定义的规则来控制。 Ingress 是对集群中服务的外部访问进行管理的 API 对象典型的访问方式是 HTTP。 Ingress 可以提供负载均衡、SSL 终结和基于名称的虚拟托管。
2、ingress 的依赖 你必须拥有一个 Ingress 控制器 才能满足 Ingress 的要求。仅创建 Ingress 资源本身没有任何效果。 你可能需要部署一个 Ingress 控制器例如 ingress-nginx。 你可以从许多 Ingress 控制器中进行选择。 理想情况下所有 Ingress 控制器都应遵从参考规范。 但实际上各个 Ingress 控制器操作略有不同。
3、ingress-nginx 安装流程 参考链接https://kubernetes.github.io/ingress-nginx/deploy/ 3.1 k8s的包管理器 Helm 安装 Helm官网https://helm.sh/zh/docs/intro/quickstart/注安装Helm的时候需要注意k8s的版本

下载helm

[rootk8s-master ~]# wget https://get.helm.sh/helm-v3.10.0-linux-amd64.tar.gz -O helm-v3.10.0-linux-amd64.tar.gz[rootk8s-master ~]# tar -zxvf helm-v3.10.0-linux-amd64.tar.gz[rootk8s-master ~]# mv linux-amd64/helm /usr/local/bin/ [rootk8s-master ~]# helm version version.BuildInfo{Version:v3.10.0, GitCommit:ce66412a723e4d89555dc67217607c6579ffcb21, GitTreeState:clean, GoVersion:go1.18.6} 3.2 添加helm仓库 [rootk8s-master ~]# helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx ingress-nginx has been added to your repositories [rootk8s-master ~]# helm repo list NAME URL ingress-nginx https://kubernetes.github.io/ingress-nginx [rootk8s-master ~]# helm search repo ingress-nginx NAME CHART VERSION APP VERSION DESCRIPTION ingress-nginx/ingress-nginx 4.9.1 1.9.6 Ingress controller for Kubernetes using NGINX a… 3.3 通过helm下载ingress-nginx 下载ingress-nginx的时候需要查看版本是否匹配k8s的版本地址链接查看新版本是否支持由于我的k8s版本是1.25所以最新的v1.9.6可以使用。
[rootk8s-master ~]# helm pull ingress-nginx/ingress-nginx [rootk8s-master ~]# ll ingress-nginx-4.9.1.tgz -rw-r–r–. 1 root root 53966 2月 25 14:38 ingress-nginx-4.9.1.tgz [rootk8s-master ~]# mv ingress-nginx-4.9.1.tgz /opt/helm/ [rootk8s-master ~]# cd !\( cd /opt/helm[rootk8s-master helm]# ll 总用量 4088 -rw-r--r--. 1 root root 2293749 2月 25 14:40 helm-v3.10.0-linux-amd64.tar.gz -rw-r--r--. 1 root root 53966 2月 25 14:38 ingress-nginx-4.9.1.tgz[rootk8s-master helm]# tar -xf ingress-nginx-4.9.1.tgz[rootk8s-master helm]# cd ingress-nginx [rootk8s-master ingress-nginx]# ll 总用量 128 drwxr-xr-x. 2 root root 4096 2月 25 14:40 changelog -rw-r--r--. 1 root root 702 1月 27 15:46 Chart.yaml drwxr-xr-x. 2 root root 4096 2月 25 14:40 ci -rw-r--r--. 1 root root 213 1月 27 15:46 OWNERS -rw-r--r--. 1 root root 48217 1月 27 15:46 README.md -rw-r--r--. 1 root root 11358 1月 27 15:46 README.md.gotmpl drwxr-xr-x. 3 root root 4096 2月 25 14:40 templates drwxr-xr-x. 2 root root 4096 2月 25 14:40 tests -rw-r--r--. 1 root root 44163 1月 27 15:46 values.yaml3.4 修改values.yaml参数配置 3.4.1 修改ingress的控制器的镜像地址为国内地址 registry: registry.cn-hangzhou.aliyuncs.com image: google_containers/nginx-ingress-controller3.4.2 注释ingress的控制器中的哈希校验 3.4.3 修改dnsPolicy的值为 ClusterFirstWithHostNet 3.4.4 修改hostNetwork的值为true 3.4.5 修改kind的值为DaemonSET 3.4.6 在nodeSelector下添加 ingress: “true” 3.4.7 修改这里的type的值为ClusterIP 3.4.8 修改enabled的值为false 3.4.9 修改kube-webhook处的镜像地址和type registry: registry.cn-hangzhou.aliyuncs.com image: google_containers/kube-webhook-certgen 3.5 创建这个ingress资源 3.5.1 专门为ingress-nginx创建一个namespace [rootk8s-master ingress-nginx]# kubectl create ns ingress-nginx namespace/ingress-nginx created3.5.2 为需要部署的ingress节点上添加标签 [rootk8s-master ingress-nginx]# kubectl label node k8s-master ingresstrue node/k8s-master labeled[rootk8s-master ingress-nginx]# kubectl get nodes --show-labels NAME STATUS ROLES AGE VERSION LABELS k8s-master Ready control-plane 5d21h v1.25.0 beta.kubernetes.io/archamd64,beta.kubernetes.io/oslinux,ingresstrue,kubernetes.io/archamd64,kubernetes.io/hostnamek8s-master,kubernetes.io/oslinux,node-role.kubernetes.io/control-plane,node.kubernetes.io/exclude-from-external-load-balancers k8s-node-01 Ready none 5d20h v1.25.0 beta.kubernetes.io/archamd64,beta.kubernetes.io/oslinux,kubernetes.io/archamd64,kubernetes.io/hostnamek8s-node-01,kubernetes.io/oslinux,typemicrosvc k8s-node-02 Ready none 3d21h v1.25.0 beta.kubernetes.io/archamd64,beta.kubernetes.io/oslinux,kubernetes.io/archamd64,kubernetes.io/hostnamek8s-node-02,kubernetes.io/oslinux,typemicrosvc3.5.3 安装ingress-nginx [rootk8s-master ingress-nginx]# ll 总用量 128 drwxr-xr-x. 2 root root 4096 2月 25 14:40 changelog -rw-r--r--. 1 root root 702 1月 27 15:46 Chart.yaml drwxr-xr-x. 2 root root 4096 2月 25 14:40 ci -rw-r--r--. 1 root root 213 1月 27 15:46 OWNERS -rw-r--r--. 1 root root 48217 1月 27 15:46 README.md -rw-r--r--. 1 root root 11358 1月 27 15:46 README.md.gotmpl drwxr-xr-x. 3 root root 4096 2月 25 14:40 templates drwxr-xr-x. 2 root root 4096 2月 25 14:40 tests -rw-r--r--. 1 root root 44366 2月 25 16:55 values.yaml [rootk8s-master ingress-nginx]# helm install ingress-nginx -n ingress-nginx . NAME: ingress-nginx LAST DEPLOYED: Sun Feb 25 19:35:55 2024 NAMESPACE: ingress-nginx STATUS: deployed REVISION: 1 TEST SUITE: None NOTES: The ingress-nginx controller has been installed. Get the application URL by running these commands:export POD_NAME\)(kubectl get pods –namespace ingress-nginx –selector app.kubernetes.io/nameingress-nginx,app.kubernetes.io/instanceingress-nginx,app.kubernetes.io/componentcontroller –output jsonpath{.items[0].metadata.name})kubectl port-forward –namespace ingress-nginx \({POD_NAME} 8080:80echo Visit http://127.0.0.1:8080 to access your application.An example Ingress that makes use of the controller:apiVersion: networking.k8s.io/v1kind: Ingressmetadata:name: examplenamespace: foospec:ingressClassName: nginxrules:- host: www.example.comhttp:paths:- pathType: Prefixbackend:service:name: exampleServiceport:number: 80path: /# This section is only required if TLS is to be enabled for the Ingresstls:- hosts:- www.example.comsecretName: example-tlsIf TLS is enabled for the Ingress, a Secret containing the certificate and key must also be provided:apiVersion: v1kind: Secretmetadata:name: example-tlsnamespace: foodata:tls.crt: base64 encoded certtls.key: base64 encoded keytype: kubernetes.io/tls3.5.4 在node1上添加一个标签 由于master有个污点的问题所以ingress-nginx暂时无法创建上这个问题后续在写现在在node1上添加一个ingresstrue的标签。在来查看下。 rootk8s-master ingress-nginx]# kubectl label nodes k8s-node-01 ingresstrue node/k8s-node-01 labeled [rootk8s-master ingress-nginx]# kubectl get -n ingress-nginx po NAME READY STATUS RESTARTS AGE ingress-nginx-controller-jn65t 0/1 ContainerCreating 0 12s[rootk8s-master ingress-nginx]# kubectl describe -n ingress-nginx po ingress-nginx-controller-jn65t Name: ingress-nginx-controller-jn65t Namespace: ingress-nginx Priority: 0 Service Account: ingress-nginx Node: k8s-node-01/10.10.10.177 Start Time: Sun, 25 Feb 2024 19:42:49 0800 Labels: app.kubernetes.io/componentcontrollerapp.kubernetes.io/instanceingress-nginxapp.kubernetes.io/managed-byHelmapp.kubernetes.io/nameingress-nginxapp.kubernetes.io/part-ofingress-nginxapp.kubernetes.io/version1.9.6controller-revision-hash78d8f9c87chelm.sh/chartingress-nginx-4.9.1pod-template-generation1 Annotations: none Status: Running IP: 10.10.10.177 IPs:IP: 10.10.10.177 Controlled By: DaemonSet/ingress-nginx-controller Containers:controller:Container ID: docker://5a25f4de88555d15c0a335afda6dcbe02fed2bcf992c30a06c02b05397c50649Image: registry.cn-hangzhou.aliyuncs.com/google_containers/nginx-ingress-controller:v1.9.6Image ID: docker-pullable://registry.cn-hangzhou.aliyuncs.com/google_containers/nginx-ingress-controllersha256:195a471f4765b6c752919003bf5b9a029b250531f9f48caf0beae64495daa4c2Ports: 80/TCP, 443/TCPHost Ports: 80/TCP, 443/TCPArgs:/nginx-ingress-controller--publish-service\)(POD_NAMESPACE)/ingress-nginx-controller–election-idingress-nginx-leader–controller-classk8s.io/ingress-nginx–ingress-classnginx–configmap\((POD_NAMESPACE)/ingress-nginx-controllerState: RunningStarted: Sun, 25 Feb 2024 19:43:12 0800Ready: TrueRestart Count: 0Requests:cpu: 100mmemory: 90MiLiveness: http-get http://:10254/healthz delay10s timeout1s period10s #success1 #failure5Readiness: http-get http://:10254/healthz delay10s timeout1s period10s #success1 #failure3Environment:POD_NAME: ingress-nginx-controller-jn65t (v1:metadata.name)POD_NAMESPACE: ingress-nginx (v1:metadata.namespace)LD_PRELOAD: /usr/local/lib/libmimalloc.soMounts:/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-dklj9 (ro) Conditions:Type StatusInitialized TrueReady TrueContainersReady TruePodScheduled True Volumes:kube-api-access-dklj9:Type: Projected (a volume that contains injected data from multiple sources)TokenExpirationSeconds: 3607ConfigMapName: kube-root-ca.crtConfigMapOptional: nilDownwardAPI: true QoS Class: Burstable Node-Selectors: ingresstruekubernetes.io/oslinux Tolerations: node.kubernetes.io/disk-pressure:NoSchedule opExistsnode.kubernetes.io/memory-pressure:NoSchedule opExistsnode.kubernetes.io/network-unavailable:NoSchedule opExistsnode.kubernetes.io/not-ready:NoExecute opExistsnode.kubernetes.io/pid-pressure:NoSchedule opExistsnode.kubernetes.io/unreachable:NoExecute opExistsnode.kubernetes.io/unschedulable:NoSchedule opExists Events:Type Reason Age From Message---- ------ ---- ---- -------Normal Scheduled 45s default-scheduler Successfully assigned ingress-nginx/ingress-nginx-controller-jn65t to k8s-node-01Normal Pulling 44s kubelet Pulling image registry.cn-hangzhou.aliyuncs.com/google_containers/nginx-ingress-controller:v1.9.6Normal Pulled 23s kubelet Successfully pulled image registry.cn-hangzhou.aliyuncs.com/google_containers/nginx-ingress-controller:v1.9.6 in 20.899701523sNormal Created 23s kubelet Created container controllerNormal Started 22s kubelet Started container controllerNormal RELOAD 20s nginx-ingress-controller NGINX reload triggered due to a change in configuration[rootk8s-master ingress-nginx]# kubectl get -n ingress-nginx po -owide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES ingress-nginx-controller-jn65t 1/1 Running 0 2m 10.10.10.177 k8s-node-01 none none3.5.5 配置文件 [rootk8s-master ingress-nginx]# grep -Ev ^#|^ #|^ #|^ #|^ #|^\) values.yaml namespaceOverride: commonLabels: {} controller:name: controllerenableAnnotationValidations: falseimage:chroot: falseregistry: registry.cn-hangzhou.aliyuncs.comimage: google_containers/nginx-ingress-controllertag: v1.9.6pullPolicy: IfNotPresentrunAsNonRoot: truerunAsUser: 101allowPrivilegeEscalation: falseseccompProfile:type: RuntimeDefaultreadOnlyRootFilesystem: falseexistingPsp: containerName: controllercontainerPort:http: 80https: 443config: {}configAnnotations: {}proxySetHeaders: {}addHeaders: {}dnsConfig: {}hostAliases: []hostname: {}dnsPolicy: ClusterFirstWithHostNetreportNodeInternalIp: falsewatchIngressWithoutClass: falseingressClassByName: falseenableTopologyAwareRouting: falseallowSnippetAnnotations: falsehostNetwork: truehostPort:enabled: falseports:http: 80https: 443networkPolicy:enabled: falseelectionID: ingressClassResource:name: nginxenabled: truedefault: falsecontrollerValue: k8s.io/ingress-nginxparameters: {}ingressClass: nginxpodLabels: {}podSecurityContext: {}sysctls: {}containerSecurityContext: {}publishService:enabled: truepathOverride: scope:enabled: falsenamespace: namespaceSelector: configMapNamespace: tcp:configMapNamespace: annotations: {}udp:configMapNamespace: annotations: {}maxmindLicenseKey: extraArgs: {}extraEnvs: []kind: DaemonSetannotations: {}labels: {}updateStrategy: {}minReadySeconds: 0tolerations: []affinity: {}topologySpreadConstraints: []terminationGracePeriodSeconds: 300nodeSelector:kubernetes.io/os: linuxingress: truelivenessProbe:httpGet:path: /healthzport: 10254scheme: HTTPinitialDelaySeconds: 10periodSeconds: 10timeoutSeconds: 1successThreshold: 1failureThreshold: 5readinessProbe:httpGet:path: /healthzport: 10254scheme: HTTPinitialDelaySeconds: 10periodSeconds: 10timeoutSeconds: 1successThreshold: 1failureThreshold: 3healthCheckPath: /healthzhealthCheckHost: podAnnotations: {}replicaCount: 1minAvailable: 1resources:requests:cpu: 100mmemory: 90Miautoscaling:enabled: falseannotations: {}minReplicas: 1maxReplicas: 11targetCPUUtilizationPercentage: 50targetMemoryUtilizationPercentage: 50behavior: {}autoscalingTemplate: []keda:apiVersion: keda.sh/v1alpha1enabled: falseminReplicas: 1maxReplicas: 11pollingInterval: 30cooldownPeriod: 300restoreToOriginalReplicaCount: falsescaledObject:annotations: {}triggers: []behavior: {}enableMimalloc: truecustomTemplate:configMapName: configMapKey: service:enabled: trueexternal:enabled: trueannotations: {}labels: {}type: ClusterIPclusterIP: externalIPs: []loadBalancerIP: loadBalancerSourceRanges: []loadBalancerClass: externalTrafficPolicy: sessionAffinity: ipFamilyPolicy: SingleStackipFamilies:- IPv4enableHttp: trueenableHttps: trueports:http: 80https: 443targetPorts:http: httphttps: httpsappProtocol: truenodePorts:http: https: tcp: {}udp: {}internal:enabled: falseannotations: {}type: clusterIP: externalIPs: []loadBalancerIP: loadBalancerSourceRanges: []loadBalancerClass: externalTrafficPolicy: sessionAffinity: ipFamilyPolicy: SingleStackipFamilies:- IPv4ports: {}targetPorts: {}appProtocol: truenodePorts:http: https: tcp: {}udp: {}shareProcessNamespace: falseextraContainers: []extraVolumeMounts: []extraVolumes: []extraInitContainers: []extraModules: []opentelemetry:enabled: falsename: opentelemetryimage:registry: registry.k8s.ioimage: ingress-nginx/opentelemetrytag: v20230721-3e2062ee5digest: sha256:13bee3f5223883d3ca62fee7309ad02d22ec00ff0d7033e3e9aca7a9f60fd472distroless: truecontainerSecurityContext:runAsNonRoot: truerunAsUser: 65532allowPrivilegeEscalation: falseseccompProfile:type: RuntimeDefaultcapabilities:drop:- ALLreadOnlyRootFilesystem: trueresources: {}admissionWebhooks:name: admissionannotations: {}enabled: falseextraEnvs: []failurePolicy: Failport: 8443certificate: /usr/local/certificates/certkey: /usr/local/certificates/keynamespaceSelector: {}objectSelector: {}labels: {}existingPsp: service:annotations: {}externalIPs: []loadBalancerSourceRanges: []servicePort: 443type: ClusterIPcreateSecretJob:name: createsecurityContext:runAsNonRoot: truerunAsUser: 65532allowPrivilegeEscalation: falseseccompProfile:type: RuntimeDefaultcapabilities:drop:- ALLreadOnlyRootFilesystem: trueresources: {}patchWebhookJob:name: patchsecurityContext:runAsNonRoot: truerunAsUser: 65532allowPrivilegeEscalation: falseseccompProfile:type: RuntimeDefaultcapabilities:drop:- ALLreadOnlyRootFilesystem: trueresources: {}patch:enabled: trueimage:registry: registry.cn-hangzhou.aliyuncs.comimage: google_containers/kube-webhook-certgentag: v20231226-1a7112e06priorityClassName: podAnnotations: {}networkPolicy:enabled: falsenodeSelector:kubernetes.io/os: linuxtolerations: []labels: {}securityContext: {}certManager:enabled: falserootCert:duration: admissionCert:duration: metrics:port: 10254portName: metricsenabled: falseservice:annotations: {}labels: {}externalIPs: []loadBalancerSourceRanges: []servicePort: 10254type: ClusterIPserviceMonitor:enabled: falseadditionalLabels: {}annotations: {}namespace: namespaceSelector: {}scrapeInterval: 30stargetLabels: []relabelings: []metricRelabelings: []prometheusRule:enabled: falseadditionalLabels: {}rules: []lifecycle:preStop:exec:command:- /wait-shutdownpriorityClassName: revisionHistoryLimit: 10 defaultBackend:enabled: falsename: defaultbackendimage:registry: registry.k8s.ioimage: defaultbackend-amd64tag: 1.5pullPolicy: IfNotPresentrunAsNonRoot: truerunAsUser: 65534allowPrivilegeEscalation: falseseccompProfile:type: RuntimeDefaultreadOnlyRootFilesystem: trueexistingPsp: extraArgs: {}serviceAccount:create: truename: automountServiceAccountToken: trueextraEnvs: []port: 8080livenessProbe:failureThreshold: 3initialDelaySeconds: 30periodSeconds: 10successThreshold: 1timeoutSeconds: 5readinessProbe:failureThreshold: 6initialDelaySeconds: 0periodSeconds: 5successThreshold: 1timeoutSeconds: 5updateStrategy: {}minReadySeconds: 0tolerations: []affinity: {}podSecurityContext: {}containerSecurityContext: {}podLabels: {}nodeSelector:kubernetes.io/os: linuxpodAnnotations: {}replicaCount: 1minAvailable: 1resources: {}extraVolumeMounts: []extraVolumes: []extraConfigMaps: []autoscaling:annotations: {}enabled: falseminReplicas: 1maxReplicas: 2targetCPUUtilizationPercentage: 50targetMemoryUtilizationPercentage: 50networkPolicy:enabled: falseservice:annotations: {}externalIPs: []loadBalancerSourceRanges: []servicePort: 80type: ClusterIPpriorityClassName: labels: {} rbac:create: truescope: false podSecurityPolicy:enabled: false serviceAccount:create: truename: automountServiceAccountToken: trueannotations: {} imagePullSecrets: [] tcp: {} udp: {} portNamePrefix: dhParam: 3.6 ingress的使用 3.6.1 编写 ingress 服务的配置 apiVersion: networking.k8s.io/v1
kind: Ingress # ingress类型 metadata: name: ingress-nginx-example # ingress的名字annotations: nginx.ingress.kubernetes.io/rewrite-target: /
spec: ingressClassName: nginx rules: - host: k8s.test.cn # 访问域名可是使用通配符http: paths: # 相当于nginx的location配置可以配置多个- path: / # 等价与nginx中的location 路径匹配 # 路径类型按照路径类型进行匹配 ImplementationSpecific 需要指定IngressClass具体匹配规则以IngressClass中的规则为准。# Exact 精确匹配URL需要与path完全匹配上且区分大小写 # Prefix 前缀匹配以/作为分隔符来进行前缀匹配pathType: Prefix # 匹配模式backend: service: name: nginx-svc # ingress转发给serviceservice的名字port: number: 80 # service的端口# 如果有TLS配置可以添加tls字段 #tls: #- hosts: # - example.com # secretName: my-tls-secret3.6.2 创建这个ingress资源 [rootk8s-master ~]# kubectl create -f ingress-nginx-example.yaml ingress.networking.k8s.io/ingress-nginx-example created3.6.3 查看这个ingress资源信息 [rootk8s-master ~]# kubectl get ingress ingress-nginx-example -o wide NAME CLASS HOSTS ADDRESS PORTS AGE ingress-nginx-example nginx k8s.test.cn 10.1.119.138 80 50s[rootk8s-master ~]# kubectl get -n ingress-nginx pod -o wide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES ingress-nginx-controller-jn65t ¹⁄₁ Running 0 62m 10.10.10.177 k8s-node-01 none none3.6.4 测试使用域名访问 [rootk8s-master ~]# echo 10.10.10.177 k8s.test.cn /etc/hosts [rootk8s-master ~]# curl k8s.test.cn !DOCTYPE html html head titleWelcome to nginx!/title stylebody {width: 35em;margin: 0 auto;font-family: Tahoma, Verdana, Arial, sans-serif;} /style /head body h1Welcome to nginx!/h1 pIf you see this page, the nginx web server is successfully installed and working. Further configuration is required./ppFor online documentation and support please refer to a hrefhttp://nginx.org/nginx.org/a.br/ Commercial support is available at a hrefhttp://nginx.com/nginx.com/a./ppemThank you for using nginx./em/p /body /html3.6.5 查询访问日志

[rootk8s-master ~]# kubectl logs -f -n ingress-nginx ingress-nginx-controller-jn65t

NGINX Ingress controllerRelease: v1.9.6Build: 6a73aa3b05040a97ef8213675a16142a9c95952aRepository: https://github.com/kubernetes/ingress-nginxnginx version: nginx/1.21.6——————————————————————————-W0225 11:43:12.164749 7 client_config.go:618] Neither –kubeconfig nor –master was specified. Using the inClusterConfig. This might not work. I0225 11:43:12.165295 7 main.go:205] Creating API client hosthttps://10.1.0.1:443 I0225 11:43:12.177840 7 main.go:249] Running in Kubernetes cluster major1 minor25 gitv1.25.0 stateclean commita866cbe2e5bbaa01cfd5e969aa3e033f3282a8a2 platformlinux/amd64 I0225 11:43:12.436449 7 main.go:101] SSL fake certificate created file/etc/ingress-controller/ssl/default-fake-certificate.pem I0225 11:43:12.565821 7 nginx.go:260] Starting NGINX Ingress controller I0225 11:43:12.627098 7 event.go:298] Event(v1.ObjectReference{Kind:ConfigMap, Namespace:ingress-nginx, Name:ingress-nginx-controller, UID:ffe00f65-b957-4108-ac62-9f88e3b3887f, APIVersion:v1, ResourceVersion:482046, FieldPath:}): type: Normal reason: CREATE ConfigMap ingress-nginx/ingress-nginx-controller I0225 11:43:13.773928 7 nginx.go:303] Starting NGINX process I0225 11:43:13.774090 7 leaderelection.go:245] attempting to acquire leader lease ingress-nginx/ingress-nginx-leader… I0225 11:43:13.777086 7 controller.go:190] Configuration changes detected, backend reload required I0225 11:43:13.793435 7 leaderelection.go:255] successfully acquired lease ingress-nginx/ingress-nginx-leader I0225 11:43:13.795060 7 status.go:84] New leader elected identityingress-nginx-controller-jn65t I0225 11:43:14.211765 7 controller.go:210] Backend successfully reloaded I0225 11:43:14.211878 7 controller.go:221] Initial sync, sleeping for 1 second I0225 11:43:14.211918 7 event.go:298] Event(v1.ObjectReference{Kind:Pod, Namespace:ingress-nginx, Name:ingress-nginx-controller-jn65t, UID:aa348af4-9773-4ca2-b2fc-45eb2c842c83, APIVersion:v1, ResourceVersion:482645, FieldPath:}): type: Normal reason: RELOAD NGINX reload triggered due to a change in configuration I0225 12:43:04.755446 7 store.go:440] Found valid IngressClass ingressdefault/ingress-nginx-example ingressclassnginx I0225 12:43:04.756941 7 event.go:298] Event(v1.ObjectReference{Kind:Ingress, Namespace:default, Name:ingress-nginx-example, UID:cf861f68-6f06-4279-acda-9884e7fd3557, APIVersion:networking.k8s.io/v1, ResourceVersion:488205, FieldPath:}): type: Normal reason: Sync Scheduled for sync I0225 12:43:04.757794 7 controller.go:190] Configuration changes detected, backend reload required I0225 12:43:04.989965 7 controller.go:210] Backend successfully reloaded I0225 12:43:04.990671 7 event.go:298] Event(v1.ObjectReference{Kind:Pod, Namespace:ingress-nginx, Name:ingress-nginx-controller-jn65t, UID:aa348af4-9773-4ca2-b2fc-45eb2c842c83, APIVersion:v1, ResourceVersion:482645, FieldPath:}): type: Normal reason: RELOAD NGINX reload triggered due to a change in configuration I0225 12:43:13.804201 7 status.go:304] updating Ingress status namespacedefault ingressingress-nginx-example currentValuenull newValue[{ip:10.1.119.138}] I0225 12:43:13.813972 7 event.go:298] Event(v1.ObjectReference{Kind:Ingress, Namespace:default, Name:ingress-nginx-example, UID:cf861f68-6f06-4279-acda-9884e7fd3557, APIVersion:networking.k8s.io/v1, ResourceVersion:488223, FieldPath:}): type: Normal reason: Sync Scheduled for sync 10.10.10.100 - - [25/Feb/2024:12:46:25 0000] GET / HTTP/1.1 200 612 - curl/7.29.0 75 0.008 [default-nginx-svc-80] [] 10.2.1.55:80 612 0.008 200 e2b058939e017bdfa86c953e312ea0573.6.6 ingress配置多域名 配置多域名和单域名很相通如下一个例子 apiVersion: networking.k8s.io/v1 kind: Ingress metadata:name: ingress-nginx-exampleannotations:nginx.ingress.kubernetes.io/rewrite-target: / spec:ingressClassName: nginxrules:# 配置第一个域名- host: k8s.test.cnhttp:paths:- path: /pathType: Prefixbackend:service:name: nginx-svcport:number: 80# 配置第二个域名 - host: k8s.test.comhttp:paths:# 配置第一个路径- path: /pathType: Prefixbackend:service:name: nginx-svcport:number: 80# 配置第二个路径 - path: /htmlpathType: Prefixbackend:service:name: nginx-svcport:number: 80