Skip to content

OSDOCS-18910: Document OLM v1 deployment configuration API #1

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

Closed
cbippley wants to merge 30 commits into from
Closed

OSDOCS-18910: Document OLM v1 deployment configuration API #1

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
30 commits
Select commit Hold shift + click to select a range
4dfef78
OSDOCS-18432#Adding BM nodes to vSphere clusters TP -> GA
Feb 24, 2026
a6393fc
OSDOCS-18456#GCP PD images snapshot class
Feb 26, 2026
10d479c
OSDOCS#18166: Removing unsupported OSSO versions for 4.22
bergerhoffer Apr 23, 2026
bbf2711
OSDOCS#18167: Removing unsupported KDO versions for 4.22
bergerhoffer Apr 23, 2026
1c72c9b
OSDOCS-17649:Update acronyms where not defined_CQA jobs
jheraght May 1, 2026
3aa0a35
OSDOCS#18076: Updating the Kubernetes version in example output to 1.35
bergerhoffer May 5, 2026
930dc39
OSDOCS-17043_b:adding CQA updates
brendan-daly-red-hat May 6, 2026
ff9857f
Speeding Up Pulling Container Images/CRI-O Additional Storage Support
Apr 24, 2026
536f8fe
Merge pull request #111283 from brendan-daly-red-hat/OSDOCS-17043_b
skopacz1 May 8, 2026
ce4cf94
Merge pull request #107216 from lpettyjo/OSDOCS-18432
lpettyjo May 8, 2026
000e68d
Fix ConceptLink warnings in virt/support
abrennan89 May 8, 2026
20f031d
Fix asciidoc rendering error
rheslop May 8, 2026
d58fda6
Merge pull request #110809 from mburke5678/nodes-crio-addt-storage
mburke5678 May 8, 2026
fa0d55b
Merge pull request #111456 from rheslop/main-CNV-86780
rheslop May 8, 2026
79c82d5
Merge pull request #111455 from abrennan89/fix-concept-links-support
abrennan89 May 8, 2026
8fe968e
vale and dita checks for ROSA getting started
jc-berger Apr 28, 2026
0bf6425
more doc feedback
jc-berger May 8, 2026
0a074a5
fix build error
jc-berger May 8, 2026
d9db754
Merge pull request #107621 from lpettyjo/OSDOCS-18456
lpettyjo May 8, 2026
95e0f46
OSDOCS 8353 Boot new workers directly into custom pool configuration
Apr 2, 2026
937ff1b
more fixing of build log errors
jc-berger May 8, 2026
c419c79
Merge pull request #109551 from mburke5678/mco-boot-into-custom-mcp
mburke5678 May 8, 2026
db59423
Merge pull request #110911 from jc-berger/jcberger-18319-vale-rosa-ge…
EricPonvelle May 8, 2026
132fe2b
Revert "OSDOCS-18319 [ROSA]: Vale and Dita checks for ROSA getting st…
EricPonvelle May 8, 2026
1fa2856
Merge pull request #110703 from bergerhoffer/OSDOCS-18167
bergerhoffer May 11, 2026
d25ec7d
Merge pull request #110702 from bergerhoffer/OSDOCS-18166
bergerhoffer May 11, 2026
e156bbf
Merge pull request #111259 from bergerhoffer/OSDOCS-18076
bergerhoffer May 11, 2026
e7b9b85
Merge pull request #111469 from openshift/revert-110911-jcberger-1831…
EricPonvelle May 11, 2026
949f960
Merge pull request #111133 from jheraght/OSDOCS-17649
bhardesty May 11, 2026
2cf7462
OSDOCS-18910: Document OLM v1 deployment configuration API
cbippley May 11, 2026
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
2 changes: 2 additions & 0 deletions .vale/styles/config/vocabularies/OpenShiftDocs/accept.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,9 @@
[Tt]elco
[Uu]npause
Assisted Installer
ClusterObjectSets?
Control Plane Machine Set Operator
[Dd]eployment [Cc]onfigurations?
GHz
gpsd
gpspipe
Expand Down
1 change: 0 additions & 1 deletion .vale/styles/config/vocabularies/OpenShiftDocs/reject.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,6 @@
# Add terms that have a corresponding correctly capitalized form to accept.txt.

