kubernetes ingress controller

The content of this section: Service Discovery and load balancing Ingress Combat First, service discovery and load balancingIn the previous installation deployment Kubernetes cluster, it was simple to demonstrate that pod and Service,kubernetes implemented service discovery and load balancing for containers within the

Kubernetes about the service exposure is mainly through the Nodeport way, through the binding minion host of a port, then the pod request forwarding and load balancing, but this way the defect is The service may have many, if each is bound to a node host port, the host needs to open the perimeter of a heap of ports to make services calls, management confusion Cannot apply firewall rules required by many companies The ideal way is thr

-app:traefik-ingress-lb Template:metadata:labels:k8s-app: TRAEFIK-INGRESS-LB annotations:prometheus.io/scrape: "True" Prometheus.io/port: "8580" spec:t Erminationgraceperiodseconds:60 hostnetwork:true restartpolicy:always Volumes:-name:traefik-conf IG Configmap:name:traefik-conf-name:traefik-key secret:secretname:dz11-ingress -secret-name:traefik-log Hos

ObjectiveIngress is a way to expose the internal service of a k8s cluster, and user-edited profiles define a ingress resource to enable external network access to the intranet service.Ingress Controller is to manage all Ingress objects, ingress controller inside is actually

official website of the instructions and did not succeed, consulted a large number of documents, and combined with their own practice finally ruled out the problem, installation success. Share my installation process below.1. Preparing the installation EnvironmentK8s 1.22. Enable Kubernetes API Authenticationhttp://kubernetes.io/docs/admin/authentication/This step can not be ignored, otherwise nginx ingress