Ingress-nginx: Page "Bare-metal considerations"/Section "A pure software solution: MetalLB" doesn't mention how to install ingress-nginx service

Created on 12 Oct 2019  路  16Comments  路  Source: kubernetes/ingress-nginx

Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see https://kubernetes.io/docs/tasks/debug-application-cluster/troubleshooting/.): No

What keywords did you search in NGINX Ingress controller issues before filing this one? (If you have found any duplicates, you should instead reply there.): MetalLB


Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT

NGINX Ingress controller version: Latest

Kubernetes version (use kubectl version): Latest

Environment:

  • Cloud provider or hardware configuration:
  • OS (e.g. from /etc/os-release):
  • Kernel (e.g. uname -a):
  • Install tools:
  • Others:

What happened:

Page "Bare-metal considerations"/Section "A pure software solution: MetalLB" doesn't mention how to install ingress-nginx service.

What you expected to happen:
It should mention that to use MetalLB, the ingress-nginx service must be created using the command:

kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingressnginx/master/deploy/static/provider/cloud-generic.yaml

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know:

kindocumentation lifecyclrotten

Most helpful comment

I did the nginx line from my comment, and then installed MetalLB. I kept away from the NodePort stuff.

All 16 comments

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

I ran into this exact thing yesterday. +1 for updating the docs with this info.

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/reopen

@dinhanhhuy: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

This should be fixed if possible please. Just wasted a lot of time on this, installing the bare-metal version.

@scottrobertson Did you get this to work? I am about to attempt this and don't want to spend a ton of time for sure.

@mrlesmithjr I ended up not using MetalLB sorry.

@scottrobertson No worries. I think I got it working. Much appreciated!

@mrlesmithjr can u please share your solution?

@bh90210 since my last comment, I did end up using MetalLB actually. I just used the cloud generic version:

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

I'm a bit confused though. Should I install the ingress first like it's described here https://kubernetes.github.io/ingress-nginx/deploy/#bare-metal
and the also run kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v0.35.0/deploy/static/provider/cloud/deploy.yaml

should I just run the above command?

I did the nginx line from my comment, and then installed MetalLB. I kept away from the NodePort stuff.

Was this page helpful?
0 / 5 - 0 ratings