[Dd]eployment [Cc]onfigs?
[Dd]eployment [Cc]onfigurations?
[Oo]peratorize
[Ss]ingle [Nn]ode OpenShift
[Tt]hree [Nn]ode OpenShift
Expand Down
4 changes: 4 additions & 0 deletions _topic_maps/_topic_map.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2485,6 +2485,8 @@ Topics:
File: mco-update-boot-skew-mgmt
- Name: Manually updating the boot image
File: mco-update-boot-images-manual
- Name: Creating custom machine config pools
File: machine-config-custom-mcp
- Name: Managing unused rendered machine configs
File: machine-configs-garbage-collection
- Name: Image mode for OpenShift
Expand Down Expand Up @@ -2955,6 +2957,8 @@ Topics:
File: nodes-nodes-resources-configuring
- Name: Allocating specific CPUs for nodes in a cluster
File: nodes-nodes-resources-cpus
- Name: Additional CRI-O storage locations for faster container startup
File: nodes-nodes-additional-crio-storage
- Name: Enabling TLS security profiles for the kubelet
File: nodes-nodes-tls
Distros: openshift-enterprise,openshift-origin
Expand Down
18 changes: 16 additions & 2 deletions extensions/ce/olmv1-configuring-extensions.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,9 +7,9 @@ include::_attributes/common-attributes.adoc[]
toc::[]

[role="_abstract"]
In {olmv1-first}, extensions watch all namespaces by default. Some Operators support only namespace-scoped watching based on {olmv0} install modes. To install these Operators, configure the watch namespace for the extension. For more information, see "Discovering bundle install modes".
In {olmv1-first}, you can configure cluster extensions to customize installation behavior. This includes configuring watch namespaces for Operators that support only namespace-scoped watching based on {olmv0} install modes, and customizing operator pod deployments with resource limits, node placement, and other settings.

:FeatureName: Configuring a watch namespace for a cluster extension
:FeatureName: Configuring cluster extensions
include::snippets/technology-preview.adoc[]

include::modules/olmv1-config-api.adoc[leveloffset=+1]
Expand All @@ -29,8 +29,22 @@ include::modules/olmv1-config-api-watch-namespace-examples.adoc[leveloffset=+2]

include::modules/olmv1-clusterextension-watchnamespace-validation-errors.adoc[leveloffset=+2]

include::modules/olmv1-deployment-config-api.adoc[leveloffset=+1]

include::modules/olmv1-clusterobjectsets-deployment-mechanism.adoc[leveloffset=+1]

include::modules/olmv1-customizing-operator-deployments.adoc[leveloffset=+1]

include::modules/olmv1-deployment-config-examples.adoc[leveloffset=+1]

include::modules/olmv1-deployment-config-reference.adoc[leveloffset=+1]

include::modules/olmv1-deployment-config-troubleshooting.adoc[leveloffset=+1]

[id="olmv1-configuring-extensions_additional-resources"]
[role="_additional-resources"]
== Additional resources

* xref:../../extensions/ce/managing-ce.adoc#olmv1-installing-an-operator_managing-ce[Installing a cluster extension in all namespaces]
* link:https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/[Kubernetes: Assigning Pods to Nodes]
* link:https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/[Kubernetes: Taints and Tolerations]
34 changes: 34 additions & 0 deletions machine_configuration/machine-config-custom-mcp.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,34 @@
:_mod-docs-content-type: ASSEMBLY
[id="machine-config-creating-custom-mcp"]
= Creating custom machine config pools
include::_attributes/common-attributes.adoc[]
:context: machine-config-creating-custom-mcp

toc::[]

[role="_abstract"]
You can create custom machine config pools (MCP) to manage compute nodes for custom use cases that extend outside of the default node types. By using a custom machine config pool, you can deploy changes targeted only at nodes in the custom pool.

Custom machine config pools inherit their configurations from the `worker` machine config pool. Changes made to the `worker` machine config pool apply to nodes in the custom pool. However, changes made to the custom machine config pool apply only to the nodes in the custom pool. For more information on custom machine config pools, see "Node configuration management with machine config pools".

[NOTE]
====
Custom machine config pools for the control plane nodes are not supported.
====

