You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/deployment/private-cloud/private-cloud-cluster/private-cloud-global-operator.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -149,7 +149,7 @@ Currently, there is no API support to convert a namespace from standard to globa
149
149
6. Click **Done** to return to the Namespaces Overview page.
150
150
151
151
{{% alert color="info" %}}
152
-
Once the standard namespaces are converted to Global Operator Managed namespace, thenthe status of the Clusterin which the standard namespace was present before conversion would be changed to **Conversion Finalized**, otherwise it will show **Conversion in Progress**ifnot all the namespaces within that cluster are converted.
152
+
After the standard namespaces are converted to Global Operator Managed namespace, the status of the clusterin which the standard namespace was present before conversion is changed to **Conversion Finalized**. If not all the namespaces within the cluster are converted yet, the status shows **Conversion in Progress**.
153
153
{{% /alert %}}
154
154
155
155
## Licensing
@@ -159,7 +159,7 @@ Once the standard namespaces are converted to Global Operator Managed namespace,
159
159
Configure Private Cloud License Management (PCLM) in the Global Operator namespace. For more information, see [Private Cloud License Manager](/developerportal/deploy/private-cloud/private-cloud-license-manager/).
160
160
161
161
{{% alert color="info" %}}
162
-
For Global Operator installations, execute the commands from PCLM section in both the Global Operator namespace and its managed namespaces where the license is intended to be applied. Make sure that identical PCLM license details are configured for both the Managed and Global Operator namespaces to avoid unexpected outcomes.
162
+
For Global Operator installations, execute the commands from the PCLM section in both the Global Operator namespace and its managed namespaces where the license must be applied. Make sure that identical PCLM license details are configured for both the Managed and Global Operator namespaces to avoid unexpected outcomes.
163
163
{{% /alert %}}
164
164
165
165
{{% alert color="warning" %}}
@@ -172,4 +172,4 @@ Claimed licenses are visible in the PCLM Statistics section of the Managed names
172
172
173
173
## Upgrading Managed Namespaces
174
174
175
-
When you [upgrade](/developerportal/deploy/private-cloud-upgrade-guide/#upgrade-cluster) the Global Operator main namespace, the managed namespaces within the global operator namespace are also upgraded automatically along with the main namespace.
175
+
When you [upgrade](/developerportal/deploy/private-cloud-upgrade-guide/#upgrade-cluster) the Global Operator main namespace, the managed namespaces within the global operator namespace are also automatically upgraded.
0 commit comments