Configuring ingress using minikube

[glinker]

Steps to reproduce the issue:

1. minikube config set ingress true

This used to work but now i get an error saying no such option "ingress"

Full output of failed command:

Full output of minikube start command used, if not already included:

Optional: Full output of minikube logs command:

[medyagh]

@glinker do u mind clraifying what you are trying to do ? I dont think u can enable ingress by config. I think you are probabbly loooking for minikube addon enable ingress ?

[glinker]

@medyagh thanks for the response. It appears that the mechanism to enable ingress changed with later versions of minikube. Before, it was "minikube set config ingress true" but has now changed to "minikube addon enable ingress". I was able to get this set up and working

[medyagh]

ponse. It appears that the mechanism to enable ingress changed with later versions of minikube. Before, it was "minikube set config ingress true" but has now changed to "minikube addon enable ingress". I was able to get this set up and working

glad to see the issue was solved, do you mind sharing what driver did you use on what operating system and what example did you run?

our documentation on ingress has been a bit out dated, it would be nice to see end users using it with eaxmples in a tutorial on our website. https://minikube.sigs.k8s.io/docs/

[skrtks]

"minikube addon enable ingress" does not seem to be working in v1.10.1. The command does not give any errors, but when checking if the controller is running (kubectl get pods -n kube-system), the status is ImagePullBackOff.

[kopotp]

"minikube addon enable ingress" does not seem to be working in v1.10.1. The command does not give any errors, but when checking if the controller is running (kubectl get pods -n kube-system), the status is ImagePullBackOff.

Seems like quay.io is down

Failed to pull image "quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.32.0": rpc error: code = Unknown desc = Error response from daemon: Get https://quay.io/v2/kubernetes-ingress-controller/nginx-ingress-controller/manifests/0.32.0: received unexpected HTTP status: 500 Internal Server Error

https://status.quay.io/

Please don't use any RedHat dependencies in future releases 😕

[kevinresol]

And this is down again, right now, lasted for more than 3 hours.

[jgoeres]

I noticed the same issue and came here looking for a way to tell minikube to pull the ingress controller image from some other location, alas this seems not possible. Or is it?
How about allowing to set an alternative image (plus pull secret!) for the ingress addon (or for ANY add on that pulls an image)? That would allow people that use minikube in their internal process to host such images on internal registries, to not have a dependency on external systems.
I will open a dedicated issue for this requirement.

[sharifelgamal]

I'm going to close this in favor of #8298, I think properly supporting alternate repositories for addons is a good idea.