[OSDOCS-7645]: Remove Note Regarding Inability to Delete Default Machine Pool, other MP updates #64189

mletalie · 2023-08-31T17:05:19Z

Version(s):

4.13+
Issue:

Link to docs preview:

https://64189--docspreview.netlify.app/openshift-rosa/latest/rosa_cluster_admin/rosa_nodes/rosa-managing-worker-nodes#creating_a_machine_pool_rosa-managing-worker-nodes

https://64189--docspreview.netlify.app/openshift-rosa/latest/rosa_cluster_admin/rosa_nodes/rosa-managing-worker-nodes#deleting-machine-poolsrosa-managing-worker-nodes

https://64189--docspreview.netlify.app/openshift-rosa/latest/rosa_cluster_admin/rosa_nodes/rosa-managing-worker-nodes#rosa-adding-taints-clirosa-managing-worker-nodes

QE review:

QE has approved this change.

Additional information:

ocpdocs-previewbot · 2023-08-31T17:17:44Z

🤖 Updated build preview is available at:
https://64189--docspreview.netlify.app

Build log: https://circleci.com/gh/ocpdocs-previewbot/openshift-docs/24159

bchandra-ocp · 2023-09-06T01:00:32Z

https://64189--docspreview.netlify.app/openshift-rosa/latest/rosa_cluster_admin/rosa_nodes/rosa-nodes-machinepools-about#machine-pools -

We need to update the list to reflect a) You can remove or add labels to any machine pool b) You can add taint to any machine pool as long as there is one machine pool without any taints c) You can create or delete a machine pool as long as there is one machine pool without any taints.
"By default, a cluster has one machine pool. During cluster installation, you can label this machine pool. After the cluster is installed its node type or size cannot be changed." This needs to be corrected: "By default, a cluster has one machine pool. During cluster installation, you can define instance type or size and add labels to this machine pool."
The NOTE in the box already covers for the fact that once created, machine pool can't be updated to change the node type or size.

https://64189--docspreview.netlify.app/openshift-rosa/latest/rosa_cluster_admin/rosa_nodes/rosa-nodes-machinepools-about#machine-pools-in-multiple-zone-clusters

The whole section starting with "When you create a machine pool..." can be simplified into following two sentences that help customer with the feature:

In a cluster created across multiple Availability Zones (AZ), the machine pools can be created across either all the three AZs or any single AZ of your choice. The machine pool created by default at the time of cluster creation will be created with machines in all 3 AZs and scale in multiples of 3.

https://64189--docspreview.netlify.app/openshift-rosa/latest/rosa_cluster_admin/rosa_nodes/rosa-managing-worker-nodes

What's the difference between two bullet points under 5 (b) "Set the minimum and maximum node count limits for autoscaling."? Perhaps, we need to say what are allowed minimums and allowed values (multiples of 3 in case of 3 AZs)?
The NOTE about optionally configuring autoscaling is already covered by saying step 5 is Optional. Do we need that NOTE box?
Step 7 to Optionally configure disk size must be expanded. It should include what's default, what's minimum and maximum values etc.
Step 8: same comment about NOTE box. We can remove that since the step is Optional already
Step 8 c: Needs a NOTE to call out that creating a machine pool with Taint will be possible only if the cluster already has a machine pool w/o taint.

xueli181114 · 2023-09-07T11:47:24Z

modules/creating-a-machine-pool-ocm.adoc

@@ -86,6 +86,10 @@ endif::openshift-rosa[]
 .. Expand the *Edit node labels and taints* menu.
 .. Under *Node labels*, add *Key* and *Value* entries for your node labels.
 .. Under *Taints*, add *Key* and *Value* entries for your taints.
+[NOTE]
+====
+Creating a machine pool with taints is only possible if the cluster already has at least one machine pool without a taint.


Hmm... In theory a cluster will always to have a machinepool without taint. So customer can create machinepool with taint anytime.

@xueli181114, Good point. That being said, I will leave it in for now as it was a directive (and is while technically a given, is also factual). Will see if there is any other input to remove. Thx.

xueli181114 · 2023-09-07T11:49:56Z

modules/rosa-adding-taints-cli.adoc

@@ -10,6 +10,10 @@

 You can add taints to a machine pool for your Red Hat OpenShift Service on AWS (ROSA) cluster by using the ROSA CLI.

