Links
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 Links 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.
part ofLinksUsed to create connections between containers in different layers within the same environment.
After setting up the above connection Containers can work with the environment variables of linked images (here imports are recognized by the prefix). In the next section, we'll show you a step-by-step example of linking a container:
1. Click on the buttonAddand fill in information in the fields that appear.
- Node- Click the drop-down list to select the desired layer in the current environment.
- Alias- Type the connection alias (LB in our case) and then use it as a prefix for the variable imported into the current container from the previously selected layer.

Tips:Once a container is linked, the platform also adds the associated DNS records. (same name as alias) to Ruk-Com Cloud DB. This way you can use containers within these two environment layers. Not only the IP address or NodeID, but also the given aliases are counted, such as {alias_name} _N for example. After binding to the DB alias, you can ping specific containers in the appropriate layers "db_1", "db_2", etc. while working with the network within the platform via Ruk-Com Cloud SSH if using common layer aliases. (In the absence of a "db" counter), a Round-Robin algorithm is used to select containers within a given node group.
2. After that press Save to confirm link settings. You can link different node groups to the layers you want.
- Note:
- All listed connections are effective when the button is pressed.Applyfor this frame and if necessary for all topology wizard builds.
- Things to know:
- The associated node will berestartto adapt to the new settings. (causing related containers to stop briefly)
3. You canEditorRemoveunnecessary links at any time by clicking the button you want to execute on the Docker layer settings frame.

When the update occurs You can check the results by switching to the section.Variables (This will list the newly imported parameters)