Contribute

Set up the pinned development environment, run the required checks, and keep code, contracts, and docs in step.

Build the provider from source and run it against a local OpenBao and Kind cluster with one command, for development and evaluation.

The strict typed Go rules, package boundaries, and lint, ast-grep, and Semgrep gates every pull request must pass.

What the test suite must prove, the test layers that prove it, the install regression check, and how to run longer fuzz campaigns.

Every end-to-end lane and its make target, how labels and the suite manifest select lanes, the environment variables, and where reports land.

How versions are pinned, what runs on pull requests, main, and nightly, and how the release workflows build, verify, sign, and publish artifacts.

Captured kubeadm cold-start and warmup results, what they show about decrypt load, and why the provider keeps the direct decrypt path.

The writing, structure, verification, and presentation standard for the published documentation.

How the Hugo documentation site is organized, built, checked, and published.