+[NOTE]
+====
+For users of ROSA CLI `rosa` version 1.2.25 and prior versions, the number of taints cannot be changed within the machine pool (ID=`Default`) created along with the cluster. cannot be deleted. For users of ROSA CLI `rosa` version 1.2.26 and beyond, the number of taints can be changed within the machine pool (ID=`worker`) created along with the cluster.


Suggested change

For users of ROSA CLI `rosa` version 1.2.25 and prior versions, the number of taints cannot be changed within the machine pool (ID=`Default`) created along with the cluster. cannot be deleted. For users of ROSA CLI `rosa` version 1.2.26 and beyond, the number of taints can be changed within the machine pool (ID=`worker`) created along with the cluster.

For users of ROSA CLI `rosa` version 1.2.25 and prior versions, the number of taints cannot be changed within the machine pool (ID=`Default`) created along with the cluster cannot be deleted. For users of ROSA CLI `rosa` version 1.2.26 and beyond, the number of taints can be changed within the machine pool (ID=`worker`) created along with the cluster that contains no taints and at least two instances for a single-AZ cluster or three instances for a multi-AZ cluster.

xueli181114 · 2023-09-07T12:02:56Z

rosa_cluster_admin/rosa_nodes/rosa-nodes-machinepools-about.adoc

 * You can add additional machine pools to an existing cluster.
+* You can add taints to any machine pool as long as there is one machine pool without any taints.


The machinepool should at the same time have untaint 2(for single zone) and 3(for multi zone) replicas

lixue@Xue-Lis-MacBook-Pro ~ % rosa edit machinepool worker -c sdq-ci-twppd --taints kwy=value:NoSchedule E: Failed to update machine pool 'worker' on cluster 'sdq-ci-twppd': Machine pool 'worker' for cluster '263hpcg0hqb5v4qkp94taut6rnn4apat' can't be updated with provided params. At least one machine pool able to run OCP workload is required. Pool should not have taints and minimum replica count should be '2' lixue@Xue-Lis-MacBook-Pro ~ % rosa list machinepools -c sdq-ci-twppd ID AUTOSCALING REPLICAS INSTANCE TYPE LABELS TAINTS AVAILABILITY ZONES SUBNETS SPOT INSTANCES DISK SIZE sz1 No 1 m5.xlarge us-west-2b subnet-02c45e21191037c15 No 300 GiB worker Yes 3-6 m5.xlarge label1/openshift.com=labelvalue1, label2/openshift.com=labelvalue2 us-west-2a, us-west-2b, us-west-2c subnet-0bc1a548e9a8b46e1, subnet-02c45e21191037c15, subnet-09416be08e29bd88c No 150 GiB

xueli181114 · 2023-09-07T12:13:44Z

rosa_cluster_admin/rosa_nodes/rosa-nodes-machinepools-about.adoc

 * You can add additional machine pools to an existing cluster.
+* You can add taints to any machine pool as long as there is one machine pool without any taints.
+* You can create or delete a machine pool as long as there is one machine pool without any taints.


Same with above

xueli181114 · 2023-09-07T12:16:33Z

Any preview changes for OSD part?
Should we clarify about non-ccs cluster cannot delete/taints the default worker pool in the doc? Needs PM's confirmation

xueli181114 · 2023-09-07T12:28:51Z

And per the preview file https://64189--docspreview.netlify.app/openshift-rosa/latest/rosa_cluster_admin/rosa_nodes/rosa-managing-worker-nodes#rosa-managing-worker-nodes
It shows Worker node instance type but on UI it's Compute node instance type
And so do Worker node count should be Compute node count (per zone)

xueli181114 · 2023-09-07T12:32:02Z

modules/creating-a-machine-pool-ocm.adoc

+[NOTE]
+====
+Creating a machine pool with taints is only possible if the cluster already has at least one machine pool without a taint.
+====
 .. For each taint, select an *Effect* from the drop-down menu. Available options include `NoSchedule`, `PreferNoSchedule`, and `NoExecute`.


Above highlight message make this line wrapped as another charactered list which starts with a again.

xueli181114 · 2023-09-07T12:43:25Z

And per tuning config part
https://64189--docspreview.netlify.app/openshift-rosa/latest/rosa_cluster_admin/rosa_nodes/rosa-managing-worker-nodes#rosa-adding-tuning_rosa-managing-worker-nodes
tuning config only work for hosted cluster, it's not highlighted
And commands output should be updated, there is no Default worker pool for hosted cluster.

