Editing configurations of a remote Kubernetes cluster

You can edit the kubeconfig file, address, namespace, name, or ingress details of the remote Kubernetes cluster that you added to a team space on IBM® DevOps Test Hub (Test Hub).

You must have completed the following tasks:

Read and completed the tasks mentioned in Considerations for using a remote Kubernetes cluster, if you want to use a remote Kubernetes cluster as a location to run the test.
Registered a remote Kubernetes cluster with your team space on Test Hub. See Registering a remote Kubernetes cluster.
Ensured that you are assigned a role as a Member or Project Creator in the team space. See Managing members and their roles in a team space.
Ensured that you are assigned a role as a Project Owner or Tester in the project. See Managing access to the server projects.

Log in to Test Hub.

The Projects page of the initial team space is displayed.
Click Infrastructure > Agents and Intercepts in the navigation pane of the team space.

The Agents and Intercepts page is displayed.

You can view the agents, intercepts, Dockers, or clusters that are registered with the team space on Test Hub.
You can view the clusters that you own in any of the following ways:
- Search for the cluster by entering the name of the cluster in the Search field.
  Note: You can enter either the full name or any text that is in the name. The search is enabled for case-sensitive text that you can enter.
- Sort the Type column to sort the items, and then identify the cluster by the name or owner.
- Sort the Agents column to sort the items, and then identify the cluster by the name or owner.
You can view the following details about the clusters that are in the team space:
- The projects in the team space to which the cluster is added, are displayed in the Projects column.
- The status of the cluster is displayed in the Status column.
  Note: You can add clusters that are in the Ready state to your project, and then use them as locations to run tests.
Identify the cluster that you want to modify the configurations, and then click the Edit icon .

Note: The icon is displayed in the Actions column in the row of the cluster only if you own the cluster.

The Update cluster dialog is displayed.
Perform the following steps to change the kubeconfig file:
1. Click Browse, and locate the kubeconfig file of the Kubernetes cluster that you want to use.
2. Select the kubeconfig file, and then click Open.
  
  The name of the kubeconfig file that you selected is displayed along with the address of the Kubernetes cluster that is specified in the file.
3. Click Next.
Perform the following steps to change the namespace or name of the cluster:
1. Edit or change the namespace of the cluster that you want to use, in the Namespace field.
2. Edit or change the name of the cluster in the Name field.
3. Click Next.
Perform the following steps to change the ingress details of the cluster:
1. Select the ingress type of the cluster from the Ingress type list, if you want to use a different cluster.
2. Enter or change the ingress host pattern of the cluster in the Ingress host pattern field, if you did not provide it when setting up the remote cluster or change it to match the cluster you want to use.
3. Enter the secret if you did not provide it when setting up the remote cluster.
  The secret is used to authenticate the remote cluster to use the licenses from the Team space License Server so that the inbound traffic is allowed into the ingress domain.
  Note: The secret to use must be available with your Test Hub server administrator.
4. Click Next.
Optionally, perform the following steps to edit or change the code snippets for nodeSelectors and tolerations, if applicable for the remote cluster:
1. Enter the code snippet for nodeSelectors in a yaml format in the Node selectors field.
2. Enter the code snippet for tolerations in a yaml format in the Tolerations field.
Click Update.

The remote cluster is displayed with the updated configurations.
Note: The projects that are associated with the cluster are displayed in the Projects column and you need not add the cluster to the same project again.

You have updated an existing remote cluster with the changed configurations.

You can select the updated cluster as an alternate location to run the test assets or resources that are in your project while you configure a run from the Execution page.