---
title: Update the Load Balancer Address
slug: install-10x/update-the-load-balancer-address
docTags: 
createdAt: 2025-07-16T13:29:40.591Z
---

Use these instructions to change your existing load balancer address following a prior installation.

Execute the main installer script again on one of your existing nodes with the new load balancer address specified. The main installer script will generate a new task script that can be executed on the remaining cluster nodes.

To update the TPI load balancer address:

1. Connect to all the nodes that are part of your Turbine cluster.
   **Note:** The update process involves running commands on all cluster nodes. Swimlane recommends having a terminal window/tab open for each SSH session.
   Open a terminal for each SSH session.``
   `  # Terminal 1`
   `    ssh <node1>`
   `  # Terminal 2`
   `    ssh <node2>`
   ``
   `  # Terminal 3`
   `    ssh <node3>`
   `   ``` `
2. On node 1, run the main installer script with the new load balancer address.
   `` curl https://kurl.sh/swimlane-platform/install | sudo bash -s ha load-balancer-address=<New LB Address>:6443` ``
   **Note:** If you are on an airgapped deployment, replace the kurl.sh URL with`cat install.sh `and add the word `airgap `before `ha `as in this example: `cat install.sh | sudo bash -s airgap ha load-balancer-address=<New LB` Address>:6443
3. The installer script you run on node 1 executes a curl command. Use this new command on the other remote nodes (node 2, node 3).
   Here is the output from the node 1 installer script:
   `The load balancer address has changed. Run the following on all remote nodes to use the new address:`
   `curl -sSL https://kurl.sh/swimlane-platform/tasks.sh | sudo bash -s set-kubeconfig-server <New LB Address>:6443`
   `Continue? (Y/n)`
   **Important!** Copy the curl command for the next step, but **do not** enter Y yet.
4. Run the tasks.sh script on node 2 and node 3.
   ` # node 2`
   ` [<user>@<node2> ~]$ curl -sSL https://kurl.sh/swimlane-platform/tasks.sh | sudo bash -s set-kubeconfig-server <New LB Address>:6443`
   ` Cluster "default-cluster" set.`
   ` Cluster "kubernetes" set.`
   ` # node 3`
   ` [<user>@<node3> ~]$ curl -sSL https://kurl.sh/swimlane-platform/tasks.sh | sudo bash -s set-kubeconfig-server <New LB Address>:6443`
   ` Cluster "default-cluster" set.`
   ` Cluster "kubernetes" set.`
5. Enter Y to resume the installer load balancer change process on node 1.
   ` # node 1`
   `The load balancer address has changed. Run the following on all remote nodes to use the new address:`
   `    curl -sSL https://kurl.sh/swimlane-platform/tasks.sh | sudo bash -s set-kubeconfig-server <New LB Address>:6443`
   `Continue? (Y/n) Y`
   `Removing old load balancer address <Old LB Address> from API server certificate on node <node1>`
   `pod/regen-cert-<node1> created`
   `          Installation`
   `          Complete ✔`
   `Kotsadm: <New LB Address>:8800`
   `You can log in with your existing password. If you need to reset it, run kubectl kots reset-password default`
   `To access the cluster with kubectl, reload your shell:`
   `    bash -l`
6. Once the installer has finished running, the load balancer address will be updated. Next you update the Turbine application to use the new load balancer address.
   `https://<New LB Address>:8800 >> Login to KOTS UI >> Config >> Update "Swimlane Hostname" with the new LB address >> Save Config >> Deploy`
   **Note:** If you restore a snapshot from a backup that was generated when the cluster was configured with the old address you will need to update the config again with the new address and deploy (repeat step 6).