mletalie · 2023-09-08T14:57:42Z

https://64189--docspreview.netlify.app/openshift-rosa/latest/rosa_cluster_admin/rosa_nodes/rosa-nodes-machinepools-about#machine-pools -

We need to update the list to reflect a) You can remove or add labels to any machine pool b) You can add taint to any machine pool as long as there is one machine pool without any taints c) You can create or delete a machine pool as long as there is one machine pool without any taints.

"By default, a cluster has one machine pool. During cluster installation, you can label this machine pool. After the cluster is installed its node type or size cannot be changed." This needs to be corrected: "By default, a cluster has one machine pool. During cluster installation, you can define instance type or size and add labels to this machine pool."

The NOTE in the box already covers for the fact that once created, machine pool can't be updated to change the node type or size.

https://64189--docspreview.netlify.app/openshift-rosa/latest/rosa_cluster_admin/rosa_nodes/rosa-nodes-machinepools-about#machine-pools-in-multiple-zone-clusters

The whole section starting with "When you create a machine pool..." can be simplified into following two sentences that help customer with the feature:

In a cluster created across multiple Availability Zones (AZ), the machine pools can be created across either all the three AZs or any single AZ of your choice. The machine pool created by default at the time of cluster creation will be created with machines in all 3 AZs and scale in multiples of 3.

https://64189--docspreview.netlify.app/openshift-rosa/latest/rosa_cluster_admin/rosa_nodes/rosa-managing-worker-nodes

What's the difference between two bullet points under 5 (b) "Set the minimum and maximum node count limits for autoscaling."? Perhaps, we need to say what are allowed minimums and allowed values (multiples of 3 in case of 3 AZs)?

The NOTE about optionally configuring autoscaling is already covered by saying step 5 is Optional. Do we need that NOTE box?

Step 7 to Optionally configure disk size must be expanded. It should include what's default, what's minimum and maximum values etc.

Step 8: same comment about NOTE box. We can remove that since the step is Optional already

Step 8 c: Needs a NOTE to call out that creating a machine pool with Taint will be possible only if the cluster already has a machine pool w/o taint.

Addressed everything in this comment except #1, #2 and #3 in last section of comment. Outside the scope of the ticket, and this needs to get merged by 9/11/23. Will address these concerns in another ticket asap.

mletalie · 2023-09-08T15:14:20Z

/label peer-review-needed

tmalove · 2023-09-08T15:15:47Z

/remove-label peer-review-needed
/label peer-review-in-progress

mletalie · 2023-09-08T15:43:09Z

Any preview changes for OSD part? Should we clarify about non-ccs cluster cannot delete/taints the default worker pool in the doc? Needs PM's confirmation

As far as I know, this will be addressed in another ticket. I will follow up with team/PR.

tmalove · 2023-09-08T15:36:24Z

modules/creating-a-machine-pool-ocm.adoc

@@ -23,12 +23,12 @@ endif::openshift-rosa[]
 ifndef::openshift-rosa[]
 [IMPORTANT]
 ====
-The compute (also known as worker) node instance types, autoscaling options, and node counts that are available to you depend on your 
+The compute (also known as worker) node instance types, autoscaling options, and node counts that are available to you depend on your


Suggested change

The compute (also known as worker) node instance types, autoscaling options, and node counts that are available to you depend on your

The compute (also known as worker) node instance types, autoscaling options, and node counts that are available depend on your

See SSG: https://redhat-documentation.github.io/supplementary-style-guide/#minimalism

tmalove · 2023-09-08T16:04:17Z

modules/creating-a-machine-pool.adoc

+A machine pool is created when you install a {product-title} (ROSA) cluster. After installation, you can create additional machine pools for your cluster by using {cluster-manager} or the ROSA CLI (`rosa`).
+[NOTE]
+====
+For users of ROSA CLI `rosa` version 1.2.25 and prior versions, the machine pool created along with the cluster is identified as `Default`. For users of ROSA CLI  `rosa` version 1.2.26 and beyond, the machine pool created along with the cluster is identified as `worker`.


Suggested change

For users of ROSA CLI `rosa` version 1.2.25 and prior versions, the machine pool created along with the cluster is identified as `Default`. For users of ROSA CLI `rosa` version 1.2.26 and beyond, the machine pool created along with the cluster is identified as `worker`.

