Newer documentation is now live.You are currently reading an older version.

Install the support dump controller

TechPreview

Starting from MOSK 26.2, you can use supportdump-controller to create a diagnostic data snapshot with a SupportDump custom resource instead of gathering logs and objects through the bootstrap CLI, SSH keys, and node access as in Collect cluster logs. You download one structured archive and attach it to a support case, which reduces follow-up requests for missing logs and configuration.

The controller is installed automatically with the management cluster update to MOSK management 2.32.0. For details, see Collect support dump.

On a management cluster running a version earlier than MOSK management 2.32.0, you can install the controller manually as described below.

To install supportdump-controller:

  1. Identify the active KaaSRelease object:

    kubectl get kaasrelease -l kaas.mirantis.com/active=true
    
  2. Open the object for editing and add the following entry to the spec.management.helmReleases list:

    - chartURL: core/helm/supportdump-controller-1.45.13.tgz
      helmV3: true
      localVolumes:
      - bindMounts:
        - volPerNode: 1
        name: dump-data
      name: supportdump-controller
      namespace: kaas
      requires:
      - local-volume-provisioner
      values:
        image:
          tag: 1.45.13
      version: 1.45.13
    

Warning

Every management cluster update will remove this Helm release. Add it again after each update. If an update is in progress, add the entry to the serialized KaaSRelease object in the kaas.mirantis.com/mgmt-upgrade-target annotation of the management cluster.

For the description of the SupportDump API and the collection procedure, refer to Collect support dump in the MOSK 26.2 documentation.