MIgrating from Helm nginx-ingress to standard installation

loadbalancer
#1

I’m fairly new to using Kubernetes and so far every helm chart I’ve used has caused me some sort of issue, and https://github.com/helm/charts/tree/master/stable/nginx-ingress has also caused me issue when trying to update it, so I would like to use the standard installation method instead.

I’m planing on doing the install as described here https://www.digitalocean.com/community/tutorials/how-to-set-up-an-nginx-ingress-with-cert-manager-on-digitalocean-kubernetes#step-2-—-setting-up-the-kubernetes-nginx-ingress-controller but was unsure what the effect would be if I did the install with the helm chart already installed.

Would it just create a new loadbalancer for me and then allow me to remove the existing helm chart, ideally I was to be able to make the change without having any downtime.

0 Likes

#2

What if you follow the instructions but make sure you use a different namespace than helm used?

Then, you can make the change (if it fails easily rollback to the helm nginx as it is already there) and when the new installation is stable, delete the NS created by helm. If there are something that is not bound to a NS, make sure you are not using it in the new installation (i.e. I would try to use different names for things, maybe, to be really sure) and delete it one by one after saving it to a file (kubectl get X -o yaml)

Also, maybe just run a kubectl get -o yaml for all the resources installed by helm (before starting this), so you can easily restore it also just in case.

Let us know how it goes! :slight_smile:

0 Likes

#3

I went about it slightly differently, when I added ingress-nginx I gave it a different class name i.e

--ingress-class=nginx-custom

This then allowed me to update my current ingress to the new class

0 Likes

#4

Oh, great. That was the trickiest part? :slight_smile:

0 Likes