Open kaldvelski opened 12 months ago
diviner524
commented
12 months ago @kaldvelski By CC are you referring to Config Controller [1] ?
wanting to also create standard kubernetes resources at the same time in the namespace, e.g. a deployment that uses a bucket in GCS.
The above is allowed if you install Config Connector manually in ex: a regular GKE cluster.
[1] https://cloud.google.com/anthos-config-management/docs/concepts/config-controller-overview
kaldvelski
commented
12 months ago By CC I was referring to Config Connector, sorry for the confusion.
The above is allowed if you install Config Connector manually in ex: a regular GKE cluster.
Yes, so long as the kubernetes resources I want to create are in the same cluster as the operator is installed.
On Fri, 10 Nov 2023 at 22:29, Shuxian @.***> wrote:
@kaldvelski https://github.com/kaldvelski By CC are you referring to Config Controller [1] ?
wanting to also create standard kubernetes resources at the same time in the namespace, e.g. a deployment that uses a bucket in GCS.
The above is allowed if you install Config Connector manually in ex: a regular GKE cluster.
[1] https://cloud.google.com/anthos-config-management/docs/concepts/config-controller-overview
— Reply to this email directly, view it on GitHub https://github.com/GoogleCloudPlatform/k8s-config-connector/issues/1009#issuecomment-1806518714, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADSRLE4RWKN56OTGS6457PLYD2TFHAVCNFSM6AAAAAA7GVPZKKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBWGUYTQNZRGQ . You are receiving this because you were mentioned.Message ID: @.*** com>
Describe your question
I suspect I'm asking for the moon here, but my understanding of namespace mode is that you tell CC to listen to a namespace for any manifests to create GCP resources and then it takes care of it. Those resources can also reference different projects through the resource ref elements so the CC in one project can create resources in other projects.
However, from what I can tell the namespaces the CC can listen to have to be in the same cluster the cnrm-system is running.
My question stems from wanting to also create standard kubernetes resources at the same time in the namespace, e.g. a deployment that uses a bucket in GCS.
So to create both the deployment and the namespace, I'm limited to namespaces in the same cluster as CC.
So is there any way CC could listen to different clusters/different projects but the actual resource creation was performed by a central CC (e.g. an Anthos Config controller install)?
TIA