Sha256: e78f7855571c76031a6e6e8305db5edf46aaada92e8e2dc121c2f30210e4269f
Contents?: true
Size: 1.76 KB
Versions: 11
Compression:
Stored size: 1.76 KB
Contents
---
title: Multiple Enviroments with Layering
nav_text: Multiple Enviroments
categories: patterns
---
You can use Kubes to easily create multiple enviroments with the same YAML configs. This is thanks to [Kubes Layering]({% link _docs/layering.md %}). We'll walk through an example to help understand how it works.
## Creating Multiple Enviroments
To create multiple enviroments like dev and prod just change KUBES_ENV. Example:
KUBES_ENV=dev kubes deploy
KUBES_ENV=prod kubes deploy
Different env files will be layered and merged to produce YAML files specific to each environment.
## Project Structure
Here's an example structure, so we can understand how layering works to create multiple enviroments.
.kubes/resources/
├── base
│ ├── all.yaml
│ └── deployment.yaml
└── web
├── deployment
│ ├── dev.yaml
│ └── prod.yaml
├── deployment.yaml
└── service.yaml
## Concrete Example
Let's look at a concrete web/deployment.yaml.
Here are the files that get layered when `KUBES_ENV=dev`:
.kubes/resources/base/all.yaml
.kubes/resources/base/deployment.yaml
.kubes/resources/web/deployment.yaml
.kubes/resources/web/deployment/dev.yaml
And when `KUBES_ENV=prod`:
.kubes/resources/base/all.yaml
.kubes/resources/base/deployment.yaml
.kubes/resources/web/deployment.yaml
.kubes/resources/web/deployment/prod.yaml
Layering allows us to have common settings that are processed before your main `.kubes/resources/web/deployment.yaml` YAML manifest. And then add **environment** specific YAML files that get merged.
## Variables and Helpers
Additional, you can use variables and helpers to provide environment specific values.
Version data entries
11 entries across 11 versions & 1 rubygems