# Networking Applications Networking applications define logical networking functions within a cluster network. They represent the networking purpose that a workload or service uses inside the regional network. Each networking application maps networking behavior to a specific cluster network. This mapping allows the platform to apply the correct network domain, routing, and connectivity rules. Networking applications appear in the **Region Networking > Networking Applications** page. The page lists all applications that exist in the region. Each entry contains the following information: * **Name** The unique descriptive name of the networking application. * **Type**: The application networking type, that represents the networking behavior of the service. Examples include standard network connectivity and virtual IP services. * **Switch Domain** The switch domain that routes the networking application traffic. * **Cluster Network** The cluster network where the networking application operates. Networking applications are created and managed by administrators to organize cluster networking and to ensure consistent connectivity policies across workloads. ## Networking Applications Management Administrators manage networking applications from the **Networking Applications** page in the Region Networking section. The page displays the list of existing applications and provides the main lifecycle operations, such as creating, viewing and deleting a networking application. ### Viewing Networking Applications The networking applications table provides a view of all configured applications. To view networking applications: 1. Open **Region Networking**. 2. Select **Networking Applications**. The table displays the following properties for each entry: * **Name** The unique descriptive name of the networking application. * **Type**: The application networking type, that represents the networking behavior of the service. Examples include standard network connectivity and virtual IP services. * **Switch Domain** The switch domain associated with the networking application. * **Cluster Network** The cluster network where the networking application operates. This view helps administrators verify the networking layout of the cluster. #### Viewing a Network Application’s details The **Application Details** page provides detailed information about a specific networking application. Administrators use this page to review application configuration and to view the firewall rules associated with the application. Applications represent networking functions that operate on a cluster network. Each application is linked to a cluster network and inherits the network behavior defined for that network. To view details of a networking application: 1. Open **Region Networking**. 2. Select **Networking Applications**. The page displays the list of existing applications. 3. Select a networking application to view its details. The networking application details screen opens with the following sections: * **Info** section: Displays basic configuration properties for the application: * **Enabled/Disabled** status, indicating the networking application’s availability. * **ID** The unique identifier assigned to the application. This value is generated by the system when the application is created. Administrators typically use this identifier when referencing the application in system operations or when reviewing configuration data. * **Name** The descriptive name of the application. The name identifies the networking function associated with the application. Administrators should use clear and descriptive names to simplify network management. * **Type** The networking type assigned to the application. The type indicates the role that the application performs within the cluster networking model. Example types : * **network** * **virtual_ip** * **Cluster Network ID** The identifier of the cluster network associated with the application. Each application operates on a specific cluster network. The cluster network defines the traffic role used by the application. * **Enabled** Indicates whether the application is currently enabled. An enabled application allows network behavior and firewall rules associated with the application to be applied. Network applications of type **virtual_ip** expose a service through a virtual IP endpoint. In addition to the standard application properties, the details page includes several fields specific to virtual IP behavior. These fields describe how the virtual IP is used, the service it represents, and whether the address can be shared across multiple services: * **Direction** Indicates the traffic direction associated with the virtual IP application. The direction defines whether the virtual IP accepts traffic from external systems or handles internal traffic within the cluster network. This property helps determine how the virtual IP participates in the networking flow and which services or clients are expected to connect to it. * **Service** Identifies the service associated with the virtual IP. The service value represents the networking function or platform service that is exposed through the virtual IP. Clients use the virtual IP address to reach the service instead of connecting directly to individual nodes. Associating a service with a virtual IP provides a stable endpoint that remains consistent even if the underlying service location changes. * **Shared** Indicates whether the virtual IP address can be shared by multiple services or applications. When enabled, the same virtual IP can be used by more than one service. This allows the platform to expose multiple services through a single logical address when required by the network design. When **Shared** is disabled, the virtual IP is dedicated to a single service. * **IP Address** Displays the virtual IP address assigned to the application. This address represents the network endpoint used by clients to access the associated service. The virtual IP remains stable even if the service moves between nodes or instances within the cluster. Administrators use this address when configuring clients, external systems, or network integrations that must reach the service. * **Firewall Rules** section: Lists the network protocols and ports allowed for the application. Firewall rules control which types of traffic can access services that use the application. Each rule defines the protocol and port used for communication. Displayed fields: * **Protocol** The network protocol allowed by the firewall rule. Examples: * **tcp** * **icmp** * **Port** The network port allowed for the protocol. These ports represent services that are reachable through the application. Example interpretation: * **22 (TCP)** commonly represents SSH access. * **80 (TCP)** commonly represents HTTP traffic. * **443 (TCP)** commonly represents HTTPS traffic. Firewall rules allow administrators to restrict network access so that only required protocols and ports are permitted. ### Creating a Networking Application Creating an application defines a new networking function for the cluster. This allows services or workloads to use the appropriate network connectivity. To create a networking application: 1. Open **Region Networking**. 2. Select **Networking Applications**. The page displays the list of existing applications. 3. Select **+Create**. The **Create Application** dialog opens. 4. In the **Create Application** dialog, enter the required values. * **Name** – Enter a uniquie descriptive name for the application. * **Cluster Network** – Select the cluster network that will host the application. * **Application Type** – Select the networking type. Currently, MSP admins can only select **Network** for networking applications. 5. Select **Finish** to save the configuration. The application appears in the networking applications list after creation. ### Deleting a Networking Application Deleting an application removes it from the regional networking configuration. This operation should be performed only when the application is no longer required. To delete a networking application: 1. Open **Region Networking**. 2. Select **Networking Applications**. The page displays the list of existing applications. 3. Select the networking application to delete. 4. Select **Delete** from the top toolbar. The **Delete Application** dialog opens, displaying the name of the networking application selected to be deleted. 5. To confirm deletion, select **Ok**. The application is removed from the configuration and is no longer displayed in the networking applications list. ## Recommended Best Practices ### Use consistent naming conventions Use clear and descriptive names for applications. This makes it easier to identify the networking purpose and reduces the risk of configuration errors. ### Align applications with cluster network design Create applications that reflect the network roles within the cluster. Examples include access, control, or data networks. A structured approach simplifies troubleshooting and improves operational clarity. ### Avoid unnecessary applications Create applications only when they represent a real networking function. Excess applications increase administrative complexity and can make troubleshooting more difficult. ### Validate cluster network selection Confirm that the correct cluster network is selected when creating an application. Selecting the wrong network can prevent services from communicating correctly. ### Review switch domain mappings Verify that the application is associated with the correct switch domain. Incorrect domain mapping can affect connectivity and routing. ## Troubleshooting ### Application does not appear in the list Possible causes include: * The application was not successfully created. * The page has not refreshed after the operation. Possible actions: * Refresh the page. * Reopen the **Networking Applications** view. ### Incorrect network connectivity Services may fail to communicate if the application is associated with the wrong cluster network. Possible actions: * Verify the **Cluster Network** value in the application entry. * Confirm the network role assigned to the application. ### Unexpected switch domain assignment If an application appears under the wrong switch domain, traffic may not follow the intended network path. Possible actions: * Review the application configuration. * Confirm that the correct cluster network was selected during creation. ### Application cannot be deleted Deletion may fail if the application is still in use by active services. Possible actions: * Identify services that depend on the application. * Remove or reconfigure those services before deleting the application.