Multiple Public IP Addresses for a Single Container

Objective

This guide explains how to use Multiple Public IP Addresses for a Single Container 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.

Ruk-Com Cloud PaaS supports identification.Public IPMultiple (IPv4 and IPv6 resolutions) are assigned to a single container. As a result, a given IP can be one or both versions simultaneously.

For example, if multiple websites are hosted on a single node, multi IP helps manage them as separate, production-ready services. Because of the ability to use namescustom domainandSSL certificateof each item specifically This option is also useful for operating network devices (such as load balancers) that have multiple IP addresses for each network.

Note:Public IPv4 and IPv6 are paid options and are billed separately. (Price is the same or may differ) on an hourly basis. You can view the exact pricing for IPs per node/per environment by visiting the dashboard.Quotas & Pricing > Account Limits

You can assign multiple IP addresses through your Ruk-Com Cloud Dashboard using the appropriate spinner in the topology wizard when creating an environment or changing the topology.

Here you can choose the number of addresses you want from both Public IPv4 and Public IPv6 as appropriate. If you reach the limit, you can contact your hosting provider to increase the number of available addresses.

Managing multiple Public IP Addresses

On the main dashboard screen, each node within the environment topology list has details about all of its assigned IP addresses. They are listed in the following order:

• Private IP- Automatically attach internal IP address; It is always displayed first under the Node ID value.
• Public IPv4- A single external IP record or an extended list of all v4 addresses is second.
• Public IPv6- A single external IP record or an extended list of all v6 addresses is displayed last.

You can also copy to the clipboard and extract individual addresses using the appropriate buttons. Options next to the item name Attach/Detach IP(s) will help in adjusting the total number of assigned IPs for the respective type, such as: in each separate block.

Node SettingsIt will display the currently available number of attached IP addresses with the Apply button dimmed until you make some changes.

Note:Each Public IP added for the first time is considered a primary Public IP (always displayed first in the IP list) and can only be deleted if there are no more assigned addresses remaining on the node. This address is used for both inbound and outbound traffic, while the rest of the IP can only receive it.

Therefore, all IP addresses assigned to the container Will be displayed in the environment topology details at the terminal when connecting to the environment viaSSH Gate

All container external addresses are displayed in the column.WAN IP(in the same order as the dashboard, e.g. IPv4 > IPv6) whileLAN IPThere is a place inside

Note:In cases where the type of IP to reconnect is not clearly specified (e.g. internalCloud Scriptingsolution or add-on package settings at Marketplace), IPv4 will be used by default.

Set of thingsAPI Methodthat you can use to perform Public IP-related tasks. For detailed API reference information about Public IP, go to the following sections:

API Reference on multiple Public IPs

In this section you can find information aboutJelastic APIMethods provided for working with multiple Public IPs

1. To attach or remove Public IP via Jelastic API with the methodSetExtIpCount

https://[hoster-api-host]/1.0/environment/control/rest/setextipcount?envname=[string]&session=[string]&type=[string]&count=[int]&nodegroup=[string]&nodeid=[int]

This method applies to the following parameters:

• envname-Name of the source environment
• session- ID of current user session
• type- Public IP version (ipv4 or ipv6)
• count -Number of IP addresses to add or remove per container.
• nodegroup- The destination node group (such as bl, cp, sqldb, nosqldb, storage, vps, or build).
• nodeid- ID of destination node

To increase or decrease the number of dedicated IPs (IPv4 or IPv6) on the destination container, you must count and specify the number of addresses already defined.

2. To switch Public IP addresses between two nodes within the same or separate environment. You can use SwapExtIps method.

https://{hoster-api-host}/1.0/environment/control/rest/swapextips?envname=[string]&session=[string]&sourcenodeid=[int]&destnodeid=[int]&sourceip=[string]&destip=[string]

This method applies to the following parameters:

• envname-Name of the source environment
• session- ID of current user session
• sourcenodeid- ID of the source node to move Public IP address
• destnodeid- ID of the destination node to which the Public IP address will be moved (can belong to another environment)
• sourceip- Public IP address of the source node to be switched.
• destip- Public IP address of the destination node to be switched.

To switch all Public IP addresses between the source and destination nodes, omit the parameter.sourceipanddetip

Hm?Note:presentSwapExtIpsThe method can only be used with Public IPv4.