For users of ROSA CLI `rosa` version 1.2.25 and earlier versions, the machine pool created along with the cluster is identified as `Default`. For users of ROSA CLI `rosa` version 1.2.26 and later, the machine pool created along with the cluster is identified as `worker`.

tmalove · 2023-09-08T16:06:53Z

modules/deleting-machine-pools-cli.adoc

@@ -7,6 +7,11 @@
 = Deleting a machine pool using the ROSA CLI
 You can delete a machine pool for your Red Hat OpenShift Service on AWS (ROSA) cluster by using the ROSA CLI.

+[NOTE]
+====
+For users of ROSA CLI `rosa` version 1.2.25 and prior versions, the machine pool (ID='Default') created along with the cluster cannot be deleted. For users of ROSA CLI `rosa` version 1.2.26 and beyond, the machine pool (ID='worker') created along with the cluster can be deleted as long as there is one machine pool within the cluster that contains no taints and at least two replicas for a single-AZ cluster or three replicas for a multi-AZ cluster.


Suggested change

For users of ROSA CLI `rosa` version 1.2.25 and prior versions, the machine pool (ID='Default') created along with the cluster cannot be deleted. For users of ROSA CLI `rosa` version 1.2.26 and beyond, the machine pool (ID='worker') created along with the cluster can be deleted as long as there is one machine pool within the cluster that contains no taints and at least two replicas for a single-AZ cluster or three replicas for a multi-AZ cluster.

For users of ROSA CLI `rosa` version 1.2.25 and earlier versions, the machine pool (ID='Default') that is created along with the cluster cannot be deleted. For users of ROSA CLI `rosa` version 1.2.26 and later, the machine pool (ID='worker') that is created along with the cluster can be deleted as long as there is one machine pool within the cluster that contains no taints, and at least two replicas for a single-AZ cluster or three replicas for a multi-AZ cluster.

Does 'AZ' modify 'cluster'? Should it be 'single AZ-cluster' and 'multi AZ-cluster'?

Hi @tmalove, the hyphen looks to be where it should be; however, in doing some research on our docs and AWS docs, the majority of the time "M" in multi-AZ is capped. Same with "S" in single-AZ. so I am going to go with that. May need to be added to our style guide...thx.

tmalove · 2023-09-08T16:07:38Z

modules/deleting-machine-pools.adoc

 .Prerequisites

 * You have created an {product-title} cluster.
 * The cluster is in the ready state.
-* You have an existing machine pool without any taints and with at least two instances for a single-AZ cluster or three instances for a multi-AZ cluster.
+* You have an existing machine pool without any taints and with at least two replicas for a single-AZ cluster or three replicas for a multi-AZ cluster.


See my earlier question about 'AZ-cluster'.

tmalove · 2023-09-08T16:10:47Z

modules/rosa-adding-taints-cli.adoc

@@ -10,6 +10,10 @@

 You can add taints to a machine pool for your Red Hat OpenShift Service on AWS (ROSA) cluster by using the ROSA CLI.

+[NOTE]
+====
+For users of ROSA CLI `rosa` version 1.2.25 and prior versions, the number of taints cannot be changed within the machine pool (ID=`Default`) created along with the cluster. For users of ROSA CLI `rosa` version 1.2.26 and beyond, the number of taints can be changed within the machine pool (ID=`worker`) created along with the cluster. There must be at least one machine pool without any taints and with at least two replicas for a single-AZ cluster or three replicas for a multi-AZ cluster.


Suggested change

For users of ROSA CLI `rosa` version 1.2.25 and prior versions, the number of taints cannot be changed within the machine pool (ID=`Default`) created along with the cluster. For users of ROSA CLI `rosa` version 1.2.26 and beyond, the number of taints can be changed within the machine pool (ID=`worker`) created along with the cluster. There must be at least one machine pool without any taints and with at least two replicas for a single-AZ cluster or three replicas for a multi-AZ cluster.

For users of ROSA CLI `rosa` version 1.2.25 and earlier versions, the number of taints cannot be changed within the machine pool (ID=`Default`) that are created along with the cluster. For users of ROSA CLI `rosa` version 1.2.26 and later, the number of taints can be changed within the machine pool (ID=`worker`) that are created along with the cluster. There must be at least one machine pool without any taints and with at least two replicas for a single-AZ cluster or three replicas for a multi-AZ cluster.

tmalove · 2023-09-08T16:12:18Z

