From 8ae7e79ae134e9663626a581e91a2d080766f513 Mon Sep 17 00:00:00 2001 From: enxebre Date: Fri, 29 May 2026 15:49:58 +0200 Subject: [PATCH] docs(cpo): fix HCCO deployment location in AGENTS.md HCCO runs in the control plane namespace on the management cluster, not in the guest cluster. It reconciles guest-side resources by talking to the guest API server, but the pod itself lives in the HCP namespace. Co-Authored-By: Claude Opus 4.6 --- control-plane-operator/AGENTS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/control-plane-operator/AGENTS.md b/control-plane-operator/AGENTS.md index 63f671d62e1..b26f1ed8403 100644 --- a/control-plane-operator/AGENTS.md +++ b/control-plane-operator/AGENTS.md @@ -21,7 +21,7 @@ See `support/controlplane-component/AGENTS.md` and `support/controlplane-compone ## HCCO (Hosted Cluster Config Operator) -HCCO is a **separate binary in the same image**, invoked as `control-plane-operator hosted-cluster-config-operator`. It runs as a Deployment **in the guest cluster** (not the management cluster), reconciling guest-side resources: `openshift-config/pull-secret`, node configuration, in-place upgrades, global pull secret, draining, etc. +HCCO is a **separate binary in the same image**, invoked as `control-plane-operator hosted-cluster-config-operator`. It runs as a Deployment in the control plane namespace, mainly reconciling guest-side resources: `openshift-config/pull-secret`, node configuration, in-place upgrades, global pull secret, draining, etc. HCCO controllers are in `hostedclusterconfigoperator/controllers/`. They do **not** use the v2 component framework today — this is a migration opportunity.