From 1905b0d02db630d841c2a094f459ef2641fae097 Mon Sep 17 00:00:00 2001 From: RichardHoch Date: Thu, 2 Feb 2023 13:50:22 +0200 Subject: [PATCH] MIG-1300: fix error in MTC workflow sample use case --- modules/migration-mtc-workflow.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/migration-mtc-workflow.adoc b/modules/migration-mtc-workflow.adoc index 31364e5e7f79..30cd193c23cd 100644 --- a/modules/migration-mtc-workflow.adoc +++ b/modules/migration-mtc-workflow.adoc @@ -15,7 +15,7 @@ You can migrate Kubernetes resources, persistent volume data, and internal conta * A namespace specified in a migration plan. * Namespace-scoped resources: When the {mtc-short} migrates a namespace, it migrates all the objects and resources associated with that namespace, such as services or pods. Additionally, if a resource that exists in the namespace but not at the cluster level depends on a resource that exists at the cluster level, the {mtc-short} migrates both resources. + -For example, a security context constraint (SCC) is a resource that exists at the cluster level and a service account (SA) is a resource that exists at the namespace level. If an SA exists in a namespace that the {mtc-short} migrates, the {mtc-short} automatically locates any SCCs that are linked to the SA and also migrates those SCCs. Similarly, the {mtc-short} migrates persistent volume claims that are linked to the persistent volumes of the namespace. +For example, a security context constraint (SCC) is a resource that exists at the cluster level and a service account (SA) is a resource that exists at the namespace level. If an SA exists in a namespace that the {mtc-short} migrates, the {mtc-short} automatically locates any SCCs that are linked to the SA and also migrates those SCCs. Similarly, the {mtc-short} migrates persistent volumes that are linked to the persistent volume claims of the namespace. + [NOTE] ====