For example, you could use a custom machine config pool to create an _infrastructure_ node. Components that you move to an infrastructure node do not need to be accounted for during sizing. For more information on infrastructure nodes, see "Creating infrastructure machine sets".

After you create the custom machine config pool, you can boot new nodes directly to the pool by creating a new machine set. Or, you can add existing nodes to the custom pool by using labels.

include::modules/machine-config-custom-mcp-automatic.adoc[leveloffset=+1]
include::modules/machine-config-custom-mcp-existing.adoc[leveloffset=+1]

[role="_additional-resources"]
[id="additional-resources_{context}"]
== Additional resources

* xref:../machine_configuration/index.adoc#architecture-machine-config-pools_machine-config-overview[Node configuration management with machine config pools]
* xref:../machine_configuration/mco-update-boot-images-manual.adoc#mco-update-boot-images-manual[Manually updating the boot image]
* xref:../machine_management/creating-infrastructure-machinesets.adoc#creating-infrastructure-machinesets[Creating infrastructure machine sets]


4 changes: 2 additions & 2 deletions modules/ai-adding-worker-nodes-to-cluster.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -323,6 +323,6 @@ $ oc get nodes
[source,terminal]
----
NAME STATUS ROLES AGE VERSION
control-plane-1.example.com Ready master,worker 56m v1.34.2
compute-1.example.com Ready worker 11m v1.34.2
control-plane-1.example.com Ready master,worker 56m v1.35.4
compute-1.example.com Ready worker 11m v1.35.4
----
6 changes: 3 additions & 3 deletions modules/aws-outposts-load-balancer-clb.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,9 +64,9 @@ $ oc get nodes -l <key_name>=<value>
[source,terminal]
----
NAME STATUS ROLES AGE VERSION
node1.example.com Ready worker 7h v1.34.2
node2.example.com Ready worker 7h v1.34.2
node3.example.com Ready worker 7h v1.34.2
node1.example.com Ready worker 7h v1.35.4
node2.example.com Ready worker 7h v1.35.4
node3.example.com Ready worker 7h v1.35.4
----

. Configure the Classic Load Balancer service by adding the cloud-based subnet information to the `annotations` field of the `Service` manifest:
Expand Down
4 changes: 2 additions & 2 deletions modules/cleaning-crio-storage.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -123,7 +123,7 @@ $ oc get nodes
+
----
NAME STATUS ROLES AGE VERSION
ci-ln-tkbxyft-f76d1-nvwhr-master-1 Ready, SchedulingDisabled master 133m v1.34.2
ci-ln-tkbxyft-f76d1-nvwhr-master-1 Ready, SchedulingDisabled master 133m v1.35.4
----
+
. Mark the node schedulable. You will know that the scheduling is enabled when `SchedulingDisabled` is no longer in status:
Expand All @@ -138,5 +138,5 @@ $ oc adm uncordon <node_name>
+
----
NAME STATUS ROLES AGE VERSION
ci-ln-tkbxyft-f76d1-nvwhr-master-1 Ready master 133m v1.34.2
ci-ln-tkbxyft-f76d1-nvwhr-master-1 Ready master 133m v1.35.4
----
12 changes: 6 additions & 6 deletions modules/cnf-configuring-nrop-on-schedlable-control-planes.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -122,12 +122,12 @@ $ oc get nodes
[source,terminal]
----
NAME STATUS ROLES AGE VERSION
worker-0 Ready worker,worker-cnf 100m v1.34.2
worker-1 Ready worker 93m v1.34.2
master-0 Ready control-plane,master,worker 108m v1.34.2
master-1 Ready control-plane,master,worker 107m v1.34.2
master-2 Ready control-plane,master,worker 107m v1.34.2
worker-2 Ready worker 100m v1.34.2
worker-0 Ready worker,worker-cnf 100m v1.35.4
worker-1 Ready worker 93m v1.35.4
master-0 Ready control-plane,master,worker 108m v1.35.4
master-1 Ready control-plane,master,worker 107m v1.35.4
master-2 Ready control-plane,master,worker 107m v1.35.4
worker-2 Ready worker 100m v1.35.4
----

