Perform To upgrade a Release 22.6 or earlier NSP cluster to upgrade the NSP system.

Log in as the root or NSP admin user on the NSP deployer host.

Perform the following steps to preserve the existing deployment configuration.

1. Open the following file using a plain-text editor such as vi:

   /opt/nsp/NSP-CN-DEP-release-ID/NSP-CN-release-ID/config/nsp-config.yml

2. Edit the following line in the platform section, kubernetes subsection to read as shown below:

     deleteOnUndeploy:false

3. Save and close the file.

Enter the following:

# cd /opt/nsp/NSP-CN-DEP-release-ID/bin ↵

Enter the following to undeploy the NSP:

Note: If the NSP cluster VMs do not have the required SSH key, you must include the --ask-pass argument in the command, as shown in the following example, and are subsequently prompted for the root password of each cluster member:

nspdeployerctl --ask-pass uninstall --undeploy

# ./nspdeployerctl uninstall --undeploy ↵

Open the following file using a plain-text editor such as vi:

/opt/nsp/nsp-k8s-deployer-release-ID/config/k8s-deployer.yml

Set the following parameter to true, as shown below:

Note: Dual-stack NE management can function only when the network environment is appropriately configured, for example:

• Only valid, non-link-local static or DHCPv6-assigned addresses are used.

• A physical or virtual IPv6 subnet is configured for IPv6 communication with the NEs.

  enable_dual_stack_networks: true

Save and close the k8s-deployer.yml file.

Create a backup copy of the updated k8s-deployer.yml and transfer it to a secure location on a station that is not part of the NSP deployment.

Enter the following:

# cd /opt/nsp/nsp-k8s-deployer-release-ID/bin ↵

Enter the following:

Note: If the NSP cluster VMs do not have the required SSH key, you must include the --ask-pass argument in the command, as shown in the following example, and are subsequently prompted for the root password of each cluster member:

nspk8sctl --ask-pass install

# ./nspk8sctl install ↵

The configuration update is put into effect.

When the configuration update is complete, log in as the root or NSP admin user on the NSP cluster host.

Restart the coredns and dns-autoscaler pods.

1. Enter the following commands to determine how many replicas of each pod are running:

   # kubectl describe deployments.apps coredns -n kube-system | grep Replicas ↵

   # kubectl describe deployments.apps dns-autoscaler -n kube-system | grep Replicas ↵

2. You must set the number of coredns and dns-autoscaler pod replcas to 0, and then back to the replica count observed in substep 1.

   Enter the following sequence of commands, where initial_count is the number of replicas observed in substep 1:

   # kubectl scale deployment coredns -n kube-system --replicas=0 ↵

   # kubectl scale deployment coredns -n kube-system --replicas=initial_count ↵

   # kubectl scale deployment dns-autoscaler -n kube-system --replicas=0 ↵

   # kubectl scale deployment dns-autoscaler -n kube-system --replicas=initial_count ↵

Log in as the root or NSP admin user on the NSP deployer host.

Perform the following steps to preserve the existing deployment configuration.

1. Open the following file using a plain-text editor such as vi:

   /opt/nsp/NSP-CN-DEP-release-ID/NSP-CN-release-ID/config/nsp-config.yml

2. Edit the file to include the required IPv6 addresses; see IP version support for information about any requirements or restrictions.

3. Save and close the file.

Enter the following:

# cd /opt/nsp/NSP-CN-DEP-release-ID/bin ↵

Enter the following to redeploy the NSP:

Note: If the NSP cluster VMs do not have the required SSH key, you must include the --ask-pass argument in the command, as shown in the following example, and are subsequently prompted for the root password of each cluster member:

nspdeployerctl --ask-pass install --config --deploy

# ./nspdeployerctl install --config --deploy ↵

IPv6 communication is enabled.

Close the open console windows.

End of steps