Difference between revisions of "Minikube addons enable ingress"
Jump to navigation
Jump to search
| (4 intermediate revisions by the same user not shown) | |||
| Line 3: | Line 3: | ||
🌟 The '[[ingress]]' addon is enabled | 🌟 The '[[ingress]]' addon is enabled | ||
| + | == Examples == | ||
minikube addons enable ingress | minikube addons enable ingress | ||
💡 ingress is an addon maintained by Kubernetes. For any concerns contact minikube on GitHub. | 💡 ingress is an addon maintained by Kubernetes. For any concerns contact minikube on GitHub. | ||
| Line 24: | Line 25: | ||
https://github.com/kubernetes/minikube/issues/7332 | https://github.com/kubernetes/minikube/issues/7332 | ||
| − | + | == Errors == | |
minikube addons enable ingress | minikube addons enable ingress | ||
🔎 Verifying ingress addon... | 🔎 Verifying ingress addon... | ||
| − | 💣 enable failed: run callbacks: running callbacks: [sudo KUBECONFIG=/var/lib/minikube/kubeconfig /var/lib/minikube/binaries/v1.18.0/kubectl apply -f /etc/kubernetes/addons/ingress-configmap.yaml -f /etc/kubernetes/addons/ingress-rbac.yaml -f /etc/kubernetes/addons/ingress-dp.yaml: Process exited with status 1 | + | 💣 enable failed: run callbacks: [[running callbacks]]: [sudo KUBECONFIG=/var/lib/minikube/kubeconfig /var/lib/minikube/binaries/v1.18.0/kubectl apply -f /etc/kubernetes/addons/ingress-configmap.yaml -f /etc/kubernetes/addons/ingress-rbac.yaml -f /etc/kubernetes/addons/ingress-dp.yaml: Process exited with status 1 |
| − | |||
== Related terms == | == Related terms == | ||
| Line 35: | Line 35: | ||
* <code>[[minikube stop]]</code> | * <code>[[minikube stop]]</code> | ||
* [[Ingress controller]] | * [[Ingress controller]] | ||
| + | * <code>[[kubectl get svc]]</code> | ||
| + | * <code>[[minikube addons enable ingress-dns]]</code> | ||
== See also == | == See also == | ||
Latest revision as of 11:18, 6 February 2024
Examples[edit]
minikube addons enable ingress 💡 ingress is an addon maintained by Kubernetes. For any concerns contact minikube on GitHub. You can view the list of minikube maintainers at: https://github.com/kubernetes/minikube/blob/master/OWNERS 💡 After the addon is enabled, please run "minikube tunnel" and your ingress resources would be available at "127.0.0.1" ▪ Using image registry.k8s.io/ingress-nginx/kube-webhook-certgen:v20231011-8b53cabe0 ▪ Using image registry.k8s.io/ingress-nginx/kube-webhook-certgen:v20231011-8b53cabe0 ▪ Using image registry.k8s.io/ingress-nginx/controller:v1.9.4 🔎 Verifying ingress addon... 🌟 The 'ingress' addon is enabled
minikube addons enable ingress 💡 Due to networking limitations of driver docker on darwin, ingress addon is not supported. Alternatively to use this addon you can use a vm-based driver: 'minikube start --vm=true' To track the update on this work in progress feature please check: https://github.com/kubernetes/minikube/issues/7332
Errors[edit]
minikube addons enable ingress 🔎 Verifying ingress addon... 💣 enable failed: run callbacks: running callbacks: [sudo KUBECONFIG=/var/lib/minikube/kubeconfig /var/lib/minikube/binaries/v1.18.0/kubectl apply -f /etc/kubernetes/addons/ingress-configmap.yaml -f /etc/kubernetes/addons/ingress-rbac.yaml -f /etc/kubernetes/addons/ingress-dp.yaml: Process exited with status 1
Related terms[edit]
See also[edit]
minikube addons enable [ csi-hostpath-driver | dashboard | metrics-server ]- minikube: [
status|start|stop|version|addons|addons list|addons enable|dashboard|logs|tunnel|ssh|config|image | delete],config setminikube start --vm=true, kicbase,~/.minikube/, minikube --help, Minikube changelog
Advertising:
