Env Config
The config.rb is where you can configure Kubes settings:
.kubes/config.rb
Kubes.configure do |config|
config.repo = "111111111111.dkr.ecr.us-west-2.amazonaws.com/demo"
config.logger.level = "info"
# auto-switching
# config.kubectl.context = "dev-cluster"
# config.kubectl.context_keep = false
end
Config Overrides
Env Overrides
You can override configs on a per-env basis with config/env files. Examples:
.kubes/config/env/dev.rb
Kubes.configure do |config|
config.repo = "222222222222.dkr.ecr.us-west-2.amazonaws.com/demo"
config.kubectl.context = "dev-cluster"
end
.kubes/config/env/prod.rb
Kubes.configure do |config|
config.repo = "333333333333.dkr.ecr.us-west-2.amazonaws.com/demo"
config.kubectl.context = "prod-cluster"
end
App Overrides
If KUBES_APP is set, app-scoped configs can be used to override settings further. Here are some with config/env/app example files:
.kubes/config/env/app1/dev.rb
Kubes.configure do |config|
config.repo = "222222222222.dkr.ecr.us-west-2.amazonaws.com/demo"
config.kubectl.context = "dev-cluster"
end
.kubes/config/env/app2/prod.rb
Kubes.configure do |config|
config.repo = "333333333333.dkr.ecr.us-west-2.amazonaws.com/demo"
config.kubectl.context = "prod-cluster"
end
This allows you to set specific app-level settings with:
KUBES_APP=app1 kubes deploy
KUBES_APP=app2 kubes deploy
Auto-Switching Context
Kubes supports automatically switching the kubectl context based on KUBES_ENV. Example:
KUBES_ENV=dev kubes deploy
KUBES_ENV=prod kubes deploy # can use different kubectl context
So dev and prod can use different kubectl contexts based on what is configured by:
Kubes.configure do |config|
config.kubectl.context = "..."
end
For more details refer to the Auto Context Docs.