DevFW-CICD/ingress-nginx-helm
14
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update index.md (#7766)

Browse source 
Proposal to add information to Helm Installation

I can into an issue recently which cost me the better part of an afternoon and evening. The only information about some changes, I was not aware of, was in this blog post about improvements in 1.18.

The information about the errors I was receiving lead me to dead ends prior to finding that blog post. `IngressClass` and `ingressClassName` are thrown around a lot and it can be confusing but it helped me to eventually find a solution.

I kept getting `Error: rendered manifests contain a resource that already exists. Unable to continue with install: IngressClass "nginx" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata ...` and could not figure out how to fix it.

I believe adding the proposed changes, or a version of them, would help eliminate that frustration I experienced for other users that may run into these issues.
This commit is contained in:
mitchldtn 2021-10-10 13:36:38 -05:00 committed by GitHub
parent 9e3c528640
commit 4ad67e125e
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/deploy/index.md
View file

@ -235,6 +235,8 @@ helm repo update
helm install ingress-nginx ingress-nginx/ingress-nginx helm install ingress-nginx ingress-nginx/ingress-nginx
``` ```
[For multiple NGINX Ingress controllers](https://kubernetes.github.io/ingress-nginx/#how-to-easily-install-multiple-instances-of-the-ingress-nginx-controller-in-the-same-cluster)
## Detect installed version: ## Detect installed version:
```console ```console