git clone https://github.com/g-crd/setup.git cd setup make build ./bin/setup version After installation, you must initialize the workspace. This creates the default directory structure and configuration file.
g.crd/setup version # Expected output: g.crd/setup v2.0.0 Fetch the latest release directly from the GitHub releases page:
g.crd/setup diff --show-managed-fields For automated pipelines, use the --dry-run and --output flags. g.crd/setup
curl -LO https://github.com/g-crd/setup/releases/download/v2.0.0/setup-linux-amd64 chmod +x setup-linux-amd64 sudo mv setup-linux-amd64 /usr/local/bin/g.crd/setup For developers who need the latest edge features:
- name: Deploy CRDs run: | g.crd/setup deploy \ --kubeconfig $ secrets.KUBECONFIG \ --dry-run=false \ --output summary git clone https://github
apiVersion: g.crd/v1 kind: SetupConfig metadata: name: production-setup spec: crdRoot: ./crd validation: enabled: true schemaPath: ./schemas deployment: strategy: apply # Options: apply, create, server-side namespace: crd-system hooks: preInstall: ./scripts/pre-check.sh postInstall: ./scripts/notify.sh Once configured, you can leverage these essential commands: 1. Scaffold a New CRD Generate a boilerplate CRD with a typed specification:
g.crd/setup can emit a standardized inventory file: curl -LO https://github
brew install g-crd/tap/setup Verify the installation: