openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-06 06:46:26 +01:00
Code Issues Releases Activity

Merge pull request #93645 from jeana-redhat/reformat-CAPI-ts-proc

Browse Source 
use desc list for ts content
This commit is contained in:
Jeana Routh
2025-05-21 14:49:33 -04:00
committed by GitHub
parent b18daad371 f766e01bb5
commit 32cf11fcef
1 changed files with 4 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
modules/ts-capi-cli-reference-intended-objects.adoc
View File

@@ -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.