Kubernetes------Service

已于 2024-09-10 22:10:03 修改
阅读量1k 收藏 14
点赞数 7
分类专栏： Kubernetes 文章标签： kubernetes
于 2024-09-10 22:00:00 首次发布
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/weixin_39555954/article/details/141909285
版权

目录

一、属性说明

二、定义和基本配置

 1、定义

 2、创建Service

2.1、type=ClusterIP

 2.2、type=NodePort

 2.3、固定IP访问

三、Service、EndPoint、Pod之间的关系

四、服务发现

1、基于Service中IP访问外部服务

2、基于Service中域名访问外部服务

五、Ingress的安装和使用

1、Ingress是啥

2、Ingress的安装

2.1、安装helm

2.2、环境准备 

2.3、配置SSl证书

六、附录

1、helm安装包

2、values.yml文件修改后的内容

3、Helm和kubernetes版本对照

4、Ingress-nginx和k8s版本对照

一、属性说明

属性名称取值类型是否必须取值说明
versionString✔v1
kindString✔Service
metadataObejct✔元数据
metadata.nameString✔Service名称
metadata.namespaceString✔命名空间，不指定默认为default
metadata.labels[]list自定义标签属性列表
metadata.annotation[]list自定义注解属性列表
specObejct✔详细描述
spec.selector[]list✔Label Selector配置，将选择具有指定Label标签的Pod作为管理范围
spec.typeString✔

Service的类型，默认为ClusterIp。

ClusterIp:虚拟服务IP地址，该地址用于Kubernetes集群内部的Pod访问，在Node上Kube-proxy通过设置的iptables规则进行转发。

NodePort：使用宿主机的端口，使能够访问各Node的外部客户端通过Node的IP地址和端口号就能访问服务。

LoadBanlancer：使用外接负载均衡器完成到服务的负载分发，需要在spec.status.loadBalancer字段指定外部负载均衡器的IP地址，同时定义NodePort和clusterIp，用于公有云环境。

spec.clusterIpString虚拟服务的IP地址，当type=ClusterIP时，如果不指定，则系统进行自动分配，也可以手工指定；type=LoadBalancer时，需要指定。
spec.sessionAffinityString

是否支持Session，可选值为ClientIP，默认值为None。

ClientIp:表示将同一个客户端（根据客户端的IP地址决定）的访问请求都转发到同一个后端Pod。

spec.ports[]listService端口列表
spec.ports[].nameString端口名称
spec.ports[].protocolString端口协议，支持TCP和UDP，默认 为TCP
spec.ports[].portint服务监听的端口号
spec.ports[].targetPortint需要转发到Pod的端口号
spec.ports[].nodePortint当spec.type=NodePort时，指定映射到宿主机的端口号。
StatusObject当spec.type=LoadBalancer时，设置外部负载均衡器的地址，用于公有云。
status.loadBalancerObject外部负载均衡器
status.loadBalancer.ingressObject外部负载均衡器
status.loadBalancer.ingress.ipString外部负载均衡器的ip
status.loadBalancer.ingress.hostnameString外部负载均衡器的主机名

二、定义和基本配置

 1、定义

        Service主要用于提供网络服务，通过Service的定义，能够为客户端应用提供稳定的访问地址（域名或者IP）和负载均衡功能，以及屏蔽后端EndPoint的变化，是Kubernetes实现微服务的核心资源。通常我们的服务都是分布式的，这样就不会是一个单一的Pod，而且Pod还会面对扩容和缩容，除此之外Pod发生了故障转移，这些都会导致Pod的IP发生变化，而Service恰好可以通过自己的负载均衡策略实现请求到Pod上，而不用关注Pod的ip变化。

 2、创建Service

#创建deploy
 kubectl create -f nginx-deploy.yaml

#创建service
 kubectl create -f nginx-svc.yaml 
apiVersion: apps/v1  #版本
kind: Deployment  #类型为Deployment
metadata: #元数据
  labels:  #标签
    app: my-nginx
  name: nginx-deploy
spec: #描述
  replicas: 3 #副本数量
  revisionHistoryLimit: 10  #历史版本限制，用来回退，如果设置为0则没有回退
  selector: #选择器
    matchLabels: #按标签匹配
      app: my-nginx #标签的值
  template:
    metadata:
      labels:
        app: my-nginx
    spec: #容器描述
      containers:
        - name: nginx-container
          image: nginx:1.21.4
          imagePullPolicy: IfNotPresent
          ports:
            - containerPort: 80
              name: nginx-port
              protocol: TCP

apiVersion: v1
kind: Service #类型
metadata: #元数据
  name: nginx-svc  #service的名称
  labels:
    app: nginx-svc #自身的标签
spec:
  selector:
    app: my-nginx  #所有匹配到改标签的pod都可以通过service访问
  ports:
    - protocol: TCP  #可选值TCP、UDP、SCTP 默认为 TCP
      port: 80 #service自己的端口，通过内网访问你的端口
      targetPort: 80 #目标端口
  type: ClusterIP #nodeport 随机端口 30000-32000，该端口直接绑定到node上，且每个节点都会绑定该端口，可以暴露端口供外部访问
                  # ClusterIP 默认值

#创建资源
kubectl create -f nginx-deploy.yaml 

kubectl create -f nginx-svc.yaml 

#查看service
kubectl get services

kubectl get svc

#查看endpoint
kubectl get endpoints

kubectl get ep

#查看pod
kubectl get po -o wide

 

 分别修改三个Pod中nginx的内容

#分别进入容器，修改nginx欢迎页内容
kubectl exec nginx-deploy-6c648dd6dd-867b6 -it -- /bin/sh

kubectl exec nginx-deploy-6c648dd6dd-pj5tp -it -- /bin/sh 

kubectl exec nginx-deploy-6c648dd6dd-tgl82 -it -- /bin/sh  


echo "10.244.1.145   node2" > /usr/share/nginx/html/index.html

echo "10.244.1.144   node2" > /usr/share/nginx/html/index.html

echo "172.17.0.3   node1" > /usr/share/nginx/html/index.html

2.1、type=ClusterIP

 该地址用于Kubernetes内部Pod访问。通过service访问nginx

#通过service访问nginx
while true ;do curl 10.97.61.178 ; sleep 1;done;

 可以看到Service是随机访问到pod的。

#编辑deploy对pod扩容，将副本数改为4
kubectl edit deploy nginx-deploy

#查看Pod
kubectl get po -o wide

 

 再次通过service访问pod，是可以访问到扩容的这个pod的。

 2.2、type=NodePort

使用宿主机的端口，使能够访问各Node的外部客户端通过Node的IP地址和端口号就能访问服务。

apiVersion: v1
kind: Service #类型
metadata: #元数据
  name: nginx-svc  #service的名称
  labels:
    app: nginx-svc #自身的标签
spec:
  selector:
    app: my-nginx  #所有匹配到改标签的pod都可以通过service访问
  ports:
    - protocol: TCP  #可选值TCP、UDP、SCTP 默认为 TCP
      port: 80 #service自己的端口，通过内网访问你的端口
      targetPort: 80 #目标端口
      nodePort: 30080  #指定端口访问 ,外部访问，绑定到主机node上的，端口范围为30000-32767
  type: NodePort
#创建资源
kubectl create -f nginx-svc.yaml 

#查看svc
kubectl get svc

 

 2.3、固定IP访问

apiVersion: v1
kind: Service #类型
metadata: #元数据
  name: nginx-svc  #service的名称
  labels:
    app: nginx-svc #自身的标签
spec:
  selector:
    app: my-nginx  #所有匹配到改标签的pod都可以通过service访问
  ports:
    - protocol: TCP  #可选值TCP、UDP、SCTP 默认为 TCP
      port: 80 #service自己的端口，通过内网访问你的端口
      targetPort: 80 #目标pod端口
  type: ClusterIP
  sessionAffinity: ClientIP #指定客户端ip访问，默认是None
  sessionAffinityConfig:  #会话配置
    clientIP:
      timeoutSeconds: 3600 #会话保持的最长时间，单位为秒

