Automatic Promote NodePort To the DNS Hostname

GitOps Argo CD
#1

Details: Hello Team,

I just want to ask you some technical advise… I work as DevOps Engineer and I am designing a service with load balancer to my company. studying your course and the labs i just found a very very cool and nice feature i would like to implement and i do not know how to do that. So I appreciate if you can give me a hint or just tell me the solution you adopt to made that feature.

In short, in one of your lab for example: lab-monitor-argocd-with-prometheus-grafana-alertmanager
when defining a K8s service with you NodePort, it would automatically added to the DNS name of the lab without configuring any thing else.
for example: define a new service Nodeport on port 31629, it would automatically be available on the url:

https://31629-port-d2d33d15e6304142.labs.kodekloud.com

I look forward to doing the same. so just defining a new service NodePort and that port is published on my dns:
for example new nodeport:87654 so it would be available on:

https:.//www.port-8764.myexample.com

so no configuration happened on Ingress & SSL certification?

#2

How the lab infrastructure works and what you do at your company would be very different things. I am not a full time employee and as such do not have access to the lab infrastructure, but it is built specifically to use randomly generated DNS names that point to nginx proxies which interface with the lab VMs.

In a corporate situation, you would not serve public sites through nodeports. You should absolutely use ingress, and if running in cloud, then have the appropriate cloud load balancer providers installed to automatically front your ingress. You would more than likely have to deploy the certificates to the cloud load balancer, but then that should be automated as part of the deployment process when a new public-facing application is deployed to the cluster.

#3

Thanks Alistair for the reply.
Can you recommend any documentation or tutorial to configure such nginx proxy on k8s?