The documentation is under development and may contain incomplete information.

To delete a cluster, several steps need to be followed:

  1. Remove all additional nodes from the cluster:

    1.1. Remove the node from the Kubernetes cluster:

    d8 k drain <node> --ignore-daemonsets --delete-local-data
    d8 k delete node <node>
    

    1.2. Run the cleanup script on the node:

    bash /var/lib/bashible/cleanup_static_node.sh --yes-i-am-sane-and-i-understand-what-i-am-doing
    
  2. Check the update channel set in the cluster. To do this, run the command:

    d8 k get mc deckhouse -o jsonpath='{.spec.settings.releaseChannel}'
    
  3. Run the Deckhouse installer:

    docker run --pull=always -it [<MOUNT_OPTIONS>] \
       registry.deckhouse.ru/deckhouse/<DECKHOUSE_REVISION>/install:<RELEASE_CHANNEL> bash
    

    where:

    • <MOUNT_OPTIONS> — the options for mounting files into the installer container, such as SSH access keys;
    • <DECKHOUSE_REVISION>edition of the platform (e.g., ee — for Enterprise Edition, ce — for Community Edition, etc.)
    • <RELEASE_CHANNEL>update channel of the platform in kebab-case. It should match the one set in config.yaml during the installation of DVP:
      • alpha — for the Alpha update channel;
      • beta — for the Beta update channel;
      • early-access — for the Early Access update channel;
      • stable — for the Stable update channel;
      • rock-solid — for the Rock Solid update channel.

    Example of running the installer container for the CE edition:

    docker run -it --pull=always \
       -v "$PWD/dhctl-tmp:/tmp/dhctl" \
       -v "$HOME/.ssh/:/tmp/.ssh/" registry.deckhouse.ru/deckhouse/ce/install:stable bash
    
  4. Execute the cluster removal command:

    dhctl destroy --ssh-user=<USER> \
       --ssh-agent-private-keys=/tmp/.ssh/id_rsa \
       --yes-i-am-sane-and-i-understand-what-i-am-doing \
       --ssh-host=<MASTER_IP>
    

    where:

    • <USER> — the user of the remote machine from which the installation was performed;
    • <MASTER_IP> — IP address of the master node in the cluster.

    The installer will connect to the master node and remove all Deckhouse components and the Kubernetes cluster from it.