. Verify that the NUMA Resources Operator’s pods are running on the intended nodes by running the following command. You should see a numaresourcesoperator pod for each node group you specified in the CR:
Expand Down
10 changes: 5 additions & 5 deletions modules/compliance-apply-remediation-for-customized-mcp.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,11 +23,11 @@ $ oc get nodes -n openshift-compliance
[source,terminal]
----
NAME STATUS ROLES AGE VERSION
ip-10-0-128-92.us-east-2.compute.internal Ready master 5h21m v1.34.2
ip-10-0-158-32.us-east-2.compute.internal Ready worker 5h17m v1.34.2
ip-10-0-166-81.us-east-2.compute.internal Ready worker 5h17m v1.34.2
ip-10-0-171-170.us-east-2.compute.internal Ready master 5h21m v1.34.2
ip-10-0-197-35.us-east-2.compute.internal Ready master 5h22m v1.34.2
ip-10-0-128-92.us-east-2.compute.internal Ready master 5h21m v1.35.4
ip-10-0-158-32.us-east-2.compute.internal Ready worker 5h17m v1.35.4
ip-10-0-166-81.us-east-2.compute.internal Ready worker 5h17m v1.35.4
ip-10-0-171-170.us-east-2.compute.internal Ready master 5h21m v1.35.4
ip-10-0-197-35.us-east-2.compute.internal Ready master 5h22m v1.35.4
----

. Add a label to nodes.
Expand Down
12 changes: 6 additions & 6 deletions modules/connected-to-disconnected-verify.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,10 +44,10 @@ $ oc get nodes
[source,terminal]
----
NAME STATUS ROLES AGE VERSION
ci-ln-47ltxtb-f76d1-mrffg-master-0 Ready master 42m v1.34.2
ci-ln-47ltxtb-f76d1-mrffg-master-1 Ready master 42m v1.34.2
ci-ln-47ltxtb-f76d1-mrffg-master-2 Ready master 42m v1.34.2
ci-ln-47ltxtb-f76d1-mrffg-worker-a-gsxbz Ready worker 35m v1.34.2
ci-ln-47ltxtb-f76d1-mrffg-worker-b-5qqdx Ready worker 35m v1.34.2
ci-ln-47ltxtb-f76d1-mrffg-worker-c-rjkpq Ready worker 34m v1.34.2
ci-ln-47ltxtb-f76d1-mrffg-master-0 Ready master 42m v1.35.4
ci-ln-47ltxtb-f76d1-mrffg-master-1 Ready master 42m v1.35.4
ci-ln-47ltxtb-f76d1-mrffg-master-2 Ready master 42m v1.35.4
ci-ln-47ltxtb-f76d1-mrffg-worker-a-gsxbz Ready worker 35m v1.35.4
ci-ln-47ltxtb-f76d1-mrffg-worker-b-5qqdx Ready worker 35m v1.35.4
ci-ln-47ltxtb-f76d1-mrffg-worker-c-rjkpq Ready worker 34m v1.35.4
----
12 changes: 6 additions & 6 deletions modules/coreos-layering-configuring-on-revert.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,12 +64,12 @@ $ oc get nodes
[source,terminal]
----
NAME STATUS ROLES AGE VERSION
ip-10-0-148-79.us-west-1.compute.internal Ready worker 32m v1.34.2
ip-10-0-155-125.us-west-1.compute.internal Ready,SchedulingDisabled worker 35m v1.34.2
ip-10-0-170-47.us-west-1.compute.internal Ready control-plane,master 42m v1.34.2
ip-10-0-174-77.us-west-1.compute.internal Ready control-plane,master 42m v1.34.2
ip-10-0-211-49.us-west-1.compute.internal Ready control-plane,master 42m v1.34.2
ip-10-0-218-151.us-west-1.compute.internal Ready worker 31m v1.34.2
ip-10-0-148-79.us-west-1.compute.internal Ready worker 32m v1.35.4
ip-10-0-155-125.us-west-1.compute.internal Ready,SchedulingDisabled worker 35m v1.35.4
ip-10-0-170-47.us-west-1.compute.internal Ready control-plane,master 42m v1.35.4
ip-10-0-174-77.us-west-1.compute.internal Ready control-plane,master 42m v1.35.4
ip-10-0-211-49.us-west-1.compute.internal Ready control-plane,master 42m v1.35.4
ip-10-0-218-151.us-west-1.compute.internal Ready worker 31m v1.35.4
----