rosa_cluster_admin/rosa_nodes/rosa-nodes-machinepools-about.adoc


 Multiple machine pools can exist on a single cluster, and each machine pool can contain a unique node type and node size configuration.

 == Machine pools in multiple zone clusters
-When you create a machine pool in a multiple availability zone (Multi-AZ) cluster, that one machine pool has 3 zones. The machine pool, in turn, creates a total of 3 compute machine sets - one for each zone in the cluster. Each of those compute machine sets manages one or more machines in its respective availability zone.
+In a cluster created across multiple Availability Zones (AZ), the machine pools can be created across either all of the three AZs or any single AZ of your choice. The machine pool created by default at the time of cluster creation will be created with machines in all three AZs and scale in multiples of three.


Suggested change

In a cluster created across multiple Availability Zones (AZ), the machine pools can be created across either all of the three AZs or any single AZ of your choice. The machine pool created by default at the time of cluster creation will be created with machines in all three AZs and scale in multiples of three.

In a cluster that is created across multiple Availability Zones (AZ), the machine pools can be created across either all of the three AZs or any single AZ of your choice. The machine pool created by default at the time of cluster creation will be created with machines in all three AZs and scale in multiples of three.

tmalove · 2023-09-08T16:13:12Z

/remove-label peer-review-in-progress
/label peer-review-done

mletalie · 2023-09-08T17:33:47Z

/label merge-review-needed

EricPonvelle · 2023-09-08T17:37:00Z

/cherrypick enterprise-4.13

EricPonvelle · 2023-09-08T17:37:05Z

/cherrypick enterprise-4.14

openshift-cherrypick-robot · 2023-09-08T17:37:49Z

@EricPonvelle: new pull request created: #64541

In response to this:

/cherrypick enterprise-4.13

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

openshift-cherrypick-robot · 2023-09-08T17:37:53Z

@EricPonvelle: new pull request created: #64542

In response to this:

/cherrypick enterprise-4.14

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

openshift-ci bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Aug 31, 2023

mletalie force-pushed the OSDOCS-7645 branch from c0da6d5 to f9268ac Compare August 31, 2023 17:07

openshift-ci bot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Aug 31, 2023

mletalie changed the title ~~Osdocs 7645~~ [OSDOCS-7645]: Remove Note Regarding Inability to Delete Default Machine Pool, other MP updates Aug 31, 2023

mletalie force-pushed the OSDOCS-7645 branch from f9268ac to 35fd02f Compare September 5, 2023 17:24

openshift-ci bot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Sep 5, 2023

mletalie force-pushed the OSDOCS-7645 branch from ee405b3 to 2300fa7 Compare September 5, 2023 20:35

mletalie force-pushed the OSDOCS-7645 branch from 2300fa7 to 39eafb3 Compare September 7, 2023 11:08

xueli181114 reviewed Sep 7, 2023

View reviewed changes

mletalie force-pushed the OSDOCS-7645 branch from 38934de to 2a1398a Compare September 8, 2023 15:09

openshift-ci bot added the peer-review-needed Signifies that the peer review team needs to review this PR label Sep 8, 2023

openshift-ci bot added peer-review-in-progress Signifies that the peer review team is reviewing this PR and removed peer-review-needed Signifies that the peer review team needs to review this PR labels Sep 8, 2023

tmalove approved these changes Sep 8, 2023

View reviewed changes

openshift-ci bot added peer-review-done Signifies that the peer review team has reviewed this PR and removed peer-review-in-progress Signifies that the peer review team is reviewing this PR labels Sep 8, 2023

mletalie force-pushed the OSDOCS-7645 branch from 2a1398a to 4e4f3fc Compare September 8, 2023 16:57

Remove default machine pool info

fb5bc59

mletalie force-pushed the OSDOCS-7645 branch from 4e4f3fc to fb5bc59 Compare September 8, 2023 16:58

openshift-ci bot added the merge-review-needed Signifies that the merge review team needs to review this PR label Sep 8, 2023

EricPonvelle merged commit 090505e into openshift:main Sep 8, 2023

openshift-cherrypick-robot mentioned this pull request Sep 8, 2023

[enterprise-4.13] [OSDOCS-7645]: Remove Note Regarding Inability to Delete Default Machine Pool, other MP updates #64541

Merged

openshift-cherrypick-robot mentioned this pull request Sep 8, 2023

[enterprise-4.14] [OSDOCS-7645]: Remove Note Regarding Inability to Delete Default Machine Pool, other MP updates #64542

Merged