#创建资源
kubectl create -f nginx-svc.yaml

#查看
kubectl get svc

#通过service访问pod,只会访问一个pod
while true ;do curl 10.111.86.26 ; sleep 1;done;

 

 

三、Service、EndPoint、Pod之间的关系

     

Endpoint 类似我们在之前所学习的 服务注册中心 （eureka、nacos）。Endpoint是Kubernetes中的一个资源对象，存储在etcd中，用于记录一个service对应的所有pod的访问地址。

一个Service由一组Pod（通过标签关联）组成，这些Pod通过Endpoints暴露出来，Endpoints是实现实际服务的端点集合。

通俗易懂总结：kubernetes 中的 Service与Endpoints通讯获取实际服务地址，在路由转发到具体pod上。

四、服务发现

1、基于Service中IP访问外部服务

       普通的Service通过Label Selector对后端Endpoint列表进行了一次抽象，如果后端Endpoint不是由Pod副本提供，则Service还可以抽象定义为任意其他服务，将一个Kubernetes集群外的已知服务定义为Kubernetes内的一个Service，供集群内的其他应用访问。常见的应用场景

  • 已部署的一个集群外服务，比如 数据库服务，缓存服务等。
  • 其他Kubernetes集群的某个服务。
  • 迁移过程中对某个服务进行Kubernetes内的服务名访问机制的验证。
apiVersion: v1
kind: Service #类型
metadata: #元数据
  name: nginx-svc-external  #service的名称
  labels:
    app: nginx #自身的标签
spec:
  ports:
    - port: 80 #service自己的端口，通过内网访问你的端口
      targetPort: 80 #目标pod端口
      name: web
  type: ClusterIP

---
#自定义Endpoint

apiVersion: v1
kind: Endpoints  #类型
metadata:
  labels:
    app: nginx #与上面service保持一致
  name: nginx-svc-external #与service一样
  namespace: default #命名空间
subsets:
  - addresses:
      - ip: 192.168.139.1 #目标ip，当集群内部访问到该service时，会转发到该ip上，这里测试ip为本机ip，外网访问的ip同样适用
    ports:
      - port: 8080  #端口，这里我配置的是tomcat
        name: web  #端口名字，与上面service一致
        protocol: TCP #与Service一致



#创建资源
 kubectl create -f nginx-svc-external-ip.yaml

#查看svc,ep
kubectl get svc,ep

#使用busybox容器检测，没有的可以创建
kubectl run -it --image busybox:1.28.4 dns-test  -- /bin/sh

#已存在使用该指令进入pod
kubectl exec -it dns-test -- sh

#进入pod内使用wget命令检测，其中nginx-svc-external为服务的名称，支持跨namespace访问，访问方式为<serviceName>.<namespace>
wget http://nginx-svc-external

 

结论：可以看到通过访问service服务已经访问到了Tomcat的服务。

2、基于Service中域名访问外部服务

apiVersion: v1
kind: Service #类型
metadata: #元数据
  name: nginx-svc-external-domain  #service的名称
  labels:
    app: nginx-svc-external-domain #自身的标签
spec:
  type: ExternalName
  externalName: www.wssnail.com




#创建资源
 kubectl create -f nginx-svc-external-domain.yaml

#查看
kubectl get svc

 

五、Ingress的安装和使用

1、Ingress是啥

        Ingress提供从集群外部到集群内服务的 HTTP 和 HTTPS 路由。 流量路由由 Ingress 资源所定义的规则来控制。使用Ingress进行服务路由时，Ingress Controller 基于Ingress 规则将客户端请求直接转发到Service对应的后端Endpoint上，这样会跳过kube-proxy设置的路由转发规则，提高网络转发效率。下面是Ingress网络访问的示意图。

​

  •  对www.wsssnail.com/api的访问将被路由到api的service，然后通过service访问到它管理的pod
  •  对www.wsssnail.com/web的访问将被路由到web的service，然后通过service访问到它管理的pod
  •  对www.wsssnail.com/doc的访问将被路由到doc的service，然后通过service访问到它管理的pod

2、Ingress的安装

2.1、安装helm

#官方地址
https://helm.sh/zh/docs/intro/install/

#创建目录helm
mkdir helm

#进入目录 下载helm包
wget https://get.helm.sh/helm-v3.11.3-linux-amd64.tar.gz

#解压文件并移动helm文件到/usr/local/bin
tar -zxf helm-v3.11.3-linux-amd64.tar.gz 

#移动文件
mv helm /usr/local/bin/

#查看版本
helm version

#添加仓库
helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx

#查看仓库列表
helm repo list

#搜索
helm search repo ingress-nginx

#拉取，指定版本
helm pull ingress-nginx/ingress-nginx --version 4.5.0

#移动文件到/helm文件
mv ingress-nginx-4.5.0.tgz /root/helm/

#解压文件
tar -xf ingress-nginx-4.5.0.tgz 

#进入ingress-nginx目录修改value.yml文件，主要修改镜像地址和镜像，以及node标签

values.yml修改后的完整文件见附录2


#创建命名空间
 kubectl create ns ingress-nginx

#给节点打标签
kubectl label node node1 ingress=true

#执行安装，注意后面有个点别丢了
helm install ingress-nginx -n ingress-nginx .

#查看
kubectl get po -n ingress-nginx



#如果安装失败了卸载helm库

#查看helm列表
 helm list -n <namespace>

#卸载
helm delete ingress-nginx -n  <namespace>

 

2.2、环境准备 

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: example
#  annotations:
#    kubernetes.io/ingerss.class: "nginx"
#    nginx.ingress.kubernetes.io/enable-cors: "true"     # 启用CORS。
#    nginx.ingress.kubernetes.io/cors-allow-origin: "*"  # 允许所有域访问。
#    nginx.ingress.kubernetes.io/cors-allow-methods: "GET, PUT, POST, DELETE, PATCH, OPTIONS"  # 允许的HTTP方法。
spec:
  ingressClassName: nginx
  rules:
    - host: test.wssnail.com
      http:
        paths:
          - pathType: Prefix
            backend:
              service:
                name: nginx-svc
                port:
                  number: 80
            path: /
  tls:
    - hosts:
        - test.wssnail.com
      secretName: ingress-secret
#---
#apiVersion: v1
#kind: Secret
#metadata:
#    name: example-tls
#data:
#    tls.crt: <base64 encoded cert>
#    tls.key: <base64 encoded key>
#type: kubernetes.io/tls

apiVersion: apps/v1  #版本
kind: Deployment  #类型为Deployment
metadata: #元数据
  name: nginx-deploy-test-ingress
spec: #描述
  replicas: 3 #副本数量
  selector: #选择器
    matchLabels:
      app: nginx-test-ingress #标签的值
  template:
    metadata:
      labels:
        app: nginx-test-ingress
    spec: #容器描述
      containers:
        - name: nginx-container
          image: nginx:1.21.6
          imagePullPolicy: IfNotPresent
          ports:
            - containerPort: 80
              name: nginx-port
              protocol: TCP
---
apiVersion: v1
kind: Service #类型
metadata: #元数据
  name: nginx-svc  #service的名称
  labels:
    app: nginx-test-ingress #自身的标签
spec:
  selector:
    app: nginx-test-ingress  #所有匹配到改标签的pod都可以通过service访问
  ports:
    - protocol: TCP  #可选值TCP、UDP、SCTP 默认为 TCP
      port: 80 #service自己的端口，通过内网访问你的端口
      name: web
  type: NodePort
#创建资源
kubectl create -f ingress-nginx.yaml 
kubectl create -f nginx-svc-test-ingress.yaml

 配置主机host，在C:\Windows\System32\drivers\etc路径下添加dns解析 

192.168.139.207  test.wssnail.com  #其中ip为ingress pod所在节点的ip

 此域名我在浏览器访问的时候出现了跨域问题，目前不知道怎么解决，但是可以ping通，证明ingress已经转发到了相应的服务上。

 

2.3、配置SSl证书

 生成证书

