Skip to content

Latest commit

 

History

History
105 lines (72 loc) · 3.45 KB

README.md

File metadata and controls

105 lines (72 loc) · 3.45 KB
Raw

Lab 3 - Ingressing and Egressing with Linkerd

Linkerd's control plane does not include ingress or egress gateways. Linkerd allows you choice of your preferred ingress (and egress) controller.

How to use Ingress with Linkerd

In case you're anticipating infusing Linkerd into your ingress controller's pods there is some setup required. Linkerd discovers services dependent on the :authority or Host header. This permits Linkerd to comprehend what service a request is bound for without being subject to DNS or IPs.

In this workshop, you will use the NGINX Ingress Controller with Linkerd.

3.1 Installing NGINX Ingress Controller

Using Meshery, select the Linkerd from the Management menu, and:

  1. Enter ingress-nginx into the namespace field.
  2. Click the (+) icon on the Apply Service Mesh Configuration card and select NGINX Ingress Controller to install the latest version of KIC.

3.2 Setting up ingress controller with the sample application deployed

Using Meshery, click the (▶️) icon on the Apply Custom Configuration card and apply the following manifest to your cluster:

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: web-ingress
  namespace: emojivoto
  annotations:
    kubernetes.io/ingress.class: "nginx"
    nginx.ingress.kubernetes.io/configuration-snippet: |
      proxy_set_header l5d-dst-override $service_name.$namespace.svc.cluster.local:$service_port;
      grpc_set_header l5d-dst-override $service_name.$namespace.svc.cluster.local:$service_port;

spec:
  rules:
    - host: example.com
      http:
        paths:
          - backend:
              serviceName: web-svc
              servicePort: 80

Nginx ingress will include the l5d-dst-override header to tell Linkerd where to direct the request. You'll need to include both the Kubernetes administration FQDN (web-svc.emojivoto.svc.cluster.local) and the destination servicePort.

To test this, you need to get the external IP of your controller.

Docker Desktop You may use http://localhost or http://kubernetes.docker.internal or your host's IP address.

Minikube

Run this command to expose your Kubernetes's cluster services to your localhost network.

minikube tunnel

You may use http://localhost or You may use http://localhost: provided by the output of minikube tunnel.

Hosted Kubernetes

Retrieve the external IP address by running:

kubectl get svc --all-namespaces \
  -l app=nginx-ingress,component=controller \
  -o=custom-columns=EXTERNAL-IP:.status.loadBalancer.ingress[0].ip

You can now curl to your service without using port-forward, like this:

curl -H "Host: example.com" http://{external-ip}

Continue to Lab 4: Exploring Linkerd Dashboard


Alternative, manual installation steps are provided for reference below. No need to execute these if you have performed the steps above.

Appendix - Alternative Manual Install

3.1 Installing NGINX Ingress Controller

  • Install ingress controller using Docker Desktop
kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v0.40.2/deploy/static/provider/cloud/deploy.yaml
  • Install the ingress controller using Minikube
minikube addons enable ingress