Skip to content

Latest commit

 

History

History
135 lines (93 loc) · 4.47 KB

ingress-controller.md

File metadata and controls

135 lines (93 loc) · 4.47 KB
Raw

Ingress Controllers

This lab will show how to use Kubernetes ingress controllers to route traffic to our Heroes web application.

Add Ingress Controller to an Azure Kubernetes Service Cluster

There are a number of ingress controllers available today. Here is a quick, but not exhaustive list for reference purposes:

  • Nginx
  • Traefik
  • LinkerD
  • Custom Ingress Controllers

For the purposes of this lab we will be using Nginx as our ingress controller.

Configure Helm

We will use Helm to install Nginx. We had configured Helm in prior labs.

  1. Open the Azure Cloud Shell

  2. Validate your Helm install by running the below commands.

    helm version

# You should see something like the following as output:
Client: &version.Version{SemVer:"v2.11.0", GitCommit:"9ad53aac42165a5fadc6c87be0dea6b115f93090", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.11.0", GitCommit:"9ad53aac42165a5fadc6c87be0dea6b115f93090", GitTreeState:"clean"}

    Note: If helm was not configured, you must run helm init

Install Nginx using Helm

The Nginx Ingress Controller is an Ingress controller that uses a ConfigMap to store the nginx configuration and provides layer 7 capabilities for applications deployed on Kubernetes.

  1. Install Nginx using Helm CLI

    # The following command will install the Nginx ingress controller into the K8s cluster.

helm install --name ingress stable/nginx-ingress --namespace kube-system

  2. Validate that Nginx was installed

    kubectl get pods -n kube-system | grep nginx

# You should see something like the following as output:
ingress-nginx-ingress-controller-86bf69bcfc-jqvsg        1/1       Running   0          1d
ingress-nginx-ingress-default-backend-86d6db4c47-td2k8   1/1       Running   0          1d
    • The nginx-ingress helm chart deploys a nginx ingress controller and also a backend for the ingress controller. The backend is used when a route is not found and will display a 404 error. You can browse to the public IP to preview this.
    kubectl get svc -n kube-system | grep nginx

# You should see something like the following as output:
ingress-nginx-ingress-controller       LoadBalancer  10.0.231.143  52.173.190.190  80:30910/TCP,443:30480/TCP  1d
ingress-nginx-ingress-default-backend  ClusterIP     10.0.175.123  <none>          80/TCP                      1d
    • The nginx controller will use a LoadBalancer type service where the backend is of type ClusterIP

Deploy the heroes web\api app with Ingress

We will now deploy the application with a configured Ingress resource.

  1. Clear the previous web/api deployment of your cluster:

    cd ~/blackbelt-aks-hackfest/labs/helper-files

kubectl delete -f heroes-web-api.yaml

  2. In the helper-files directory and open and edit the heroes-web-api-ingress.yaml file. Change all image field in the YAML files to match your docker registry url.

    • You will need to replace the <login server> with the ACR login server created in earlier labs.

      Note: You will update the image name TWICE updating the web and api container images.

      • Example:

        spec:
containers:
- image: mycontainerregistry.azurecr.io/azureworkshop/rating-web:v1
    name:  heroes-web-cntnr

  3. Deploy heroes-web-api-ingress.yaml

    kubectl apply -f heroes-web-api-ingress.yaml

    Note: Below is an example of a Ingress object

    ---
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
name: heroes-web-ingress
annotations:
    kubernetes.io/ingress.class: nginx
    # Add to generate certificates for this ingress
    kubernetes.io/tls-acme: 'false'
spec:
rules:
    - host:
    http:
        paths:
        - backend:
            serviceName: web
            servicePort: 8080
            path: /

  4. Browse to the web app via the Ingress

# get ingress external IP
kubectl get svc -n kube-system | grep ingress

ingress-nginx-ingress-controller        LoadBalancer   10.0.155.205   52.186.29.245   80:32045/TCP,443:31794/TCP   2h
ingress-nginx-ingress-default-backend   ClusterIP      10.0.171.59    <none>          80/TCP                       2h

Note: you will likely see a privacy SSL warning