How to install two ingress-nginx-controller & ingress-nginx-extra-controller
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- helm, kubernetes, nginx
- Domain
- devops, documentation
Research direction
Start by reproducing the two Helm commands from the issue and inspect the nginx-ingress chart's IngressClass ownership behavior. Document the supported way to install two controllers, including the required release or IngressClass settings, and verify that both installations succeed without the ownership error.
Written by the indexing model from the issue text.
Description
Hi Team, I am trying to install two ingress-nginx and getting the following error -
Command used -
helm install ingress-nginx nginx-stable/nginx-ingress -n ingress-nginx
Output - Successfully deployed
helm install ingress-nginx-extra-controller nginx-stable/nginx-ingress -n ingress-nginx
Error-
Error: INSTALLATION FAILED: 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; annotation validation error: key "meta.helm.sh/release-name" must equal "ingress-nginx-extra-controller": current value is "ingress-nginx"
I could not find any documentation on above in this repo - can you please suggest
- Dominant language
- Scala
- Stars
- 26
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from AbsaOSS/spline-getting-started
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
AbsaOSS/spline-getting-started#48 · 12 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
AbsaOSS/spline-getting-started#47 · 7 comments ·
-
Document a workaround for codeless init issue on DatabricksMay be free again @wajda claimed this 1257 days ago, and no pull request is open. Open
Difficulty 3/5 1-2 days Newbie friendliness 25/100
AbsaOSS/spline-getting-started#45 · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
AbsaOSS/spline-getting-started#42 · 3 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
All issues in AbsaOSS/spline-getting-started
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
cpp-best-practices/project_validator#245 ·
Maintainers usually reply within 1 day
-
python 🐍 Task 🔧
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
valkey-io/valkey-glide#7709 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
zio/zio-logging#1181 ·
Maintainers usually reply within 1 day
-
area:node bug priority:P2 status:backlog
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
KD5UJC-XYZ/scarab#933 ·
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
Sandesh13fr/TCalc#257 ·
Maintainers usually reply within 20 days