Advanced Variables

Basic variables layering should provides enough flexibility and is generally recommended. This page covers more advanced variables layering.

Advanced Layering Example

Here’s a more complex structure to demonstrate advanced layering.

├── base
│   └── deployment.rb
├── base.rb
├── dev.rb
├── prod.rb
└── web
    ├── deployment
    │   ├── dev.rb
    │   └── prod.rb
    └── deployment.rb

Concrete Example

Let’s look at a concrete web/deployment.yaml.

Here are the files that get layered when KUBES_ENV=dev:


And when KUBES_ENV=prod:


With advanced layering you can target a specific role and kind. So variables are only scoped to the resources you want.

Full Layering Table

Here’s a table showing the the full layering.

Folder/Pattern Example
base.rb base.rb
ENV.rb dev.rb
base/all.rb base/all.rb
base/all/ENV.rb base/all/dev.rb
base/KIND.rb base/deployment.rb
base/KIND/base.rb base/deployment/base.rb
base/KIND/ENV.rb base/deployment/dev.rb
ROLE/KIND.rb web/deployment.rb
ROLE/KIND/base.rb web/deployment/base.rb
ROLE/KIND/ENV.rb web/deployment/dev.rb


To help you get started quickly, you can generate starter variable code.

$ kubes new variable
      create  .kubes/variables/dev.rb


@example = "dev-value"

To create the prod variables, set KUBES_ENV=prod.

$ KUBES_ENV=prod kubes new variable
      create  .kubes/variables/prod.rb


@example = "prod-value"