HAProxy Setup

Nirmata uses HAProxy, an open source load balancer proxy, for TCP and HTTP applications.

Installing HAProxy

  1. Click Environments in the left navigation.

  2. Click the target environment to install HAProxy.

  3. Click the + to Run an Application.

    The Run Application setup overlay appears.

  4. Enter a unique Run name for the application that includes haproxy.

    Example: my-env-haproxy

  5. Use the default selection Catalog for Upstream Type.

  6. Select HAProxy from the Catalog Application drop-down menu.

  7. Click the Run Application button to save your changes and run HAProxy on the environment. Click Cancel to return to the Environment Details page.

Notes:

Checking HAProxy Deployment Status

  1. Click the arrow next to the Search box.

  2. Note the newly deploying instance of haproxy-ingress.

On completion, the Application Details page shows the State as Running if the HAProxy installation was completed successfully.

If the HAProxy resources are running, the HAProxy installation is complete.

Installing Multiple Instances of HAProxy

To install mulitple instances of HAProxy, you must do the following for each new instance:

  1. Create a unique Cluster Role Binding.
  2. Create a unique Ingress Class.

Creating a Unique Cluster Role Binding

The new instance of HAProxy requires a unique Cluster Role Binding with a unique name. To create a unique Cluster Role Binding:

  1. Click on the HAProxy instance installed in your environment.

  2. The Application Details page appears. Click on Storage & Configuration.

  3. Scroll down to the Other Resources section. Note the resources identified as ClusterRoleBinding in the Kind column. Use an existing cluster role binding as a template to create a unique instance.

  4. Click on an existing cluster role binding.

    The Cluster Role Binding Detail page is displayed.

  5. Click the Download button to download a copy of the cluster role binding YAML file.

  6. Open the downloaded YAML file and give the cluster role binding a unique name by modifying name under metadata.

  7. Rename the new cluster role binding YAML file using the same unique name specified when editing the file in the previous step.

    Example: hap-appscorpent1-crb3.yaml

  8. Click the browser Back button to return to the Application Details page.

  9. Click the gear icon on the right side of the Application Details page and select Import to Application from the menu.

    The Import YAML to Application HAProxy overlay appears.

  10. Click inside the gray box to open a file selector, or drag your file inside the gray box to upload the new cluster role binding.

  11. Click the Import button or click cancel to return to the previous page.

    Note the presence of the new cluster role binding in the Other Resources section of Application Details.

  12. Delete the existing cluster role binding used when creating the new cluster role binding.

  13. A confirmation overlay appears. Click Delete to continue or click Cancel to return to the previous page.

Next step: create a unique ingress class for HAProxy.

Creating a Unique Ingress Class

The new instance of HAProxy requires an ingress class with a unique name. To create a unique ingress class:

  1. Click on the HAProxy instance installed in your environment.

  2. The Application Details page appears. Click the gray arrow button under Workloads to expand the service details.

  3. Click the pod instance for HAProxy.

  4. The Pod Details page appears. Click haproxy-ingress under Containers.

  5. The Container Detail page appears. Scroll down to the Container Spec section and click View Container in Pod Template on the right.

  6. The Container Template page appears. Scroll to the top and click the edit icon in the Container Template section on the right.

  7. The Edit Container overlay appears.

  8. In the Args section, click inside the field containing the --ingress-class argument.

  9. Modify the value of the key value-pair to be a unique instance for the ingress class.

    Example: --ingress-class=ingress10

  10. Click Save to continue. Click Cancel to return to the previous page.

Note: upon saving there will be a short delay during the pod redeployment using the new ingress class.

Check HAProxy deployment status after adding or modifying a cluster role binding or ingress class.