Replacing the Packaged Ingress Controller from the IHC

This is a document discussing how to remove the previously packaged Ingress Controller resource from the old chart (IHC). In this demo, we will be deploying a replacement Ingress-Nginx controller.

Immuta Helm Changes

These changes are not all inclusive but involve the bare minimum that needs to be changed.

First, disable the ingress-nginx Ingress Controller in our Helm values.

nginxIngress:
  enabled: false

Then make sure that the Ingress resource has the correct label. In this demo, we're going to just do a 1:1 replacement with the new patch version of the ingress-nginx controller.

web:
  ingress:
    ingressClassName: nginx

Deploy Ingress-Nginx

You can either deploy this controller with Helm or with the one liner provided by Kubernetes.

Helm

This is desirable if the customer's networking needs are a little more granular, as this can be customized a little more easily.

helm upgrade --install ingress-nginx ingress-nginx \
  --repo https://kubernetes.github.io/ingress-nginx \
  --namespace ingress-nginx --create-namespace

Kubectl Apply the Whole Manifest at Once

kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.12.1/deploy/static/provider/cloud/deploy.yaml