Links

Container Linking

The Links section establishes a connection between containers located in different layers of the same environment. After linking, one container can use environment variables imported from the connected layer through a defined alias prefix.

In this article

How Container Linking Works

Container linking allows a layer to access variables and network references from another layer inside the same environment. The imported properties are identified by the alias assigned during link creation.

Source layerThe node group whose variables and network information will be shared.
Target layerThe container layer where the link is configured.
AliasA user-defined prefix used to identify imported variables and internal DNS records.
ResultThe target containers can access linked variables and address the connected nodes by alias.
1

Open the Links section

Open the required environment, select the destination container layer and access its settings. Switch to the Links section.

2

Click Add

Select the Add button to create a new connection.

3

Select the node layer

Use the Node drop-down list to select the required layer from the current environment.

4

Enter the alias

Enter a connection alias. The alias becomes the prefix for variables imported from the selected layer.

Add container linking settings
Select the linked node layer and assign a connection alias.
✓

Multiple links are supported

A single container layer can be linked to several different node groups when the application needs access to multiple services.

Alias and Internal DNS Behavior

When containers are linked, the platform creates corresponding internal DNS records using the assigned alias. This allows applications to reference linked containers by name instead of relying only on IP addresses or node identifiers.

To address a specific container in the linked layer, use the alias followed by the container number:

db_1 db_2 db_3

For example, when the alias is db, individual database containers can be reached as db_1, db_2 and so on through the platform’s internal network.

i

Layer-level alias

When the alias is used without a numeric suffix, such as db, the platform selects a container from the linked layer using a round-robin algorithm.

Save and Apply Linking Settings

1

Save the link

Click Save after entering the node and alias values.

2

Apply the layer changes

Click Apply in the layer settings window.

3

Confirm the topology update

When required, apply the changes again in the main topology wizard to complete the configuration.

!

Short service interruption

Linked nodes are restarted when the new settings are applied. This can cause a brief downtime for the involved containers.

Edit or Remove a Link

Select an existing link and use the Edit or Remove buttons in the upper toolbar of the container layer settings. Apply the changes after updating or deleting the record.

Edit or remove container linking settings
Manage existing links using the Edit and Remove actions.

Verify Imported Variables

After the link is applied, open the Variables section of the target container layer. The newly imported parameters should appear with the configured alias prefix.

✓

Verification checklist

  • Confirm that the alias is displayed in the linked variable names.
  • Verify that the required source layer was selected.
  • Check internal DNS resolution using the alias or alias with a numeric suffix.
  • Confirm that all Apply actions completed successfully.

Expected Result

The target container layer is connected to the selected node group. Linked environment variables become available with the assigned alias prefix, and the linked containers can be reached through internal DNS names based on that alias.

Important Notes

  • Container links can be created only between layers of the same environment.
  • Choose a short and meaningful alias that clearly identifies the linked service.
  • The alias is used both as a variable prefix and as an internal DNS name.
  • Remember to apply changes at both the layer and topology levels when required.
  • Applying link changes restarts the involved nodes and may cause brief downtime.
  • Review application dependencies before editing or removing an active production link.

Common Issues and Solutions

Variables are not visibleConfirm that the link was saved and all Apply actions were completed. Then reopen the Variables section.
Alias does not resolveVerify the alias spelling and confirm that the selected source layer contains active containers.
Specific node cannot be reachedUse the alias with the correct numeric suffix, such as db_1 or db_2.
Unexpected target is selectedUsing the alias without a suffix invokes round-robin selection across the linked layer.
Application briefly disconnectsThis can occur because linked nodes restart when configuration changes are applied.

Related Guides