Skip to main content
NetApp Backup and Recovery

Manage Kubernetes clusters in NetApp Backup and Recovery

Contributors netapp-mwallis
PDFs

Discover and manage Kubernetes clusters to protect their hosted resources.

Note To discover Kubernetes clusters, refer to Discover Kubernetes workloads.

Edit Kubernetes cluster information

You can edit a cluster if you need to change its name.

Required NetApp Console role

Backup and Recovery super admin or Backup and Recovery backup admin. Learn about NetApp Backup and Recovery access roles. Learn about NetApp Console access roles for all services.

Steps

  1. In NetApp Backup and Recovery, select Inventory > Clusters.

  2. In the list of clusters, select a cluster you want to edit and select the associated Actions menu.

  3. Select Edit cluster.

  4. Make any required changes to the cluster name. The cluster name must match the name that you used with the Helm command during the discovery process.

  5. Select Done.

Remove a Kubernetes cluster

To stop protecting a Kubernetes cluster, disable protection and delete associated applications, then remove the cluster from NetApp Backup and Recovery. NetApp Backup and Recovery does not delete the cluster or its resources; it only removes the cluster from the NetApp Console inventory.

Required NetApp Console role

Backup and Recovery super admin. Learn about NetApp Backup and Recovery access roles. Learn about NetApp Console access roles for all services.

Steps

  1. In NetApp Backup and Recovery, select Inventory > Clusters.

  2. In the list of clusters, select the cluster you want to remove and select the associated Actions menu.

  3. Select Remove cluster.

  4. Review the information in the confirmation dialog box, and select Remove.

Upgrade Trident Protect

For Kubernetes clusters running Trident Protect 26.05 or later, you can upgrade Trident Protect directly from NetApp Backup and Recovery. The upgrade option only appears if a newer version is available.

Required NetApp Console role

Backup and Recovery super admin. Learn about NetApp Backup and Recovery access roles. Learn about NetApp Console access roles for all services.

Steps

  1. In NetApp Backup and Recovery, select Inventory > Clusters.

  2. Select a Kubernetes cluster to upgrade, and select the Actions icon Actions option > Upgrade cluster.

  3. In the upgrade dialog, do the following:

    1. From the list, select the version to upgrade to.

    2. Select Upgrade.

Reconnect a Kubernetes cluster to a Console agent

If your Console agent's IP address changes (for example, after a restart), your Kubernetes cluster loses its connection to the agent and you need to reconnect.

Required NetApp Console role

Backup and Recovery super admin. Learn about NetApp Backup and Recovery access roles. Learn about NetApp Console access roles for all services.

Steps

  1. In NetApp Backup and Recovery, select Inventory > Clusters.

  2. Select a disconnected Kubernetes cluster, and select the Action icon Actions option > Modify cluster > Reconnect cluster.

  3. In the Reconnect cluster dialog, copy the command-line instructions and run them on your cluster.

    After the command completes, your cluster should reconnect automatically.

  4. Select Close.

Migrate a Kubernetes cluster to a new Console agent

If your Console agent is deleted or becomes unavailable, migrate any clusters that use it to a new agent to avoid interrupting application protection.

Required NetApp Console role

Backup and Recovery super admin. Learn about NetApp Backup and Recovery access roles. Learn about NetApp Console access roles for all services.

Before you begin
Steps

  1. In NetApp Backup and Recovery, select Inventory > Clusters.

  2. Select a disconnected Kubernetes cluster, and select the Action icon Actions option > Modify cluster > Manage agent.

  3. From the list, select a new Console agent.

  4. Review the agent information to ensure the new Console agent can access the systems, backup targets, and secondary targets used by the protected applications on this cluster.

  5. Copy the command-line instructions for each section and run the commands on the cluster.

    This recreates Kubernetes secrets, redirects Trident Protect to the new Console agent, and reloads settings. After you finish running the commands, the cluster is using the new Console agent.

  6. Select Close.