#使用openssl生成证书,生成证书会生成证书文件
 openssl req -x509 -nodes -days 500 -newkey rsa:2048 -keyout tls.key -out tls.crt -subj "/CN=test.wssnail.com"

 创建secret

#创建secret ,其中ingress-secret为证书名称， tls.key、tls.crt对应上一步生成的文件
kubectl create secret tls ingress-secret --key tls.key --cert tls.crt

创建ingress

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: example
#  annotations:
#    kubernetes.io/ingerss.class: "nginx"
#    nginx.ingress.kubernetes.io/enable-cors: "true"     # 启用CORS。
#    nginx.ingress.kubernetes.io/cors-allow-origin: "*"  # 允许所有域访问。
#    nginx.ingress.kubernetes.io/cors-allow-methods: "GET, PUT, POST, DELETE, PATCH, OPTIONS"  # 允许的HTTP方法。
spec:
  ingressClassName: nginx
  rules:
    - host: test.wssnail.com
      http:
        paths:
          - pathType: Prefix
            backend:
              service:
                name: nginx-svc
                port:
                  number: 80
            path: /
  tls:
    - hosts:
        - test.wssnail.com
      secretName: ingress-secret  #对应创建secret的名字


#---
#apiVersion: v1
#kind: Secret
#metadata:
#    name: example-tls
#data:
#    tls.crt: <base64 encoded cert>  直接使用base64转码后的内容
#    tls.key: <base64 encoded key>
#type: kubernetes.io/tls
#创建资源，再访问域名就可以访问https
kubectl create -f ingress-nginx.yaml

六、附录

1、helm安装包

链接: https://pan.baidu.com/s/1Pve4W3cMGh9HvasapL-81A?pwd=iafb 提取码: iafb 

2、values.yml文件修改后的内容

## nginx configuration
## Ref: https://github.com/kubernetes/ingress-nginx/blob/main/docs/user-guide/nginx-configuration/index.md
##

## Overrides for generated resource names
# See templates/_helpers.tpl
# nameOverride:
# fullnameOverride:

## Labels to apply to all resources
##
commonLabels: {}
# scmhash: abc123
# myLabel: aakkmd

