From f766e01bb56c979adf50cea81227b4ff4c0f51dc Mon Sep 17 00:00:00 2001 From: Jeana Routh Date: Wed, 21 May 2025 13:58:54 -0400 Subject: [PATCH] use desc list for ts content --- modules/ts-capi-cli-reference-intended-objects.adoc | 11 ++++------- 1 file changed, 4 insertions(+), 7 deletions(-) diff --git a/modules/ts-capi-cli-reference-intended-objects.adoc b/modules/ts-capi-cli-reference-intended-objects.adoc index 4950dd7b32..a1e8431d6b 100644 --- a/modules/ts-capi-cli-reference-intended-objects.adoc +++ b/modules/ts-capi-cli-reference-intended-objects.adoc @@ -11,18 +11,16 @@ For clusters that use the Cluster API, {oc-first} commands prioritize Cluster AP This behavior impacts any `oc` command that acts upon any object that is represented in both the Cluster API and the Machine API. This explanation uses the `oc delete machine` command, which deletes a machine, as an example. -[discrete] -=== Cause +Cause:: When you run an `oc` command, `oc` communicates with the Kube API server to determine which objects to act upon. The Kube API server uses the first installed custom resource definition (CRD) it encounters alphabetically when an `oc` command is run. - ++ CRDs for Cluster API objects are in the `cluster.x-k8s.io` group, while CRDs for Machine API objects are in the `machine.openshift.io` group. Because the letter `c` precedes the letter `m` alphabetically, the Kube API server matches on the Cluster API object CRD. As a result, the `oc` command acts upon Cluster API objects. -[discrete] -=== Consequences +Consequence:: Due to this behavior, the following unintended outcomes can occur on a cluster that uses the Cluster API: @@ -30,8 +28,7 @@ Due to this behavior, the following unintended outcomes can occur on a cluster t * For namespaces that contain only Machine API objects, commands such as `oc get machine` return no results. -[discrete] -=== Workaround +Workaround:: You can ensure that `oc` commands act on the type of objects you intend by using the corresponding fully qualified name.