Tag Configuration

Learn how to apply settings via cloud provider tags.

Sedai automatically infers resource tags and Kubernetes annotations. These can be used to optionally define feature settings and compute action controls as well as for configuring Infrastructure as Code (IaC) changes.


Features

When you define settings via tags, Sedai considers it an override on settings a resource would otherwise inherit from its parent (such as a group, account, or Kubernetes cluster).

Tags must include the prefix settings.sedai.io followed by a period (.); for example:

settings.sedai.io.optimization.setting.configMode

For feature settings, the accepted keys of MANUAL and AUTO correspond to Recommend Mode and Autonomous Mode respectively.

For Kubernetes workloads, add the prefix settings.sedai.io followed by a slash (/); for example:

settings.sedai.io/optimization.setting.configMode

For feature settings, the accepted keys of MANUAL and AUTO correspond to Recommend Mode and Autonomous Mode respectively.

Optimization

Learn more about optimization settings.

Availability

Learn more about availability settings.

Release Intelligence

Learn more about release intelligence settings.

Compute Actions

The following settings only apply to AWS ECS/Fargate and Kubernetes stateless workloads.

Learn more about container and virtual machine compute actions.


IaC Configurations

Requires an IaC integration — learn more.

To apply IaC configurations, tags should be formatted with the following prefix:

configs:sedai.io:

For Kubernetes workloads, annotations should be formatted with the prefix:

configs.sedai.io/

For example:

If you use GitLabs, the variables_file_path does not need to include the project name.

For example, if the project name is A and the variables file C is at location A/B/C then you only need to include B/C as the value for variables_file_path.


AWS Lambda

AWS ECS

Kubernetes

Last updated