Cloudera Docs

Migrating existing workbench and workload resources

When a workbench upgrade is triggered, the existing ingress resources are deleted, and new Gateway API resources are created.

Pre-migration steps

Before the migration, Administrators must complete the following steps:
  1. Identify any applications using a restricted subdomain.
  2. Rename the application's subdomain to a non-conflicting value.
  3. Update and redeploy any clients that rely on the old URL.

Migration

As part of the upgrade process, a migration job is automatically initiated to convert any existing Ingress objects into Gateway API resources for existing workloads.

Post-migration steps

The listed post-migration activities are only necessary if a migration issue is identified or if a restricted application subdomain name has been used.

  1. Modify the application's subdomain name.
  2. Manually adjust the hostname in the XListenerSet or HTTPRoute.
  3. Restart the istiod deployment by running the following command:
    kubectl rollout status deployment/istiod -n istio-system