Internal Networking
This guide has been reviewed and reformatted for Ruk-Com Cloud PaaS. Screens may vary slightly by platform version.
Click or tap a screenshot to view it at its original size.
Objective
This guide explains how to use Internal Networking on Ruk-Com Cloud PaaS, with ordered procedures and practical verification points.
Before you begin
- Sign in with an account permitted to manage the relevant environment.
- Confirm the target environment, region and resources before saving changes.
- Create a backup or rollback plan before changing a production system.
Internal network configurationKubernetes ClusterIt is a completely automated process which usesK8s ServicesThe CNI plugin creates and configures an overlay network that allows all pods to be provisioned with an IP address.
Kubernetes also supports direct access to services by name. Therefore, there is no need for any service discovery mechanism. For example, your application server can connect to the database using a DNS name, which is resolved to the required internal IP. Here you createserviceobject with only valid options.
Kubernetes ClusterComes with deployment, service andingressof Hello World by default. (unless the custom deployment option is selected duringinstallation) You can check out this starter application to better understand the concept of Kubernetes service.
Ruk-Com DNS Name Resolution within PODs
Ruk-Com Kubernetes cluster uses CoreDNS to resolve Kubernetes internal DNS names are automatically assigned in the file. /etc/resolv.conf of each pod. CoreDNS also uses Ruk-Com nameservers, which allow for direct access between the K8s Cluster and other containers within the platform.
For example, if you have an environment with a database in Ruk-Com Cloud and want to connect to it from a Kubernetes pod, you must use the hostname “${nodeId}-${envName}.${platformDomain}” and the default port for the database (3306 for MySQL, 5432 for Postgres, etc.).
However, you must createendpointTo connect to that database from outside Ruk-Com