controller:
    name: controller
    image:
        ## Keep false as default for now!
        chroot: false
        registry: registry.cn-hangzhou.aliyuncs.com  #此处修改镜像
        image: google_containers/nginx-ingress-controller #此处修改镜像
        ## for backwards compatibility consider setting the full image url via the repository value below
        ## use *either* current default registry/image or repository format or installing chart by providing the values.yaml will fail
        ## repository:
        tag: "v1.6.3"
        #digest: sha256:b92667e0afde1103b736e6a3f00dd75ae66eec4e71827d19f19f471699e909d2  #此处注释掉验证
        #digestChroot: sha256:4b4a249c9a35ac16a8ec0e22f6c522b8707f7e59e656e64a4ad9ace8fea830a4 #此处注释掉验证
        pullPolicy: IfNotPresent
        # www-data -> uid 101
        runAsUser: 101
        allowPrivilegeEscalation: true
    # -- Use an existing PSP instead of creating one
    existingPsp: ""
    # -- Configures the controller container name
    containerName: controller
    # -- Configures the ports that the nginx-controller listens on
    containerPort:
        http: 80
        https: 443
    # -- Will add custom configuration options to Nginx https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/
    config: {}
    # -- Annotations to be added to the controller config configuration configmap.
    configAnnotations: {}
    # -- Will add custom headers before sending traffic to backends according to https://github.com/kubernetes/ingress-nginx/tree/main/docs/examples/customization/custom-headers
    proxySetHeaders: {}
    # -- Will add custom headers before sending response traffic to the client according to: https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/#add-headers
    addHeaders: {}
    # -- Optionally customize the pod dnsConfig.
    dnsConfig: {}
    # -- Optionally customize the pod hostname.
    hostname: {}
    # -- Optionally change this to ClusterFirstWithHostNet in case you have 'hostNetwork: true'.
    # By default, while using host network, name resolution uses the host's DNS. If you wish nginx-controller
    # to keep resolving names inside the k8s network, use ClusterFirstWithHostNet.
    #dnsPolicy: ClusterFirst
    dnsPolicy: ClusterFirstWithHostNet #此处修改
    # -- Bare-metal considerations via the host network https://kubernetes.github.io/ingress-nginx/deploy/baremetal/#via-the-host-network
    # Ingress status was blank because there is no Service exposing the NGINX Ingress controller in a configuration using the host network, the default --publish-service flag used in standard cloud setups does not apply
    reportNodeInternalIp: false
    # -- Process Ingress objects without ingressClass annotation/ingressClassName field
    # Overrides value for --watch-ingress-without-class flag of the controller binary
    # Defaults to false
    watchIngressWithoutClass: false
    # -- Process IngressClass per name (additionally as per spec.controller).
    ingressClassByName: false
    # -- This configuration enables Topology Aware Routing feature, used together with service annotation service.kubernetes.io/topology-aware-hints="auto"
    # Defaults to false
    enableTopologyAwareRouting: false
    # -- This configuration defines if Ingress Controller should allow users to set
    # their own *-snippet annotations, otherwise this is forbidden / dropped
    # when users add those annotations.
    # Global snippets in ConfigMap are still respected
    allowSnippetAnnotations: true
    # -- Required for use with CNI based kubernetes installations (such as ones set up by kubeadm),
    # since CNI and hostport don't mix yet. Can be deprecated once https://github.com/kubernetes/kubernetes/issues/23920
    # is merged
    hostNetwork: true  #此处修改
    ## Use host ports 80 and 443
    ## Disabled by default
    hostPort:
        # -- Enable 'hostPort' or not
        enabled: false
        ports:
            # -- 'hostPort' http port
            http: 80
            # -- 'hostPort' https port
            https: 443
    # -- Election ID to use for status update, by default it uses the controller name combined with a suffix of 'leader'
    electionID: ""
    ## This section refers to the creation of the IngressClass resource
    ## IngressClass resources are supported since k8s >= 1.18 and required since k8s >= 1.19
    ingressClassResource:
        # -- Name of the ingressClass
        name: nginx
        # -- Is this ingressClass enabled or not
        enabled: true
        # -- Is this the default ingressClass for the cluster
        default: false
        # -- Controller-value of the controller that is processing this ingressClass
        controllerValue: "k8s.io/ingress-nginx"
        # -- Parameters is a link to a custom resource containing additional
        # configuration for the controller. This is optional if the controller
        # does not require extra parameters.
        parameters: {}
    # -- For backwards compatibility with ingress.class annotation, use ingressClass.
    # Algorithm is as follows, first ingressClassName is considered, if not present, controller looks for ingress.class annotation
    ingressClass: nginx
    # -- Labels to add to the pod container metadata
    podLabels: {}
    #  key: value

    # -- Security Context policies for controller pods
    podSecurityContext: {}
    # -- See https://kubernetes.io/docs/tasks/administer-cluster/sysctl-cluster/ for notes on enabling and using sysctls
    sysctls: {}
    # sysctls:
    #   "net.core.somaxconn": "8192"

    # -- Allows customization of the source of the IP address or FQDN to report
    # in the ingress status field. By default, it reads the information provided
    # by the service. If disable, the status field reports the IP address of the
    # node or nodes where an ingress controller pod is running.
    publishService:
        # -- Enable 'publishService' or not
        enabled: true
        # -- Allows overriding of the publish service to bind to
        # Must be <namespace>/<service_name>
        pathOverride: ""
    # Limit the scope of the controller to a specific namespace
    scope:
        # -- Enable 'scope' or not
        enabled: false
        # -- Namespace to limit the controller to; defaults to $(POD_NAMESPACE)
        namespace: ""
        # -- When scope.enabled == false, instead of watching all namespaces, we watching namespaces whose labels
        # only match with namespaceSelector. Format like foo=bar. Defaults to empty, means watching all namespaces.
        namespaceSelector: ""
    # -- Allows customization of the configmap / nginx-configmap namespace; defaults to $(POD_NAMESPACE)
    configMapNamespace: ""
    tcp:
        # -- Allows customization of the tcp-services-configmap; defaults to $(POD_NAMESPACE)
        configMapNamespace: ""
        # -- Annotations to be added to the tcp config configmap
        annotations: {}
    udp:
        # -- Allows customization of the udp-services-configmap; defaults to $(POD_NAMESPACE)
        configMapNamespace: ""
        # -- Annotations to be added to the udp config configmap
        annotations: {}
    # -- Maxmind license key to download GeoLite2 Databases.
    ## https://blog.maxmind.com/2019/12/18/significant-changes-to-accessing-and-using-geolite2-databases
    maxmindLicenseKey: ""
    # -- Additional command line arguments to pass to nginx-ingress-controller
    # E.g. to specify the default SSL certificate you can use
    extraArgs: {}
    ## extraArgs:
    ##   default-ssl-certificate: "<namespace>/<secret_name>"

    # -- Additional environment variables to set
    extraEnvs: []
    # extraEnvs:
    #   - name: FOO
    #     valueFrom:
    #       secretKeyRef:
    #         key: FOO
    #         name: secret-resource

    # -- Use a `DaemonSet` or `Deployment`
    kind: DaemonSet  #此处修改为DaemonSet
    # -- Annotations to be added to the controller Deployment or DaemonSet
    ##
    annotations: {}
    #  keel.sh/pollSchedule: "@every 60m"

    # -- Labels to be added to the controller Deployment or DaemonSet and other resources that do not have option to specify labels
    ##
    labels: {}
    #  keel.sh/policy: patch
    #  keel.sh/trigger: poll

    # -- The update strategy to apply to the Deployment or DaemonSet
    ##
    updateStrategy: {}
    #  rollingUpdate:
    #    maxUnavailable: 1
    #  type: RollingUpdate

    # -- `minReadySeconds` to avoid killing pods before we are ready
    ##
    minReadySeconds: 0
    # -- Node tolerations for server scheduling to nodes with taints
    ## Ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/
    ##
    tolerations: []
    #  - key: "key"
    #    operator: "Equal|Exists"
    #    value: "value"
    #    effect: "NoSchedule|PreferNoSchedule|NoExecute(1.6 only)"

    # -- Affinity and anti-affinity rules for server scheduling to nodes
    ## Ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity
    ##
    affinity: {}
    # # An example of preferred pod anti-affinity, weight is in the range 1-100
    # podAntiAffinity:
    #   preferredDuringSchedulingIgnoredDuringExecution:
    #   - weight: 100
    #     podAffinityTerm:
    #       labelSelector:
    #         matchExpressions:
    #         - key: app.kubernetes.io/name
    #           operator: In
    #           values:
    #           - ingress-nginx
    #         - key: app.kubernetes.io/instance
    #           operator: In
    #           values:
    #           - ingress-nginx
    #         - key: app.kubernetes.io/component
    #           operator: In
    #           values:
    #           - controller
    #       topologyKey: kubernetes.io/hostname

    # # An example of required pod anti-affinity
    # podAntiAffinity:
    #   requiredDuringSchedulingIgnoredDuringExecution:
    #   - labelSelector:
    #       matchExpressions:
    #       - key: app.kubernetes.io/name
    #         operator: In
    #         values:
    #         - ingress-nginx
    #       - key: app.kubernetes.io/instance
    #         operator: In
    #         values:
    #         - ingress-nginx
    #       - key: app.kubernetes.io/component
    #         operator: In
    #         values:
    #         - controller
    #     topologyKey: "kubernetes.io/hostname"

    # -- Topology spread constraints rely on node labels to identify the topology domain(s) that each Node is in.
    ## Ref: https://kubernetes.io/docs/concepts/workloads/pods/pod-topology-spread-constraints/
    ##
    topologySpreadConstraints: []
    # - maxSkew: 1
    #   topologyKey: topology.kubernetes.io/zone
    #   whenUnsatisfiable: DoNotSchedule
    #   labelSelector:
    #     matchLabels:
    #       app.kubernetes.io/instance: ingress-nginx-internal

    # -- `terminationGracePeriodSeconds` to avoid killing pods before we are ready
    ## wait up to five minutes for the drain of connections
    ##
    terminationGracePeriodSeconds: 300
    # -- Node labels for controller pod assignment
    ## Ref: https://kubernetes.io/docs/user-guide/node-selection/
    ##
    nodeSelector:
        kubernetes.io/os: linux
        ingress: "true"  #此处修改，节点选择器
    ## Liveness and readiness probe values
    ## Ref: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#container-probes
    ##
    ## startupProbe:
    ##   httpGet:
    ##     # should match container.healthCheckPath
    ##     path: "/healthz"
    ##     port: 10254
    ##     scheme: HTTP
    ##   initialDelaySeconds: 5
    ##   periodSeconds: 5
    ##   timeoutSeconds: 2
    ##   successThreshold: 1
    ##   failureThreshold: 5
    livenessProbe:
        httpGet:
            # should match container.healthCheckPath
            path: "/healthz"
            port: 10254
            scheme: HTTP
        initialDelaySeconds: 10
        periodSeconds: 10
        timeoutSeconds: 1
        successThreshold: 1
        failureThreshold: 5
    readinessProbe:
        httpGet:
            # should match container.healthCheckPath
            path: "/healthz"
            port: 10254
            scheme: HTTP
        initialDelaySeconds: 10
        periodSeconds: 10
        timeoutSeconds: 1
        successThreshold: 1
        failureThreshold: 3
    # -- Path of the health check endpoint. All requests received on the port defined by
    # the healthz-port parameter are forwarded internally to this path.
    healthCheckPath: "/healthz"
    # -- Address to bind the health check endpoint.
    # It is better to set this option to the internal node address
    # if the ingress nginx controller is running in the `hostNetwork: true` mode.
    healthCheckHost: ""
    # -- Annotations to be added to controller pods
    ##
    podAnnotations: {}
    replicaCount: 1
    # -- Define either 'minAvailable' or 'maxUnavailable', never both.
    minAvailable: 1
    # -- Define either 'minAvailable' or 'maxUnavailable', never both.
    # maxUnavailable: 1

    ## Define requests resources to avoid probe issues due to CPU utilization in busy nodes
    ## ref: https://github.com/kubernetes/ingress-nginx/issues/4735#issuecomment-551204903
    ## Ideally, there should be no limits.
    ## https://engineering.indeedblog.com/blog/2019/12/cpu-throttling-regression-fix/
    resources:
        ##  limits:
        ##    cpu: 100m
        ##    memory: 90Mi
        requests:
            cpu: 100m
            memory: 90Mi
    # Mutually exclusive with keda autoscaling
    autoscaling:
        apiVersion: autoscaling/v2
        enabled: false
        annotations: {}
        minReplicas: 1
        maxReplicas: 11
        targetCPUUtilizationPercentage: 50
        targetMemoryUtilizationPercentage: 50
        behavior: {}
        # scaleDown:
        #   stabilizationWindowSeconds: 300
        #   policies:
        #   - type: Pods
        #     value: 1
        #     periodSeconds: 180
        # scaleUp:
        #   stabilizationWindowSeconds: 300
        #   policies:
        #   - type: Pods
        #     value: 2
        #     periodSeconds: 60
    autoscalingTemplate: []
    # Custom or additional autoscaling metrics
    # ref: https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/#support-for-custom-metrics
    # - type: Pods
    #   pods:
    #     metric:
    #       name: nginx_ingress_controller_nginx_process_requests_total
    #     target:
    #       type: AverageValue
    #       averageValue: 10000m

    # Mutually exclusive with hpa autoscaling
    keda:
        apiVersion: "keda.sh/v1alpha1"
        ## apiVersion changes with keda 1.x vs 2.x
        ## 2.x = keda.sh/v1alpha1
        ## 1.x = keda.k8s.io/v1alpha1
        enabled: false
        minReplicas: 1
        maxReplicas: 11
        pollingInterval: 30
        cooldownPeriod: 300
        restoreToOriginalReplicaCount: false
        scaledObject:
            annotations: {}
            # Custom annotations for ScaledObject resource
            #  annotations:
            # key: value
        triggers: []
        #     - type: prometheus
        #       metadata:
        #         serverAddress: http://<prometheus-host>:9090
        #         metricName: http_requests_total
        #         threshold: '100'
        #         query: sum(rate(http_requests_total{deployment="my-deployment"}[2m]))

        behavior: {}
    #     scaleDown:
    #       stabilizationWindowSeconds: 300
    #       policies:
    #       - type: Pods
    #         value: 1
    #         periodSeconds: 180
    #     scaleUp:
    #       stabilizationWindowSeconds: 300
    #       policies:
    #       - type: Pods
    #         value: 2
    #         periodSeconds: 60

    # -- Enable mimalloc as a drop-in replacement for malloc.
    ## ref: https://github.com/microsoft/mimalloc
    ##
    enableMimalloc: true
    ## Override NGINX template
    customTemplate:
        configMapName: ""
        configMapKey: ""
    service:
        enabled: true
        # -- If enabled is adding an appProtocol option for Kubernetes service. An appProtocol field replacing annotations that were
        # using for setting a backend protocol. Here is an example for AWS: service.beta.kubernetes.io/aws-load-balancer-backend-protocol: http
        # It allows choosing the protocol for each backend specified in the Kubernetes service.
        # See the following GitHub issue for more details about the purpose: https://github.com/kubernetes/kubernetes/issues/40244
        # Will be ignored for Kubernetes versions older than 1.20
        ##
        appProtocol: true
        annotations: {}
        labels: {}
        # clusterIP: ""

        # -- List of IP addresses at which the controller services are available
        ## Ref: https://kubernetes.io/docs/user-guide/services/#external-ips
        ##
        externalIPs: []
        # -- Used by cloud providers to connect the resulting `LoadBalancer` to a pre-existing static IP according to https://kubernetes.io/docs/concepts/services-networking/service/#loadbalancer
        loadBalancerIP: ""
        loadBalancerSourceRanges: []
        enableHttp: true
        enableHttps: true
        ## Set external traffic policy to: "Local" to preserve source IP on providers supporting it.
        ## Ref: https://kubernetes.io/docs/tutorials/services/source-ip/#source-ip-for-services-with-typeloadbalancer
        # externalTrafficPolicy: ""

        ## Must be either "None" or "ClientIP" if set. Kubernetes will default to "None".
        ## Ref: https://kubernetes.io/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies
        # sessionAffinity: ""

        ## Specifies the health check node port (numeric port number) for the service. If healthCheckNodePort isn’t specified,
        ## the service controller allocates a port from your cluster’s NodePort range.
        ## Ref: https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/#preserving-the-client-source-ip
        # healthCheckNodePort: 0

        # -- Represents the dual-stack-ness requested or required by this Service. Possible values are
        # SingleStack, PreferDualStack or RequireDualStack.
        # The ipFamilies and clusterIPs fields depend on the value of this field.
        ## Ref: https://kubernetes.io/docs/concepts/services-networking/dual-stack/
        ipFamilyPolicy: "SingleStack"
        # -- List of IP families (e.g. IPv4, IPv6) assigned to the service. This field is usually assigned automatically
        # based on cluster configuration and the ipFamilyPolicy field.
        ## Ref: https://kubernetes.io/docs/concepts/services-networking/dual-stack/
        ipFamilies:
            - IPv4
        ports:
            http: 80
            https: 443
        targetPorts:
            http: http
            https: https
        #type: LoadBalancer  
        type: ClusterIP  #此处修改
        ## type: NodePort
        ## nodePorts:
        ##   http: 32080
        ##   https: 32443
        ##   tcp:
        ##     8080: 32808
        nodePorts:
            http: ""
            https: ""
            tcp: {}
            udp: {}
        external:
            enabled: true
        internal:
            # -- Enables an additional internal load balancer (besides the external one).
            enabled: false
            # -- Annotations are mandatory for the load balancer to come up. Varies with the cloud service.
            annotations: {}
            # loadBalancerIP: ""

            # -- Restrict access For LoadBalancer service. Defaults to 0.0.0.0/0.
            loadBalancerSourceRanges: []
            ## Set external traffic policy to: "Local" to preserve source IP on
            ## providers supporting it
            ## Ref: https://kubernetes.io/docs/tutorials/services/source-ip/#source-ip-for-services-with-typeloadbalancer
            # externalTrafficPolicy: ""
    # shareProcessNamespace enables process namespace sharing within the pod.
    # This can be used for example to signal log rotation using `kill -USR1` from a sidecar.
    shareProcessNamespace: false
    # -- Additional containers to be added to the controller pod.
    # See https://github.com/lemonldap-ng-controller/lemonldap-ng-controller as example.
    extraContainers: []
    #  - name: my-sidecar
    #    image: nginx:latest
    #  - name: lemonldap-ng-controller
    #    image: lemonldapng/lemonldap-ng-controller:0.2.0
    #    args:
    #      - /lemonldap-ng-controller
    #      - --alsologtostderr
    #      - --configmap=$(POD_NAMESPACE)/lemonldap-ng-configuration
    #    env:
    #      - name: POD_NAME
    #        valueFrom:
    #          fieldRef:
    #            fieldPath: metadata.name
    #      - name: POD_NAMESPACE
    #        valueFrom:
    #          fieldRef:
    #            fieldPath: metadata.namespace
    #    volumeMounts:
    #    - name: copy-portal-skins
    #      mountPath: /srv/var/lib/lemonldap-ng/portal/skins

    # -- Additional volumeMounts to the controller main container.
    extraVolumeMounts: []
    #  - name: copy-portal-skins
    #   mountPath: /var/lib/lemonldap-ng/portal/skins

    # -- Additional volumes to the controller pod.
    extraVolumes: []
    #  - name: copy-portal-skins
    #    emptyDir: {}

    # -- Containers, which are run before the app containers are started.
    extraInitContainers: []
    # - name: init-myservice
    #   image: busybox
    #   command: ['sh', '-c', 'until nslookup myservice; do echo waiting for myservice; sleep 2; done;']

    # -- Modules, which are mounted into the core nginx image. See values.yaml for a sample to add opentelemetry module
    extraModules: []
    #   containerSecurityContext:
    #     allowPrivilegeEscalation: false
    #
    # The image must contain a `/usr/local/bin/init_module.sh` executable, which
    # will be executed as initContainers, to move its config files within the
    # mounted volume.

    opentelemetry:
        enabled: false
        image: registry.k8s.io/ingress-nginx/opentelemetry:v20230107-helm-chart-4.4.2-2-g96b3d2165@sha256:331b9bebd6acfcd2d3048abbdd86555f5be76b7e3d0b5af4300b04235c6056c9
        containerSecurityContext:
            allowPrivilegeEscalation: false
    admissionWebhooks:
        annotations: {}
        # ignore-check.kube-linter.io/no-read-only-rootfs: "This deployment needs write access to root filesystem".

        ## Additional annotations to the admission webhooks.
        ## These annotations will be added to the ValidatingWebhookConfiguration and
        ## the Jobs Spec of the admission webhooks.
        enabled: false #此处修改，不使用ssl
        # -- Additional environment variables to set
        extraEnvs: []
        # extraEnvs:
        #   - name: FOO
        #     valueFrom:
        #       secretKeyRef:
        #         key: FOO
        #         name: secret-resource
        # -- Admission Webhook failure policy to use
        failurePolicy: Fail
        # timeoutSeconds: 10
        port: 8443
        certificate: "/usr/local/certificates/cert"
        key: "/usr/local/certificates/key"
        namespaceSelector: {}
        objectSelector: {}
        # -- Labels to be added to admission webhooks
        labels: {}
        # -- Use an existing PSP instead of creating one
        existingPsp: ""
        networkPolicyEnabled: false
        service:
            annotations: {}
            # clusterIP: ""
            externalIPs: []
            # loadBalancerIP: ""
            loadBalancerSourceRanges: []
            servicePort: 443
            type: ClusterIP
        createSecretJob:
            securityContext:
                allowPrivilegeEscalation: false
            resources: {}
            # limits:
            #   cpu: 10m
            #   memory: 20Mi
            # requests:
            #   cpu: 10m
            #   memory: 20Mi
        patchWebhookJob:
            securityContext:
                allowPrivilegeEscalation: false
            resources: {}
        patch:
            enabled: true
            image:
                registry: registry.cn-hangzhou.aliyuncs.com  #此处修改 修改镜像地址
                image: google_containers/kube-webhook-certgen #此处修改 修改镜像
                ## for backwards compatibility consider setting the full image url via the repository value below
                ## use *either* current default registry/image or repository format or installing chart by providing the values.yaml will fail
                ## repository:
                #tag: v20220916-gd32f8c343
                tag: v1.3.0
                #digest: sha256:39c5b2e3310dc4264d638ad28d9d1d96c4cbb2b2dcfb52368fe4e3c63f61e10f
                pullPolicy: IfNotPresent
            # -- Provide a priority class name to the webhook patching job
            ##
            priorityClassName: ""
            podAnnotations: {}
            nodeSelector:
                kubernetes.io/os: linux
            tolerations: []
            # -- Labels to be added to patch job resources
            labels: {}
            securityContext:
                runAsNonRoot: true
                runAsUser: 2000
                fsGroup: 2000
        # Use certmanager to generate webhook certs
        certManager:
            enabled: false
            # self-signed root certificate
            rootCert:
                # default to be 5y
                duration: ""
            admissionCert:
                # default to be 1y
                duration: ""
                # issuerRef:
                #   name: "issuer"
                #   kind: "ClusterIssuer"
    metrics:
        port: 10254
        portName: metrics
        # if this port is changed, change healthz-port: in extraArgs: accordingly
        enabled: false
        service:
            annotations: {}
            # prometheus.io/scrape: "true"
            # prometheus.io/port: "10254"
            # -- Labels to be added to the metrics service resource
            labels: {}
            # clusterIP: ""

            # -- List of IP addresses at which the stats-exporter service is available
            ## Ref: https://kubernetes.io/docs/user-guide/services/#external-ips
            ##
            externalIPs: []
            # loadBalancerIP: ""
            loadBalancerSourceRanges: []
            servicePort: 10254
            type: ClusterIP
            # externalTrafficPolicy: ""
            # nodePort: ""
        serviceMonitor:
            enabled: false
            additionalLabels: {}
            ## The label to use to retrieve the job name from.
            ## jobLabel: "app.kubernetes.io/name"
            namespace: ""
            namespaceSelector: {}
            ## Default: scrape .Release.Namespace only
            ## To scrape all, use the following:
            ## namespaceSelector:
            ##   any: true
            scrapeInterval: 30s
            # honorLabels: true
            targetLabels: []
            relabelings: []
            metricRelabelings: []
        prometheusRule:
            enabled: false
            additionalLabels: {}
            # namespace: ""
            rules: []
            # # These are just examples rules, please adapt them to your needs
            # - alert: NGINXConfigFailed
            #   expr: count(nginx_ingress_controller_config_last_reload_successful == 0) > 0
            #   for: 1s
            #   labels:
            #     severity: critical
            #   annotations:
            #     description: bad ingress config - nginx config test failed
            #     summary: uninstall the latest ingress changes to allow config reloads to resume
            # - alert: NGINXCertificateExpiry
            #   expr: (avg(nginx_ingress_controller_ssl_expire_time_seconds) by (host) - time()) < 604800
            #   for: 1s
            #   labels:
            #     severity: critical
            #   annotations:
            #     description: ssl certificate(s) will expire in less then a week
            #     summary: renew expiring certificates to avoid downtime
            # - alert: NGINXTooMany500s
            #   expr: 100 * ( sum( nginx_ingress_controller_requests{status=~"5.+"} ) / sum(nginx_ingress_controller_requests) ) > 5
            #   for: 1m
            #   labels:
            #     severity: warning
            #   annotations:
            #     description: Too many 5XXs
            #     summary: More than 5% of all requests returned 5XX, this requires your attention
            # - alert: NGINXTooMany400s
            #   expr: 100 * ( sum( nginx_ingress_controller_requests{status=~"4.+"} ) / sum(nginx_ingress_controller_requests) ) > 5
            #   for: 1m
            #   labels:
            #     severity: warning
            #   annotations:
            #     description: Too many 4XXs
            #     summary: More than 5% of all requests returned 4XX, this requires your attention
    # -- Improve connection draining when ingress controller pod is deleted using a lifecycle hook:
    # With this new hook, we increased the default terminationGracePeriodSeconds from 30 seconds
    # to 300, allowing the draining of connections up to five minutes.
    # If the active connections end before that, the pod will terminate gracefully at that time.
    # To effectively take advantage of this feature, the Configmap feature
    # worker-shutdown-timeout new value is 240s instead of 10s.
    ##
    lifecycle:
        preStop:
            exec:
                command:
                    - /wait-shutdown
    priorityClassName: ""