** When the node is back in the `Ready` state, check that the node is using the base image:
Expand Down
12 changes: 6 additions & 6 deletions modules/coreos-layering-configuring.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -165,12 +165,12 @@ $ oc get nodes
[source,terminal]
----
NAME STATUS ROLES AGE VERSION
ip-10-0-148-79.us-west-1.compute.internal Ready worker 32m v1.34.2
ip-10-0-155-125.us-west-1.compute.internal Ready,SchedulingDisabled worker 35m v1.34.2
ip-10-0-170-47.us-west-1.compute.internal Ready control-plane,master 42m v1.34.2
ip-10-0-174-77.us-west-1.compute.internal Ready control-plane,master 42m v1.34.2
ip-10-0-211-49.us-west-1.compute.internal Ready control-plane,master 42m v1.34.2
ip-10-0-218-151.us-west-1.compute.internal Ready worker 31m v1.34.2
ip-10-0-148-79.us-west-1.compute.internal Ready worker 32m v1.35.4
ip-10-0-155-125.us-west-1.compute.internal Ready,SchedulingDisabled worker 35m v1.35.4
ip-10-0-170-47.us-west-1.compute.internal Ready control-plane,master 42m v1.35.4
ip-10-0-174-77.us-west-1.compute.internal Ready control-plane,master 42m v1.35.4
ip-10-0-211-49.us-west-1.compute.internal Ready control-plane,master 42m v1.35.4
ip-10-0-218-151.us-west-1.compute.internal Ready worker 31m v1.35.4
----

. When the node is back in the `Ready` state, check that the node is using the custom layered image:
Expand Down
12 changes: 6 additions & 6 deletions modules/coreos-layering-removing.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,12 +52,12 @@ $ oc get nodes
[source,terminal]
----
NAME STATUS ROLES AGE VERSION
ip-10-0-148-79.us-west-1.compute.internal Ready worker 32m v1.34.2
ip-10-0-155-125.us-west-1.compute.internal Ready,SchedulingDisabled worker 35m v1.34.2
ip-10-0-170-47.us-west-1.compute.internal Ready control-plane,master 42m v1.34.2
ip-10-0-174-77.us-west-1.compute.internal Ready control-plane,master 42m v1.34.2
ip-10-0-211-49.us-west-1.compute.internal Ready control-plane,master 42m v1.34.2
ip-10-0-218-151.us-west-1.compute.internal Ready worker 31m v1.34.2
ip-10-0-148-79.us-west-1.compute.internal Ready worker 32m v1.35.4
ip-10-0-155-125.us-west-1.compute.internal Ready,SchedulingDisabled worker 35m v1.35.4
ip-10-0-170-47.us-west-1.compute.internal Ready control-plane,master 42m v1.35.4
ip-10-0-174-77.us-west-1.compute.internal Ready control-plane,master 42m v1.35.4
ip-10-0-211-49.us-west-1.compute.internal Ready control-plane,master 42m v1.35.4
ip-10-0-218-151.us-west-1.compute.internal Ready worker 31m v1.35.4
----

. When the node is back in the `Ready` state, check that the node is using the base image:
Expand Down
24 changes: 12 additions & 12 deletions modules/graceful-restart.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,9 +58,9 @@ The control plane nodes are ready if the status is `Ready`, as shown in the foll
[source,terminal]
----
NAME STATUS ROLES AGE VERSION
ip-10-0-168-251.ec2.internal Ready control-plane,master 75m v1.34.2
ip-10-0-170-223.ec2.internal Ready control-plane,master 75m v1.34.2
ip-10-0-211-16.ec2.internal Ready control-plane,master 75m v1.34.2
ip-10-0-168-251.ec2.internal Ready control-plane,master 75m v1.35.4
ip-10-0-170-223.ec2.internal Ready control-plane,master 75m v1.35.4
ip-10-0-211-16.ec2.internal Ready control-plane,master 75m v1.35.4
----

