Managed resources

Mon, 01 Jan 0001 00:00:00 +0000

This page is the authoritative list of what KCC actually owns in this repo. Counts are computed from the manifests in main and reflect what KCC reconciles, not what exists in GCP (drift is recovered by the controller on the next reconcile).

Note on secretmanager/ directories. Per the naming convention, directories are named after the Config Connector API group they correspond to. The secretmanager/ / secretsmanager/ directories are the one deliberate exception: they sit alongside the KCC API-group directories but contain External Secrets Operator resources (apiVersion: external-secrets.io/v1beta1 - SecretStore, ExternalSecret), not KCC resources. These resources bridge Postgres credentials from GCP Secret Manager into Kubernetes secrets and are reconciled by the ESO controller, not by KCC. They are called out explicitly in each project’s table below.

Operations

Mon, 01 Jan 0001 00:00:00 +0000

KCC is GitOps. The flow for every change is the same: edit YAML, open a PR, merge, ArgoCD syncs, KCC reconciles. There is no kubectl apply step and no gcloud step.

Repository rule. From AGENTS.md:

Do not ever try to kubectl apply Kubernetes manifests or use terraform apply directly. This repository follows GitOps principles. All changes to resources are handled via CI/CD. You may use the kustomize command to verify changes in kustomization overlays.

Config Connector on Infra Services

Managed resources

Operations