# -- Rollback limit
##
revisionHistoryLimit: 10
## Default 404 backend
##
defaultBackend:
    ##
    enabled: false
    name: defaultbackend
    image:
        registry: registry.k8s.io
        image: defaultbackend-amd64
        ## for backwards compatibility consider setting the full image url via the repository value below
        ## use *either* current default registry/image or repository format or installing chart by providing the values.yaml will fail
        ## repository:
        tag: "1.5"
        pullPolicy: IfNotPresent
        # nobody user -> uid 65534
        runAsUser: 65534
        runAsNonRoot: true
        readOnlyRootFilesystem: true
        allowPrivilegeEscalation: false
    # -- Use an existing PSP instead of creating one
    existingPsp: ""
    extraArgs: {}
    serviceAccount:
        create: true
        name: ""
        automountServiceAccountToken: true
    # -- Additional environment variables to set for defaultBackend pods
    extraEnvs: []
    port: 8080
    ## Readiness and liveness probes for default backend
    ## Ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/
    ##
    livenessProbe:
        failureThreshold: 3
        initialDelaySeconds: 30
        periodSeconds: 10
        successThreshold: 1
        timeoutSeconds: 5
    readinessProbe:
        failureThreshold: 6
        initialDelaySeconds: 0
        periodSeconds: 5
        successThreshold: 1
        timeoutSeconds: 5
    # -- The update strategy to apply to the Deployment or DaemonSet
    ##
    updateStrategy: {}
    #  rollingUpdate:
    #    maxUnavailable: 1
    #  type: RollingUpdate

    # -- `minReadySeconds` to avoid killing pods before we are ready
    ##
    minReadySeconds: 0
    # -- Node tolerations for server scheduling to nodes with taints
    ## Ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/
    ##
    tolerations: []
    #  - key: "key"
    #    operator: "Equal|Exists"
    #    value: "value"
    #    effect: "NoSchedule|PreferNoSchedule|NoExecute(1.6 only)"

    affinity: {}
    # -- Security Context policies for controller pods
    # See https://kubernetes.io/docs/tasks/administer-cluster/sysctl-cluster/ for
    # notes on enabling and using sysctls
    ##
    podSecurityContext: {}
    # -- Security Context policies for controller main container.
    # See https://kubernetes.io/docs/tasks/administer-cluster/sysctl-cluster/ for
    # notes on enabling and using sysctls
    ##
    containerSecurityContext: {}
    # -- Labels to add to the pod container metadata
    podLabels: {}
    #  key: value

    # -- Node labels for default backend pod assignment
    ## Ref: https://kubernetes.io/docs/user-guide/node-selection/
    ##
    nodeSelector:
        kubernetes.io/os: linux
    # -- Annotations to be added to default backend pods
    ##
    podAnnotations: {}
    replicaCount: 1
    minAvailable: 1
    resources: {}
    # limits:
    #   cpu: 10m
    #   memory: 20Mi
    # requests:
    #   cpu: 10m
    #   memory: 20Mi

    extraVolumeMounts: []
    ## Additional volumeMounts to the default backend container.
    #  - name: copy-portal-skins
    #   mountPath: /var/lib/lemonldap-ng/portal/skins

    extraVolumes: []
    ## Additional volumes to the default backend pod.
    #  - name: copy-portal-skins
    #    emptyDir: {}

    autoscaling:
        annotations: {}
        enabled: false
        minReplicas: 1
        maxReplicas: 2
        targetCPUUtilizationPercentage: 50
        targetMemoryUtilizationPercentage: 50
    service:
        annotations: {}
        # clusterIP: ""

        # -- List of IP addresses at which the default backend service is available
        ## Ref: https://kubernetes.io/docs/user-guide/services/#external-ips
        ##
        externalIPs: []
        # loadBalancerIP: ""
        loadBalancerSourceRanges: []
        servicePort: 80
        type: ClusterIP
    priorityClassName: ""
    # -- Labels to be added to the default backend resources
    labels: {}
