Uninstall High Availability cluster

Remove the
FactoryTalk® Optix™
High Availability application stack, K3s cluster, and local manager data.
IMPORTANT: Persistent Volume Claims (PVC) are deleted during uninstallation. All database data is lost, including uploaded projects. Back up any required data before proceeding. Rehost entitlements by using High Availability Manager or Entitlement Manager, depending on how they were installed.
Ensure that kubectl and Helm are installed on your Windows management workstation and that kubectl is configured to connect to the target cluster.
IMPORTANT:
Rockwell Automation
 is not responsible for any third-party software, including but not limited to its performance, security, updates, or compatibility with our products. Any use of third-party software is at your own risk, and we do not provide support, warranties, or guarantees for such software. Users should refer to the respective third-party providers for assistance and licensing terms.
Complete all parts of this task to fully remove the application stack, the K3s cluster, and local High Availability Manager data.
  1. To remove the application stack, run the following commands from the Windows management workstation.
    1. To remove the core High Availability application, run
      helm uninstall ftoptix -n ftoptix
      .
    2. To remove the database stack, run
      helm uninstall ftoptix-db -n ftoptix
      .
    3. To delete leftover MariaDB custom resources in the application namespace, run
      kubectl api-resources --api-group=k8s.mariadb.com --namespaced=true -o name | ForEach-Object { kubectl delete $_ -n ftoptix --all --ignore-not-found --timeout=60s }
      .
    4. To delete Persistent Volume Claims, including project and log volumes, run
      kubectl delete pvc -n ftoptix --all --ignore-not-found
      .
    5. To delete the application namespace, run
      kubectl delete namespace ftoptix
      .
    6. To uninstall the MariaDB operator, run
      helm uninstall mariadb-operator -n mariadb-system
      .
    7. To delete the MariaDB custom resource definitions, run
      kubectl get crd -o name | Select-String "k8s.mariadb.com" | ForEach-Object { kubectl delete $_ --ignore-not-found }
      .
    8. To delete the MariaDB operator namespace, run
      kubectl delete namespace mariadb-system
      .
    9. To prune container images related to
      FactoryTalk Optix
      , on each node run the following command.
      sudo ctr -n k8s.io images ls | grep -E "ra-swc|mariadb|proxysql|busybox" \
  | awk '{print $1}' | xargs -r sudo ctr -n k8s.io images rm
  2. To remove the K3s cluster, on each Ubuntu node run the matching uninstall script.
    1. On a server node, run
      sudo /usr/local/bin/k3s-uninstall.sh
      .
    2. On an agent node, run
      sudo /usr/local/bin/k3s-agent-uninstall.sh
      .
  3. To remove Keepalived, on each Ubuntu node run
    sudo apt-get purge -y keepalived
    .
  4. To remove local application data, close High Availability Manager, then delete
    %LOCALAPPDATA%\Rockwell Automation\FactoryTalk Optix High Availability Manager
    .
    IMPORTANT: Close High Availability Manager before you delete the folder.
The High Availability application stack, K3s cluster, and local manager data are removed.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal