Getting Local DNS configed with Minikube | 220826



Working on minikube

been running into trouble getting keycloak up and running using the bitnami chart for many reason and some I really don’t get. Also they seem to be updating it just as fast I am fucking with it. so i’d come back and they would have added or updated so I’m never positive if I had something wrong or something else. So I took a break from elimination testing values of the chart to deal with something that has been bothering me which would be the ingress DNS and minikube. So I looking into making it more normal than it just kinda working by either or accessing the cluster ip or using the minikube ingress which neither seem to work for me constantly

So working on local DNS is always a fun thing cause one wrong file edit and you can no longer look anything else on that machine to undo you mistake (I only did it once this time.).

Since the last year when I was messing around with the kube either to me not knowing or existing a minikube addon called “ingress-dns” has appeared in my search engine results which looks to ease my whao’s.

Link to minikube ingess-dns install guide

my current dev-machine is running Manjaro/Arch so the “Linux OS with Network Manager” was the appropriate solution for installation for me(I tried the other ones, I lost DNS so not those)

sc of relevant installation information

all of these commands worked besides the

echo "server=/test/$(minikube ip)" >/etc/NetworkManager/dnsmasq.d/minikube.conf

which lead to a

permission denied: /etc/NetworkManager/dnsmasq.d/minikube.conf

but this just due to it trying to pipe and make a new file in a protected location and adding sudo would only apply to the echo and not the create file. So I just echoed out the first part and sudo vim’ed a new file and pasta’ed it into and followed the rest of the instruction. I am sure there is a way to sudo the pipe as well, but I don’t know how to.

So what this allows is for minikube to host on “*.test " as one would expect.

example ingress-dns working

more example of ingress-dns working

Not like a world changer, but I think it’s rather cool. It does allow for a more accurate hosted kube ‘production’ environment cause you can create ingress classes/ingress/endpoints/certs that at least look more like the paid hosting than dumpy local environment.

Note: I do not like .test but it seems the best cause .local cannot be used as its reversed for other items in the DNS realm; which would have been my preferred base host name.