From aa639be98760b9988e0b4cb90b884a976f86fc93 Mon Sep 17 00:00:00 2001 From: xenolinux Date: Thu, 9 Jan 2025 17:24:05 +0530 Subject: [PATCH] OSDOCS#13013: restarting components in hcp --- modules/hosted-restart-hcp-components.adoc | 17 +++++++++++------ 1 file changed, 11 insertions(+), 6 deletions(-) diff --git a/modules/hosted-restart-hcp-components.adoc b/modules/hosted-restart-hcp-components.adoc index aae58b1c30ba..21f292681e32 100644 --- a/modules/hosted-restart-hcp-components.adoc +++ b/modules/hosted-restart-hcp-components.adoc @@ -10,21 +10,26 @@ If you are an administrator for hosted control planes, you can use the `hypershi .Procedure -To restart a control plane, annotate the `HostedCluster` resource by entering the following command: - +* To restart a control plane, annotate the `HostedCluster` resource by entering the following command: ++ [source,terminal] ---- $ oc annotate hostedcluster \ -n \ \ - hypershift.openshift.io/restart-date=$(date --iso-8601=seconds) + hypershift.openshift.io/restart-date=$(date --iso-8601=seconds) <1> ---- +<1> The control plane is restarted whenever the value of the annotation changes. The `date` command serves as the source of a unique string. The annotation is treated as a string, not a timestamp. + .Verification -The control plane is restarted whenever the value of the anonotation changes. The `date` command in the example serves as the source of a unique string. The annotation is treated as a string, not a timestamp. +After you restart a control plane, the following {hcp} components are typically restarted: -The following components are restarted: +[NOTE] +==== +You might see some additional components restarting as a side effect of changes implemented by the other components. +==== * catalog-operator * certified-operators-catalog @@ -50,4 +55,4 @@ The following components are restarted: * openshift-oauth-apiserver * packageserver * redhat-marketplace-catalog -* redhat-operators-catalog \ No newline at end of file +* redhat-operators-catalog