Skip to content

[enterprise-4.18] OSDOCS#13013: Restarting components in hcp #87209

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 17, 2025
Merged

[enterprise-4.18] OSDOCS#13013: Restarting components in hcp #87209

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 11 additions & 6 deletions modules/hosted-restart-hcp-components.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 <hosted_cluster_namespace> \
<hosted_cluster_name> \
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
Expand All @@ -50,4 +55,4 @@ The following components are restarted:
* openshift-oauth-apiserver
* packageserver
* redhat-marketplace-catalog
* redhat-operators-catalog
* redhat-operators-catalog