bergerhoffer added branch/enterprise-4.13 branch/enterprise-4.14 labels Sep 18, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[OSDOCS-7645]: Remove Note Regarding Inability to Delete Default Machine Pool, other MP updates #64189

[OSDOCS-7645]: Remove Note Regarding Inability to Delete Default Machine Pool, other MP updates #64189

mletalie commented Aug 31, 2023 •

edited

Loading

ocpdocs-previewbot commented Aug 31, 2023 •

edited

Loading

bchandra-ocp commented Sep 6, 2023

xueli181114 Sep 7, 2023

mletalie Sep 8, 2023

xueli181114 Sep 7, 2023 •

edited

Loading

xueli181114 Sep 7, 2023

xueli181114 Sep 7, 2023

xueli181114 commented Sep 7, 2023

xueli181114 commented Sep 7, 2023

xueli181114 Sep 7, 2023

xueli181114 commented Sep 7, 2023

mletalie commented Sep 8, 2023

mletalie commented Sep 8, 2023

tmalove commented Sep 8, 2023

mletalie commented Sep 8, 2023

tmalove Sep 8, 2023

tmalove Sep 8, 2023

tmalove Sep 8, 2023

mletalie Sep 8, 2023 •

edited

Loading

tmalove Sep 8, 2023

tmalove Sep 8, 2023

tmalove Sep 8, 2023

tmalove commented Sep 8, 2023

mletalie commented Sep 8, 2023

EricPonvelle commented Sep 8, 2023

EricPonvelle commented Sep 8, 2023

openshift-cherrypick-robot commented Sep 8, 2023

openshift-cherrypick-robot commented Sep 8, 2023

		* You can add additional machine pools to an existing cluster.
		* You can add taints to any machine pool as long as there is one machine pool without any taints.

	The compute (also known as worker) node instance types, autoscaling options, and node counts that are available to you depend on your
	The compute (also known as worker) node instance types, autoscaling options, and node counts that are available depend on your

	For users of ROSA CLI `rosa` version 1.2.25 and prior versions, the machine pool created along with the cluster is identified as `Default`. For users of ROSA CLI `rosa` version 1.2.26 and beyond, the machine pool created along with the cluster is identified as `worker`.
	For users of ROSA CLI `rosa` version 1.2.25 and earlier versions, the machine pool created along with the cluster is identified as `Default`. For users of ROSA CLI `rosa` version 1.2.26 and later, the machine pool created along with the cluster is identified as `worker`.

	In a cluster created across multiple Availability Zones (AZ), the machine pools can be created across either all of the three AZs or any single AZ of your choice. The machine pool created by default at the time of cluster creation will be created with machines in all three AZs and scale in multiples of three.
	In a cluster that is created across multiple Availability Zones (AZ), the machine pools can be created across either all of the three AZs or any single AZ of your choice. The machine pool created by default at the time of cluster creation will be created with machines in all three AZs and scale in multiples of three.

[OSDOCS-7645]: Remove Note Regarding Inability to Delete Default Machine Pool, other MP updates #64189

[OSDOCS-7645]: Remove Note Regarding Inability to Delete Default Machine Pool, other MP updates #64189

Conversation

mletalie commented Aug 31, 2023 • edited Loading

ocpdocs-previewbot commented Aug 31, 2023 • edited Loading

bchandra-ocp commented Sep 6, 2023

Choose a reason for hiding this comment

Choose a reason for hiding this comment

xueli181114 Sep 7, 2023 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

xueli181114 commented Sep 7, 2023

xueli181114 commented Sep 7, 2023

Choose a reason for hiding this comment

xueli181114 commented Sep 7, 2023

mletalie commented Sep 8, 2023

mletalie commented Sep 8, 2023

tmalove commented Sep 8, 2023

mletalie commented Sep 8, 2023

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

mletalie Sep 8, 2023 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

tmalove commented Sep 8, 2023

mletalie commented Sep 8, 2023

EricPonvelle commented Sep 8, 2023

EricPonvelle commented Sep 8, 2023

openshift-cherrypick-robot commented Sep 8, 2023

openshift-cherrypick-robot commented Sep 8, 2023

mletalie commented Aug 31, 2023 •

edited

Loading

ocpdocs-previewbot commented Aug 31, 2023 •

edited

Loading

xueli181114 Sep 7, 2023 •

edited

Loading

mletalie Sep 8, 2023 •

edited

Loading