. If the control plane nodes are _not_ ready, then check whether there are any pending certificate signing requests (CSRs) that must be approved.
Expand Down Expand Up @@ -99,9 +99,9 @@ The worker nodes are ready if the status is `Ready`, as shown in the following o
[source,terminal]
----
NAME STATUS ROLES AGE VERSION
ip-10-0-179-95.ec2.internal Ready worker 64m v1.34.2
ip-10-0-182-134.ec2.internal Ready worker 64m v1.34.2
ip-10-0-250-100.ec2.internal Ready worker 64m v1.34.2
ip-10-0-179-95.ec2.internal Ready worker 64m v1.35.4
ip-10-0-182-134.ec2.internal Ready worker 64m v1.35.4
ip-10-0-250-100.ec2.internal Ready worker 64m v1.35.4
----

. If the worker nodes are _not_ ready, then check whether there are any pending certificate signing requests (CSRs) that must be approved.
Expand Down Expand Up @@ -172,12 +172,12 @@ Check that the status for all nodes is `Ready`.
[source,terminal]
----
NAME STATUS ROLES AGE VERSION
ip-10-0-168-251.ec2.internal Ready control-plane,master 82m v1.34.2
ip-10-0-170-223.ec2.internal Ready control-plane,master 82m v1.34.2
ip-10-0-179-95.ec2.internal Ready worker 70m v1.34.2
ip-10-0-182-134.ec2.internal Ready worker 70m v1.34.2
ip-10-0-211-16.ec2.internal Ready control-plane,master 82m v1.34.2
ip-10-0-250-100.ec2.internal Ready worker 69m v1.34.2
ip-10-0-168-251.ec2.internal Ready control-plane,master 82m v1.35.4
ip-10-0-170-223.ec2.internal Ready control-plane,master 82m v1.35.4
ip-10-0-179-95.ec2.internal Ready worker 70m v1.35.4
ip-10-0-182-134.ec2.internal Ready worker 70m v1.35.4
ip-10-0-211-16.ec2.internal Ready control-plane,master 82m v1.35.4
ip-10-0-250-100.ec2.internal Ready worker 69m v1.35.4
----
+
If the cluster did not start properly, you might need to restore your cluster using an etcd backup. For more information, see "Restoring to a previous cluster state".
4 changes: 2 additions & 2 deletions modules/hcp-np-capacity-blocks.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -137,6 +137,6 @@ $ oc get nodes
[source, terminal]
----
NAME STATUS ROLES AGE VERSION
ip-10-0-132-74.ec2.internal Ready worker 17m v1.34.2
ip-10-0-134-183.ec2.internal Ready worker 4h5m v1.34.2
ip-10-0-132-74.ec2.internal Ready worker 17m v1.35.4
ip-10-0-134-183.ec2.internal Ready worker 4h5m v1.35.4
----
12 changes: 6 additions & 6 deletions modules/hibernating-cluster-hibernate.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,12 +36,12 @@ $ oc get nodes
[source,terminal]
----
NAME STATUS ROLES AGE VERSION
ci-ln-812tb4k-72292-8bcj7-master-0 Ready control-plane,master 32m v1.34.2
ci-ln-812tb4k-72292-8bcj7-master-1 Ready control-plane,master 32m v1.34.2
ci-ln-812tb4k-72292-8bcj7-master-2 Ready control-plane,master 32m v1.34.2
Ci-ln-812tb4k-72292-8bcj7-worker-a-zhdvk Ready worker 19m v1.34.2
ci-ln-812tb4k-72292-8bcj7-worker-b-9hrmv Ready worker 19m v1.34.2
ci-ln-812tb4k-72292-8bcj7-worker-c-q8mw2 Ready worker 19m v1.34.2
ci-ln-812tb4k-72292-8bcj7-master-0 Ready control-plane,master 32m v1.35.4
ci-ln-812tb4k-72292-8bcj7-master-1 Ready control-plane,master 32m v1.35.4
ci-ln-812tb4k-72292-8bcj7-master-2 Ready control-plane,master 32m v1.35.4
Ci-ln-812tb4k-72292-8bcj7-worker-a-zhdvk Ready worker 19m v1.35.4
ci-ln-812tb4k-72292-8bcj7-worker-b-9hrmv Ready worker 19m v1.35.4
ci-ln-812tb4k-72292-8bcj7-worker-c-q8mw2 Ready worker 19m v1.35.4
----
+
All nodes should show `Ready` in the `STATUS` column.
Expand Down
Loading