commit
fb9a16dbc9
|
|
@ -19,7 +19,7 @@ only real way to do this is to add an entry for every service in your `/etc/host
|
|||
reasons. If you have a lot of services running that each have their own dns entry then you have to set those up
|
||||
manually. Even if you automate it you then need to rely on the host operating system storing configurations instead of
|
||||
storing them in your cluster. To make it worse it has to be constantly maintained and updated as services are added,
|
||||
remove, and renamed. I call it the `/ets/hosts` pollution problem.
|
||||
remove, and renamed. I call it the `/etc/hosts` pollution problem.
|
||||
|
||||
### Solution
|
||||
What if you could just access your local services magically without having to edit your `/etc/hosts` file? Well now you
|
||||
|
|
@ -185,4 +185,4 @@ sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.mDNSResponder.pli
|
|||
| Image | Source | Owner |
|
||||
| :--- | :--- | :--- |
|
||||
| [ingress-nginx](https://quay.io/repository/kubernetes-ingress-controller/nginx-ingress-controller) | [ingress-nginx](https://github.com/kubernetes/ingress-nginx) | Kubernetes ingress-nginx
|
||||
| [minikube-ingress-dns](https://hub.docker.com/r/cryptexlabs/minikube-ingress-dns) | [minikube-ingress-dns](https://gitlab.com/cryptexlabs/public/development/minikube-ingress-dns) | Cryptex Labs
|
||||
| [minikube-ingress-dns](https://hub.docker.com/r/cryptexlabs/minikube-ingress-dns) | [minikube-ingress-dns](https://gitlab.com/cryptexlabs/public/development/minikube-ingress-dns) | Cryptex Labs
|
||||
|
|
|
|||
Loading…
Reference in New Issue