Skip to content

Feature: Add .devcontainer to standardize and automate the contributor environment #6581

@Ayushmore1214

Description

@Ayushmore1214

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:

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions