Kubernetes<\/a> with the correct selector.<\/p>\nBy default, a Kubernetes Cluster comes with a Hello World deployment, service, and ingress (unless a custom deployment option was selected during installation).<\/p>\n
Exploring this default application can provide a practical understanding of Kubernetes services and networking concepts.<\/p>\n
Platform DNS Name Resolution inside PODs<\/h2>\n
DNS name resolution within Kubernetes pods is managed by CoreDNS, which is automatically configured in the \/etc\/resolv.conf<\/strong> file of each pod. CoreDNS uses platform nameservers to facilitate direct communication between the Kubernetes Cluster and other containers within the platform.<\/p>\nFor example, suppose you have a database deployed in the platform and want to connect to it from a Kubernetes pod. You can use the “${nodeId}-${envName}.${platformDomain}<\/strong>” hostname along with the default port for the database (e.g., 3306 for MySQL, 5432 for PostgreSQL<\/strong>).<\/p>\nHowever, to connect to a database deployed outside the platform from within a Kubernetes pod, you would need to create an endpoint or ingress resource to facilitate external access.<\/p>\n
This involves configuring networking policies and possibly exposing the service using NodePort, LoadBalancer, or Ingress resources, depending on the use case and infrastructure setup.<\/p>\n