projectcalico
- 9 skills
- 0 followers
- 6 hours ago last updated
- ▌ Release Branch Cut · projectcalicoCut a release branch with the `release branch cut` command: create the branch, apply the version-reference edits, tag it, and push. Use this skill when cutting a release branch, when a cut failed partway and needs to resume, or when a version-bearing file has moved and the cut's edits need updating.
- ▌ Kind Cluster · projectcalicoCreate, deploy to, reload, and tear down a local kind cluster running Calico from locally-built images. Use when the user wants to bring up a test cluster, try a change on a real cluster, reload a rebuilt image onto kind, or destroy the cluster.
- ▌ Design Doc Edits · projectcalicoWrite or review an edit to a DESIGN.md — the altitude to write at, a worked example of an edit that was 34 lines too long, and the criteria for reviewing a design-doc diff. Use when about to add or change prose in any DESIGN.md or design/ sub-design, when reviewing a design-doc diff, or when compressing a design doc that has grown too large.
- ▌ Cherry Pick Release · projectcalicoCherry-pick a merged PR onto a Calico release branch using hack/cherry-pick-pull. Use when the user wants to backport a fix to a release-vX.YY branch or asks about the cherry-pick process.
- ▌ Operator Versioning · projectcalicoMap between Calico/enterprise versions and tigera/operator release branches, for the releases that predate the operator moving into this repo. Use this skill whenever you need to determine which operator branch corresponds to a Calico or enterprise release (e.g., "which operator branch is Calico v3.30?"), or the reverse (e.g., "what Calico version does release-v1.40 ship?"). Also use this skill whenever cherry-picking to operator release branches, creating cherry-pick PRs targeting release branches, or any task that requires knowing the operator↔Calico version relationship. Trigger even if the user doesn't explicitly ask about versioning — if the task involves targeting an operator release branch by Calico version, use this skill to find the right branch.
- ▌ Design Kubernetes API · projectcalicoDesigns a best-practice, extensible Kubernetes API resource. Use when designing new API resources for Calico.
- ▌ CI Reproduce On GCP Vm · projectcalicoReproduce CI test failures on a GCP VM matching the CI environment. Use when a CI job fails and the issue cannot be reproduced locally (e.g., kernel-dependent BPF verifier failures, kernel version-specific bugs).
- ▌ Operator API Standards · projectcalicoStandards, conventions, and dos/don'ts for adding or changing CRD types in the operator API (`operator/api/v1`). Use this skill whenever editing or creating files under `operator/api/v1/` (any *_types.go), adding/removing/renaming a CRD field, introducing a new Kind/CRD, adding kubebuilder validation or defaulting markers, or designing an overrides/configuration field. Trigger even if the user doesn't mention "standards" — any change to operator CRD types should follow these conventions.
- ▌ Implement Calico API Resource · projectcalicoImplements a new Calico API resource by plumbing it through all layers of the codebase. Use after API design is complete (see design-kubernetes-api skill).