The Links section is intended to establish connection between the containers placed at different layers of a single environment.
After such connection is set, a container will be able to work with environment variables of the linked image (herewith, the imported properties can be recognized by a specified prefix). Below, we’ll provide a step-by-step example of containers linking.
Tip: Upon linking containers, the platform also adds the corresponding DNS record (with the name identical to the used alias) to the platform DB. In such a way, you can refer to a particular container from inside of these two environment layers not just over its IP address or NodeID, but also specifying the assigned alias with counter, i.e. {aliasname}N. For example, after linking with DB alias, you can ping specific containers at the appropriate layer as “db_1”, “db_2”, etc while working with platform internal network via SSH Gateway. Herewith, if using common layer alias (i.e. without counter, “db” in our case), the system will use Round-Robin algorithm to choose any container within the defined node group.
Note:
- all the stated connections will take effect only after selecting the Apply buttons for this frame and, if needed, for the whole topology wizard
- be aware that the linked nodes will be restarted for the new settings to be applied (causing a short downtime of the involved containers)
When updates are applied, you can check the results by switching to the Variables section (where the newly imported parameters will be listed).