gcp-config-connector skillA
gcp-config-connector is agent-read markdown (skill) from gke-labs/kube-agents: Authors Config Connector (KCC) manifests for Google Cloud resource changes and hands them to submit-suggestion as a pull request under the GitOps repository's clusters/<cluster>/provisioning/ path. Use when a request changes a GKE cluster or node pool (grow, autoscale, adopt), a Cloud SQL instance (add a read replica, resize), or a VPC firewall rule on an install whose GitOps repository holds Config Connector YAML. Decides create versus acquire read-only, validates every field with kubectl expla.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Config Connector (KCC) Authoring A Google Cloud change leaves this agent only one way: as a Config Connector manifest in the GitOps repository, reviewed by a human and applied by the customer's reconciler. This skill writes that manifest. It reads the cluster and the cloud project to decide what to write, validates the result against the CRDs the customer actually runs, and opens the pull request through **submit-suggestion**. Nothing here mutates a cluster or a project, and the command policy refuses the verbs that would. ## When to Use - **A GKE node pool or cluster change** — grow or shrink a pool, turn on autoscaling, change a release channel or maintenance window, adopt a cluster the repo does not yet describe. - **A Cloud SQL change** — add a read replica, change a tier, enable backups or high availability. - **A VPC firewall rule** — open or close a port, narrow a source range, disable a rule, turn on logging. - **Adopting a resource** that exists in Google Cloud but has no manifest in the repository (acquisition). ## When NOT to Use - **Kubernetes workloads** (Deployments, Services, NetworkPolicies): the `gke-manifest-generation` skill. …
Read the whole file at its exact version.
How to install
mdr add gke-labs/kube-agents/gcp-config-connector@git:20260911.a50cdc0mdr add gke-labs/kube-agents/gcp-config-connector@sha256:7972f0b0c33c719cPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_337o42jcuwklfz6r)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (14456 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
gke-labs/kube-agents · 64 stars · license Apache-2.0 · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_337o42jcuwklfz6r GET https://markdownregistry.com/api/v1/resolve?ref=gke-labs/kube-agents/gcp-config-connector GET https://markdownregistry.com/api/v1/blob/7972f0b0c33c719c579c64f0f4015c68bae63a880d9dab833cec03d92e5aadbd
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.