## Enable RBAC as per https://github.com/kubernetes/ingress-nginx/blob/main/docs/deploy/rbac.md and https://github.com/kubernetes/ingress-nginx/issues/266
rbac:
    create: true
    scope: false
## If true, create & use Pod Security Policy resources
## https://kubernetes.io/docs/concepts/policy/pod-security-policy/
podSecurityPolicy:
    enabled: false
serviceAccount:
    create: true
    name: ""
    automountServiceAccountToken: true
    # -- Annotations for the controller service account
    annotations: {}
# -- Optional array of imagePullSecrets containing private registry credentials
## Ref: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/
imagePullSecrets: []
# - name: secretName

# -- TCP service key-value pairs
## Ref: https://github.com/kubernetes/ingress-nginx/blob/main/docs/user-guide/exposing-tcp-udp-services.md
##
tcp: {}
#  8080: "default/example-tcp-svc:9000"

# -- UDP service key-value pairs
## Ref: https://github.com/kubernetes/ingress-nginx/blob/main/docs/user-guide/exposing-tcp-udp-services.md
##
udp: {}
#  53: "kube-system/kube-dns:53"

# -- Prefix for TCP and UDP ports names in ingress controller service
## Some cloud providers, like Yandex Cloud may have a requirements for a port name regex to support cloud load balancer integration
portNamePrefix: ""
# -- (string) A base64-encoded Diffie-Hellman parameter.
# This can be generated with: `openssl dhparam 4096 2> /dev/null | base64`
## Ref: https://github.com/kubernetes/ingress-nginx/tree/main/docs/examples/customization/ssl-dh-param
dhParam:

