I use Iosevka Nerd Font

@@ViktorGamov Thx for the video and answer, Vik!

here my usecase. I want to deploy my applications on multiple namespaces - dev - qa - PR-111 (for Pull request) my services could look like that chuck-service:8080 quote-service:8080 I'm on premise with nginx-ingress and with metallb as loadbalancer I'll expose nginx-controler as daemonset with a external IP : 10.1.10.123 for ingress /chuck -> chuck-service:8080 /quote -> quote-service:8080 I want to have those applications to be accessible for from outside on 10.1.10.123 (I can't expose new IP) the domain (inside-my-company.com) name it not register in external DNS ex : dev.inside-my-company.com/chuck dev.inside-my-company.com/quote qa.inside-my-company.com/chuck qa.inside-my-company.com/quote ....

You can use KIC cluster wide - in demo ingress controller and apps are deployed in separate namespaces. Need to check on DNS names tho. What DNS provider do you use "on-premise"? What k8s distribution do you use?

@@ViktorGamov We are using ubuntu 20.04. I filled a issue for my IT network team to create a DNS for our development team. So far, we don't have any. The hack that I found for now is to add a entry in /etc/hosts like 198.168.50.200 -> patate.org and test locally only. I though that maybe it was possible to setup a private DNS server in Kubernetes to avoid that, but I didn't find any and I'm not sure if it the right way. At the end, in production the clsuter will be in a private network without internet access, so I can't use any cloud-solution. I love working with those contrains.. you need to be creative :) I look also at core-dns plugin like : k8s_gateway, but I'm not sure if I'll need it at the end. Just fooling around at this point.