Exposing Services

Objective

This guide explains how to use Exposing Services 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.

while the components of your application can communicate with each other.service nameusing the internal network External connections require additional configuration.

The most basic way to create an external connection to a service is through exposure.NodePortDirect As the name suggests, this service type opens specific ports on the node. Any traffic sent to this port will be forwarded to your service. By default the nodePort for your service is randomly selected from the range 30000-32767.

Note:
This approach has several disadvantages that should be considered when configuring a Kubernetes Cluster (one service per port, limited port range, etc.). Because of this, the NodePort service type can be used for demos or other temporary applications. However, production solutions often require more permanent external access (e.g.ingresses)

1. Here is an example of configuring a NodePort service type:

kind: Service
apiVersion: v1
metadata:
  name: nginx1
  namespace: test
  labels:
    run: nginx
spec:
  type: NodePort
  selector:
    run: nginx
  ports:
    - port: 80
      targetPort: 80

Note: Please note thatRuk-Com Cloud does not support service types.LocaBalancerAt this time, if using the chartYAMLorHelmWith such service objects you need to convert them to NodePort or create them.ingressesfor external access

2. If necessary, you can select a specific nodePort for your service. For example, the following code can be used to configure redirection from port 30984:

  ports:
    - port: 80
      targetPort: 80
      nodePort: 30984

Note:
The manually provisioned nodePort value should be within the allowed range. (30000-32767) and unique (to prevent collisions with other services)

3. In the case of connectingpublic IPWith Kubernetes worker nodes, no additional action is required.

Otherwise, the received port should be opened from the Ruk-Com side. Go to Kubernetes environment Settings > Endpoints and click Add. In the opened frame, specify the following information:

• Node– Select worker node from the list.
• Name– Name the desired endpoint.
• Private Port– Specify nodePort from the previous step.
• Protocol- Select TCP option

ClickAddTo confirm, it may take a few minutes for Ruk-Com to display the port and redirect requests to the NodePort service.