3、Helm和kubernetes版本对照

Helm 版本支持的 Kubernetes 版本
3.12.x1.27.x - 1.24.x
3.11.x1.26.x - 1.23.x
3.10.x1.25.x - 1.22.x
3.9.x1.24.x - 1.21.x
3.8.x1.23.x - 1.20.x
3.7.x1.22.x - 1.19.x
3.6.x1.21.x - 1.18.x
3.5.x1.20.x - 1.17.x
3.4.x1.19.x - 1.16.x
3.3.x1.18.x - 1.15.x
3.2.x1.18.x - 1.15.x
3.1.x1.17.x - 1.14.x
3.0.x1.16.x - 1.13.x
2.16.x1.16.x - 1.15.x
2.15.x1.15.x - 1.14.x
2.14.x1.14.x - 1.13.x
2.13.x1.13.x - 1.12.x
2.12.x1.12.x - 1.11.x
2.11.x1.11.x - 1.10.x
2.10.x1.10.x - 1.9.x
2.9.x1.10.x - 1.9.x
2.8.x1.9.x - 1.8.x
2.7.x1.8.x - 1.7.x
2.6.x1.7.x - 1.6.x
2.5.x1.6.x - 1.5.x
2.4.x1.6.x - 1.5.x
2.3.x1.5.x - 1.4.x
2.2.x1.5.x - 1.4.x
2.1.x1.5.x - 1.4.x
2.0.x1.4.x - 1.3.x

4、Ingress-nginx和k8s版本对照

SupportedIngress-NGINX versionk8s supported versionAlpine VersionNginx VersionHelm Chart Version
🔄v1.11.21.30, 1.29, 1.28, 1.27, 1.263.20.01.25.54.11.2
🔄v1.11.11.30, 1.29, 1.28, 1.27, 1.263.20.01.25.54.11.1
🔄v1.11.01.30, 1.29, 1.28, 1.27, 1.263.20.01.25.54.11.0
🔄v1.10.41.30, 1.29, 1.28, 1.27, 1.263.20.01.25.54.10.4
🔄v1.10.31.30, 1.29, 1.28, 1.27, 1.263.20.01.25.54.10.3
🔄v1.10.21.30, 1.29, 1.28, 1.27, 1.263.20.01.25.54.10.2
🔄v1.10.11.30, 1.29, 1.28, 1.27, 1.263.19.11.25.34.10.1
🔄v1.10.01.29, 1.28, 1.27, 1.263.19.11.25.34.10.0
v1.9.61.29, 1.28, 1.27, 1.26, 1.253.19.01.21.64.9.1
v1.9.51.28, 1.27, 1.26, 1.253.18.41.21.64.9.0
v1.9.41.28, 1.27, 1.26, 1.253.18.41.21.64.8.3
v1.9.31.28, 1.27, 1.26, 1.253.18.41.21.64.8.*
v1.9.11.28, 1.27, 1.26, 1.253.18.41.21.64.8.*
v1.9.01.28, 1.27, 1.26, 1.253.18.21.21.64.8.*
v1.8.41.27, 1.26, 1.25, 1.243.18.21.21.64.7.*
v1.7.11.27, 1.26, 1.25, 1.243.17.21.21.64.6.*
v1.6.41.26, 1.25, 1.24, 1.233.17.01.21.64.5.*
v1.5.11.25, 1.24, 1.233.16.21.21.64.4.*
v1.4.01.25, 1.24, 1.23, 1.223.16.21.19.10†4.3.0
v1.3.11.24, 1.23, 1.22, 1.21, 1.203.16.21.19.10†4.2.5

 

