Convert v1alpha1 TFOperator custom resource to v2

Available since MOSK 24.2

In 24.1, MOSK introduces the API v2 for Tungsten Fabric. Since 24.2, Tungsten Fabric API v2 becomes default for new deployments and includes the ability to convert the existing v1alpha1 TFOperator to v2.

To learn more about the new custom resource structure, refer to MOSK 24.1 Tungsten Fabric API v2 Reference.

Convert v1alpha1 TFOperator to v2

Warning

Conversion of TFOperator causes recreation of the Tungsten Fabric service pods. Therefore, Mirantis recommends performing the conversion during a maintenance window.

Update the tungstenfabric-operator Helm release values in the corresponding ClusterRelease resource:

spec:
  helm:
    releases:
      - name: tungstenfabric-operator
        values:
          operator:
            convertToV2: true

When the chart changes apply, the tungstenfabric-operator-convert-to-v2 job performs the following:

  1. Saves the existing v1alpha1 TFOperator specification to the tfoperator-v1alpha1-copy ConfigMap

  2. Creates the v2 TFOperator custom resource

  3. Removes the redundant v1alpha1 TFOperator custom resource

While the conversion is being performed, monitor the recreation of the Tungsten Fabric service pods. Verify that TFOperator v2 has been created successfully:

kubectl -n tf describe tf.mirantis.com openstack-tf

Reverse the conversion of v1alpha1 TFOperator to v2

Warning

Conversion of TFOperator causes recreation of the Tungsten Fabric service pods. Therefore, Mirantis recommends performing the conversion during the maintenance window.

  1. Update the TFOperator HelmBundle:

    values:
      operator:
        convertToV2: false
    
  2. Manually, delete the v2 TFOperator custom resource:

    kubectl -n tf delete tf.mirantis.com openstack-tf
    
  3. Manually, create the v1alpha1 TFOperator custom resource using data from the tfoperator-v1alpha1-copy ConfigMap.