Feature: Add .devcontainer to standardize and automate the contributor environment
Open
@Ayushmore1214 is already working on this.
Since Apr 8, 2026.
- Dominant language
- Go
- Stars
- 1.4k
- Forks
- 364
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 84
Description
Hey team! I saw the contributing docs mention adding Codespaces support. so I wanted to open an issue to track adding a .devcontainer to the repo. Right now, getting a local environment running means manually installing Go, Node, kubectl, setting up a local Docker registry, and fetching dependencies. Implementing a standardized .devcontainer with Docker-in-Docker (DinD) would let contributors instantly spin up the project in VS Code or GitHub Codespaces. They could immediately run make up/local-cluster
Let me know your thoughts.
What would you like to be added:
Why is this needed:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.