k8s-dev-sandbox

You can create an isolated Kubernetes dev sandbox by running the create script, which maps your current branch to a unique namespace and port. This provisions a reproducible Odoo environment on demand.

Yes, you need both kubectl and helm installed, along with docker, git, and python3. You also require access to a running Kubernetes cluster to provision and manage the branch sandboxes.

Yes, the sandbox workflow supports both local and CI modes. You can automate creation, teardown, testing, and TTL extension for ephemeral Kubernetes environments within your automated pipelines.

You can manage sandbox lifecycles using subcommands for status, logs, and extend. The extend command specifically handles TTL annotations to prevent automatic teardown of active branch environments.

The best way to automate teardown is using the destroy and down subcommands. These scripts handle the complete destruction and cleanup of branch-specific namespaces and resources.

A unique namespace per branch ensures complete isolation for each feature. This prevents resource conflicts and allows multiple developers to test independent Odoo branches simultaneously.