Environments and namespaces
Every Garden project has one or more environments that are defined in the project level Garden configuration. Teams often define environments such as dev
, ci
, and prod
.
Each environment can be broken down into several "namespaces", and each Garden run operates in a specific namespace. (This is not to be confused with a Kubernetes Namespace resource, although you will often use the same name for your Garden namespace and your Kubernetes Namespace.)
To specify which Garden namespace to use, you can use either of the following:
Set a specific namespace using the CLI with the
--env
flag and prepending the namespace to the environment name using the following format--env <namespace>.<environment>
Using namespaces
You can use namespaces in various ways. Some common use cases include
Unique namespaces per developer: These are typically long-running and belong to the same environment (e.g.
dev
).Ephemeral namespaces for each CI run: These are deleted after the run completes.
Short-lived preview namespaces for each pull request: These are created when the pull request is opened, updated on every push, and deleted when the pull request is closed.
An opinionated guide on using namespaces
Below is an opinionated guide on configuring environments and namespaces and the corresponding config.
Add any of
dev
,ci
,preview
andprod
environments to your project.For namespaces in the
dev
environment, template in the user’s name.For namespaces in the
ci
environment, template in the build number from your CI runner.For namespaces in the
preview
environment, template in the PR number.Use a deterministic namespace for your
prod
environment.In the
kubernetes
provider config, setnamespace: ${environment.namespace}
. This ensures the Kubernetes namespace corresponds to the Garden namespace.Define your namespace names as variables so that you can, for example, re-use them in hostnames to ensure each instance of your project has a unique hostname.
The example configuration for this setup would look as follows:
This allows each developer to get a unique namespace and a unique hostname for each service. Some further notes:
The
dev-env-name
namespace will be something likemy-project-janedoe
so each developer has a unique namespace per project.
This serves as a good base for naming your hostnames and namespaces, but you can tweak it further to meet your specific needs. For example, at Garden we use a similar scheme for our CI and preview environments, but we use the PR or build number as a further unique identifier.
Last updated