Shulou(Shulou.com)06/01 Report--

This article mainly introduces "the process of deploying 
 Nginx-ingress Controller in Kubernetes cluster". In the daily operation, I believe that many people have doubts about the process of deploying 
 Nginx-ingress Controller in Kubernetes cluster. The editor consulted all kinds of materials and sorted out simple and easy-to-use operation methods. I hope it will be helpful to answer the doubts about "the process of deploying 
 Nginx-ingress Controller in Kubernetes cluster". Next, please follow the editor to study!

Kubernetes provides two built-in cloud load balancing mechanisms for publishing public applications, one is Service resources working at the transport layer, which implements TCP load balancers, and the other is Ingress resources, which implements HTTP (S) load balancers.

Today we will focus on Ingress resources. HTTP (S) load balancer is one of the load balancing mechanisms in the application layer, which supports better scheduling decisions according to the environment. Compared with the transport layer scheduler, it provides functions such as customizable URL mapping and TLS, and supports a variety of health check mechanisms.

Ingress is one of the standard resource types of Kubernetes API. It is actually a set of rules that forward requests to specified Service resources based on DNS name or URL path. It is used to forward request traffic outside the cluster to the cluster to complete service publishing. However, the Ingress resource itself cannot perform "traffic traversal". It is only a collection of routing rules that need the assistance of other functions in order to really work, such as listening to a socket and then routing request traffic according to the matching mechanism of these rules. This component that listens for sockets and forwards traffic for Ingress resources is called Ingress Controller.

First, deploy Helm

Helm is a package management tool that packages Kubernetes resources (such as deployments, services or ingress) into a chart to save its chart to chart repository for storage and sharing. Helm supports version management of release application configuration, making release configurable, simplifying the version control, packaging, release, deletion, update and other operations of Kubernetes deployment applications.

Install Helm

1. Download Helm binaries on the official website. The latest version is 2.14.0.

Wget https://storage.googleapis.com/kubernetes-helm/helm-v2.14.0-linux-amd64.tar.gz

2. Extract the files and move the binaries in the directory to / usr/local/bin/

Tar-zxvf helm-v2.14.0-linux-amd64.tar.gz mv linux-amd64/helm / usr/local/bin/helm

3. Add permissions to Tiller. For more information, please see Role-based Access Control and create a new rbac-config.yaml, as shown below:

ApiVersion: v1kind: ServiceAccountmetadata: name: tiller namespace: kube-system---apiVersion: rbac.authorization.k8s.io/v1beta1kind: ClusterRoleBindingmetadata: name: tillerroleRef: apiGroup: rbac.authorization.k8s.io kind: ClusterRole name: cluster-adminsubjects:-kind: ServiceAccount name: tiller namespace: kube-system

Execute the create command:

Kubectl create-f rbac-config.yaml

4. Initialize Helm and install Tiller service

Helm init-upgrade-service-account tiller--tiller-image sapcc/tiller:v2.14.0

5. Check the helm version, and the following message appears to confirm the successful installation:

Client: & version.Version {SemVer: "v2.14.0", GitCommit: "8478fb4fc723885b155c924d1c8c410b7a9444e6", GitTreeState: "clean"} Server: & version.Version {SemVer: "v2.14.0", GitCommit: "8478fb4fc723885b155c924d1c8c410b7a9444e6", GitTreeState: "clean"}

6. Chart list

Helm repo update

7. Test whether chart is available

Helm search II. Install nginx-ingress using Helm

Install nginx-ingress

1. Execute the helm install command

Helm install stable/nginx-ingress-name my-nginx-set rbac.create=true

-- name: name the installed application

2. View the helm list

3. Check the service of ingress

Kuberctl get svc

3. Deploy nginx instance applications

Deploy deployment for nginx

1. Edit the nginx-app.yaml file

ApiVersion: apps/v1kind: Deploymentmetadata: name: nginx-deployment labels: app: nginxspec: replicas: 3 selector: matchLabels: app: nginx template: metadata: labels: app: nginxspec: containers:-name: nginx image: nginxdemos/hello:latest ports:-containerPort: 80

2. Execute the create creation command

Kubectl create-f nginx-app.yaml

3. Check the deployment of deployment

Kubectl get deployment nginx-deployment

Create a service for the deployment of nginx

1. Execute the expose command

Kubectl expose deployment nginx-deployment-target-port=80-port=80-protocol=TCP-name=jdc-test

2. Confirm that the service is created.

Kubectl get svc

Create an ingress for service

1. Edit the ingress-nginx.yaml file

ApiVersion: extensions/v1beta1kind: Ingressmetadata: name: jdc-ingress-controller-test annotations: metadata.annotations.kubernetes.io/ingress.class: "nginx" >

2. Execute the create creation command

Kubectl create-f ingress-nginx.yaml

3. Check the deployment of ingress

Kubectl get ingress

4. Add static resolution to the client. The public network IP is the service public network IP of nginx controller, and the domain name is host:test.nginx-ingress.jdc-test of ingress.

5. Enter url http://test.nginx-ingress.jdc-test/jdc-test into the browser to access the test

At this point, the study on "the process of deploying 
 Nginx-ingress Controller in a Kubernetes cluster" is over. I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.