Microk8s With Ingress Example

Posted on 2019-04-02 by Kendrick Tan

Prelude

This post is merely a reference guide for me to setup Kubernetes with Ingress.

What’s The Difference Between Ingress And A Loadbalancer?

LoadBalancer lives on L4 on the OSI model, Ingress services lives on L7 of the OSI model.

Use ingress for a single app with a single domain to be mapped to an IP address, use ingress to map multiple subdomains to multiple apps within your cluster.

For nicer infographs, refer to Mathhew Palmer’s blogpost.

Steps

1. Install MicroK8s

Microk8s quickstart link

sudo snap install microk8s --classic
microk8s.start

2. Install Ingress Dependent Resources

microk8s.kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/mandatory.yaml

3. Enable Ingress Addon

microk8s.enable ingress

4. Run a local Docker Registry

You can skip this step if you wanna host your image on a public/private repository.

docker run -p 5000:5000 registry

5. Clone Example Repository And Build Docker Image

git clone https://github.com/kendricktan/microk8s-ingress-example
cd microk8s-ingress-example

docker build . -t my-microk8s-app
docker tag my-microk8s-app localhost:5000/my-microk8s-app
docker push localhost:5000/my-microk8s-app

6. Run Applications And Ingress

microk8s.kubectl apply -f bar-deployment.yml
microk8s.kubectl apply -f foo-deployment.yml
microk8s.kubectl apply -f ingress.yml

7. Expose Deployments to Ingress

If you skip this step you’ll get a 503 service unavailable

microk8s.kubectl expose deployment foo-app --type=LoadBalancer --port=8080
microk8s.kubectl expose deployment bar-app --type=LoadBalancer --port=8080

8. Testing Endpoint Out

curl -kL http://127.0.0.1/bar
curl -kL http://127.0.0.1/foo