Skip to main content
Version: 1.15.0

Replicate Resources

This topic describes how to replicate resources from a cluster to another cluster on a given slice.

Overview

The Replicate feature of the KubeSlice Manager helps you to efficiently transfer applications/resources from one cluster to another, irrespective of the clusters' cloud or data center locations.

info

At a given time, a replication process can occur only from a source worker cluster to a destination worker cluster.

View the Replication Status of Slices

To view the replication status of a slice:

  1. Go to Replicate on the left sidebar.

  2. On the Replicate page, under Slices, a list of slices and the clusters connected to each of them are available in a list.

    alt

  3. Expand each slice to see the resource replication status.

    alt

Replicate Resources on a Slice

To replicate resources on a slice:

warning

Be sure that the namespace that you will replicate from source cluster is not onboarded on to a slice from the destination cluster. Be sure that namespace sameness is disabled on the slice before starting a replication. After the completion of replication, onboard that replicated namespace from the destination cluster on to the slice to continue using KubeSlice features.

  1. Go to Replicate on the left sidebar.

  2. For the slice on which you want to replicate resources from the source cluster to the destination cluster connected to it, click the replicate icon towards its right.

    On the Replicate Resources pane, details are unfilled if no resources are replicated.

    alt

    On the Replicate Resources pane:

    warning

    Be sure that the namespace that you will replicate from source cluster is not onboarded on to a slice from the destination cluster. Be sure that namespace sameness is disabled on the slice before starting a replication. After the completion of replication, onboard that replicated namespace from the destination cluster on to the slice to continue using KubeSlice features.

    1. Select a Source Cluster from the drop-down list.

      alt

    2. Select namespaces that you want to migrate from the source cluster.

    3. Select the destination cluster to which you want to migrate the resources.

    4. Click Replicate.

    5. You are notified that the replication is initiated.

    6. Track the replication's pre-check progress.

      alt

      If there is any incompatibility pre-check, then the replication process gets halted.

    7. Close the pane and it takes you to the the landing page. Click the replication icon that is in red for the slice, whose pre-checks have just failed.

      alt

    8. The Replication pane provides the Job Status. The number of compatible, actionable, and incompatible pre-checks are listed. Based on the nature of pre-check errors related to namespaces, you get to choose one of these three options:

      note

      When a pre-check fails, these options appear for some errors but not always.

      • I want KubeSlice to remediate: This action triggers KubeSlice to increase the storage and start the replication automatically only if there are no other incompatibilities.

        If there are other incompatibilities besides storage, then the replication still remains in the pre-check phase.

      • I will do it myself: This action closes the replication pane and you must start the replication again.

      • I have made the changes: After you have done the changes, you can proceed with the replication.

        alt

        Click the View Progress link to see the pre-check results again (this link does not appear for all pre-check errors).

    9. [Optional] Click Job Info to see the job ID and the timestamp.

      alt

    10. Click Proceed with replication if you want to ignore the pre-check results.

    11. Track the replication job that is in progress.

      alt

    12. When the replication completes, close this pane.

      alt

  3. On the Replicate page, under Slices, expand the slice on which you performed replication to verify the replicated resources.

Replication Statuses

The different statuses of replication are Error, In Progress, and Success.

alt

Repeat Replication on the Source and the Destination Clusters

If the source and destination worker clusters have replicated resources, you can still replicate other namespaces from the same source and destination worker clusters.

warning

Be sure that the namespace that you will replicate from source cluster is not onboarded on to a slice from the destination cluster. Be sure that namespace sameness is disabled on the slice before starting a replication. After the completion of replication, onboard that replicated namespace from the destination cluster on to the slice to continue using KubeSlice features.

To start replication on a slice connected to clusters with replicated resources:

  1. Go to Replicate on the left sidebar.

  2. On the Replicate page, click the replicate icon at the right for the slice that you want to replicate. Alternatively, expand the slice details and click the arrow icon towards the right of an existing replication.

  3. On the Replicate Resources pane, click Start a new Replication.

    alt

  4. Select a different namespace from the source cluster to replicate on to the destination cluster.

  5. Track the replication process to completion.

  6. After the replication is complete, you can either start another replication or close the Replication Resources pane.

  7. On the Replicate page, under Slices, expand the slice on which you repeated replication to verify the replication details.

Delete a Replication

To delete a replication on the destination cluster:

  1. Go to Replicate on the left sidebar.

  2. On the Replicate page, expand the slice on which you want to delete replication.

    alt

  3. From the replications' list, for the replication that you want to remove, click the Delete icon against it.

  4. You will be notified to confirm the deletion. Type DELETE and click Delete Replication.

    alt

  5. On the Replicate page, expand the slice on which you deleted replication to verify the replication details.