After Migration

You can run these steps only when you have completed the migration of:

  • Cluster Stack

  • Management Stack

  • Instance Stack

These steps are intended to disable the old components installed with Axual Helm Charts.

Disable Platform-UI and Platform-API

Objective

To remove the old Platform-UI and Platform-API installation resources.

Execution

In the old values.yaml you used to configure the Axual Helm Charts installation, disable the components:

values.yaml 
global:
  mgmt:
    api:
      enabled: false
    ui:
      enabled: false

Verification

The resources of the uninstalled components are removed from the kubernetes cluster.

Disable Rest-Proxy and Schema-Registry

Objective

To remove the old Rest-Proxy and Schema-Registry installation resources.

Execution

In the old values.yaml you used to configure the Axual Helm Charts installation, disable the components:

values.yaml 
global:
  instance:
    srslave:
      enabled: false
    srmaster:
      enabled: false
    restproxy:
      enabled: false

Verification

The resources of the uninstalled components are removed from the kubernetes cluster.

Disable Instance-API and Discovery-API

Objective

To remove the old Instance-API and Discovery-API installation resources.

Before running this step, be sure that no user is using Axual Clients anymore.

Execution

In the old values.yaml you used to configure the Axual Helm Charts installation, disable the components:

values.yaml 
global:
  instance:
    discoveryapi:
      enabled: false
    instanceapi:
      enabled: false

Verification

The resources of the uninstalled components are removed from the kubernetes cluster.

Disable Stream-Browse and Cluster-Browse

Objective

To remove the old Stream-Browse and Cluster-Browse installation resources.

Execution

In the old values.yaml you used to configure the Axual Helm Charts installation, disable the components:

values.yaml 
global:
  mgmt:
    streambrowse:
      enabled: false
  cluster:
    clusterbrowse:
      enabled: false

Verification

The resources of the uninstalled components are removed from the kubernetes cluster.

Disable Cluster-API

Objective

To remove the standalone Cluster-API we have deployed as part of Cluster Stack migration.

Before running this step, be sure that there is no Discovery API running anymore.

Execution

In the existing standalone Cluster-API values.yaml disable the component:

values.yaml 
global:
  cluster:
    enabled: false

Verification

The resources of the uninstalled component are removed from the kubernetes cluster.