细数Kubernetes Service那些事－kubernetes 服务发布以及在eBay的实践
ebay的专栏
10-12 2万+
eBay自2014年末开始kubernetes的落地工作，并在2015年扩大研发投入。目前kubernetes已经部署在eBay的生产环境，并将作为下一代云计算平台。本文结合社区kubernetes的设计和实现，并结合openstack云基础架构，深入分析kubernetes服务部署的设计与实现。如果您在寻找服务发布的方案或者在寻找kubernetes服务相关的模块的原理或行为，阅读本文会让你有比较明确的方向。
Kubernetes的service的方案
完颜振江
05-06 630
根据您的应用场景和需求,可以选择合适的 Service 方案。在这个案例中,我们创建了一个 Nginx Deployment,然后使用 ClusterIP Service 为它提供了一个集群内部可访问的 IP 地址和端口。在这个案例中,我们创建了一个 Nginx Deployment,然后使用 NodePort Service 为它提供了一个集群外部可访问的端口。如果您使用其他云厂商的 Kubernetes 集群,LoadBalancer Service 的具体配置可能会有所不同,请参考相应的文档。
kubernetes中的微服务Service（ClusterIP、NodePort、LoadBalancer）
strongjcl的博客
09-10 1112
用控制器来完成集群的工作负载，那么应用如何暴漏出去？需要通过微服务暴漏出去后才能被访问Service是一组提供相同服务的Pod对外开放的接口。借助Service，应用可以实现服务发现和负载均衡。service默认只支持4层负载均衡能力，没有7层功能。（可以通过Ingress实现）
K8s服务service
踏上征程
12-20 1517
用于定义一组Pod的访问方式。在Kubernetes集群中，Pods可以动态地启动和停止，它们可能在不同的节点上以不同的IP地址运行。服务提供了一个固定的虚拟IP地址和与之关联的DNS名称，这使得无论Pod在集群中的位置如何，其他服务或外部用户都可以通过该虚拟IP地址或DNS名称访问这组Pod。通俗一点就是：实现对外服务的统一入口防止pod失联，定义一组pod的访问策略服务发现、负载均衡。
Kubernetes之服务发现Service
思月行云
02-15 1万+
原文：Kubernetes学习之路（十四）之服务发现Service 作者系列文章：https://www.cnblogs.com/linuxk/category/1248289.html 一、Service的概念 　　KubernetesPod是有生命周期的，它们可以被创建，也可以被销毁，然而一旦被销毁生命就永远结束。 通过ReplicationController能够动态地创建和销...
Kubernetes（k8s）服务介绍
shenyuanhaojie的博客
12-14 4089
Kubernetes，又称为 k8s（首字母为 k、首字母与尾字母之间有 8 个字符、尾字母为 s，所以简称 k8s），是一种可自动实施 Linux 容器操作的开源平台。它可以帮助用户省去应用容器化过程的许多手动部署和扩展操作。也就是说，您可以将运行 Linux 容器的多组主机聚集在一起，由 Kubernetes 帮助您轻松高效地管理这些集群。而且，这些集群可跨公共云、私有云或混合云部署主机。因此，对于要求快速扩展的云原生应用而言（例如借助 Apache Kafka 进行的实时数据流处理），Kubernet
kubernetes-server-linux-amd64.tar
01-17
Kubernetes的生态系统丰富，包括Ingress、Helm、Service Mesh等，使得Kubernetes不仅可以管理微服务应用，还能处理复杂的分布式系统需求。 总之，"kubernetes-server-linux-amd64.tar"是构建Kubernetes Linux集群的...
kubernetes-dashboard.yaml
08-11
serviceAccountName: kubernetes-dashboard # Comment the following tolerations if Dashboard must not be deployed on master tolerations: - key: node-role.kubernetes.io/master effect: NoSchedule ---...
kubernetes-client-linux-amd64.tar.gz
11-22
- 监控和调试：通过获取Pod、Service、Node等资源的状态，检查应用运行情况。可以使用`kubectl logs`查看Pod日志，`kubectl describe`获取详细信息，或`kubectl top`查看资源使用情况。 - 扩缩容：通过修改...
kubernetes-server-linux-amd64-v1.15.4.tar.gz
09-10
10. **服务发现和负载均衡**：Kubernetes Service机制提供服务发现和负载均衡，使得内部Pod之间可以相互发现并通信，同时对外暴露服务供外部访问。 综上所述，"kubernetes-server-linux-amd64-v1.15.4.tar.gz"文件...
kubernetes-server-linux-amd64.tar.gz
11-29
- **Service**：定义一组Pod的逻辑集合，并提供稳定的网络接入点。 - **Volume**：共享存储在Pod内的容器间提供持久化数据。 - **Deployments, StatefulSets, DaemonSets**：不同类型的控制器用于管理Pod的生命周期...
认识Kubernates(K8S)
xiangzhihong8的专栏
08-23 5121
在后端开发中，在介绍Jenkins的可伸缩部署方式上，主要有两种方式：一种是基于Docker（或者docker-swarm 集群）的部署方式，另外一种是基于kubernetes的部署方式(而kubernetes也是基于docker而设计的)。基本概念kubernetes是google开源的容器集群管理系统，提供应用部署、维护、扩展机制等功能，利用kubernetes能方便管理跨集群运行容器化的应用，
Kubernetes系列05：深入掌握Service
热门推荐
TURING.DT
04-21 1万+
Service是kubernetes最核心的概念，通过创建Service，可以为一组具有相同功能的容器应用提供一个统一的入口地址，并且将请求进行负载分发到后端的各个容器应用上。 本节对Service的使用进行说明，包括Service的负载均衡、外网访问、DNS服务的搭建、Ingress7层路由机制等 1.Service定义详解 yaml格式的Service定义文件的完整内容： apiV
Kubernetes之Service
山不转的博客
07-25 5299
概述 Service是Kubernetes中最核心的概念，正是因为对此概念的支持，Kubernetes在某种角度下可以被看成是一种微服务平台。Kubernetes中的pod并不稳定，比如由ReplicaSet、Deployment、DaemonSet等副本控制器创建的pod，其副本数量、pod名称、pod所运行的节点、pod的IP地址等，会随着集群规模、节点状态、用户缩放等因素动态变化。Serv...
每天5分钟玩转Kubernetes | 创建Service
COCO_gsta的博客
06-21 698
书籍来源：cloudman《每天5分钟玩转Kubernetes》 一边学习一边整理老师的课程内容及试验笔记，并与大家分享，侵权即删，谢谢支持！ Kubernetes Service从逻辑上代表了一组Pod，具体是哪些Pod则是由label来挑选的。Service有自己的IP，而且这个IP是不变的。客户端只需要访问Service的IP，Kubernetes则负责建立和维护Service与Pod的映射关系。无论后端Pod如何变化，对客户端不会有任何影响，因为Service没有变。 来看个例子，创建下面的这
Kubernetes创建Service访问Pod
cuibin1991的专栏
06-29 1180
Kubernetes创建Service访问Pod
Kubernetes 10 问，测测你对 k8s 的理解程度
最新发布
凌虚Blog
11-16 625
其次，Pod 是一组独立的 Linux 命名空间，容器本质上是一个进程，Pod 内容器共享 Network、IPC、UTS namespace，而每个容器的 PID、Mount namespace 则是独立的。的方式进行采集，但是存在日志丢失的可能，因为一旦 pod 被删除，对应的容器日志文件也会被删除，而日志代理可能还未完成全部日志的采集。所以，针对长连接，是有可能出现负载不均衡的情况。策略的时候，新的 pod 会被调度到已经有 pod 的节点上，而使用另外两种策略时，则调度到没有 pod 的节点。
k8clone二进制工具迁移k8s中的无状态应用
nangonghen的博客
11-12 565
k8clone备份恢复k8s集群中的无状态应用
kubernetes-dashboard 部署
06-08
Kubernetes Dashboard 是 Kubernetes 官方提供的一个 Web 界面，用于管理 Kubernetes 集群。以下是部署 Kubernetes Dashboard 的步骤: 1. 下载 Kubernetes Dashboard YAML 文件: ```bash curl -LO https://raw.githubusercontent.com/kubernetes/dashboard/v2.4.0/aio/deploy/recommended.yaml ``` 2. 修改 Kubernetes Dashboard Service 类型: 将 recommended.yaml 文件中的 Service 类型从 ClusterIP 修改为 NodePort，这样可以通过 Node 的 IP 地址加端口号访问 Kubernetes Dashboard。 ```yaml apiVersion: v1 kind: Service metadata: name: kubernetes-dashboard namespace: kubernetes-dashboard labels: k8s-app: kubernetes-dashboard spec: type: NodePort # 将类型修改为 NodePort ports: - port: 443 targetPort: 8443 selector: k8s-app: kubernetes-dashboard ``` 3. 部署 Kubernetes Dashboard: ```bash kubectl apply -f recommended.yaml ``` 4. 创建 Service Account: ```bash cat <<EOF | kubectl apply -f - apiVersion: v1 kind: ServiceAccount metadata: name: admin-user namespace: kubernetes-dashboard EOF ``` 5. 创建 Cluster Role Binding: ```bash cat <<EOF | kubectl apply -f - apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRoleBinding metadata: name: admin-user roleRef: apiGroup: rbac.authorization.k8s.io kind: ClusterRole name: cluster-admin subjects: - kind: ServiceAccount name: admin-user namespace: kubernetes-dashboard EOF ``` 6. 获取 Token: ```bash kubectl -n kubernetes-dashboard describe secret $(kubectl -n kubernetes-dashboard get secret | grep admin-user | awk '{print $1}') ``` 7. 访问 Kubernetes Dashboard: 使用浏览器访问 Node 的 IP 地址加端口号，输入 Token 登录即可。
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

熟透的蜗牛

永远满怀热爱，永远热泪盈眶

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付：¥1
获取中
扫码支付

您的余额不足，请更换扫码支付或充值

打赏作者

实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

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

余额充值