turbot/kubernetes

GitHub
steampipe plugin install kubernetessteampipe plugin install kubernetes

Table: helm_value

Values in Helm-packed applications dictate the configuration of an application. Every Helm charts have an associated values.yaml file where the default configuration is defined. It is a source of content for the Values built-in object offered by Helm templates.

By design, applications can ship with default values.yaml file tuned for production deployments. Also, considering the multiple environments, it may have different configurations. To override the default value, it is not necessary to change the default values.yaml, but you can refer to the override value files from which it takes the configuration. For example:

Let's say you have two different environments for maintaining your app: dev and prod. And, you have a helm chart with 2 different set of values for your environments. For example:

connection "kubernetes" {
plugin = "kubernetes"
helm_rendered_charts = {
"my-app-dev" = {
chart_path = "~/charts/my-app"
values_file_paths = "~/value/file/for/dev.yaml"
}
"my-app-prod" = {
chart_path = "~/charts/my-app"
values_file_paths = "~/value/file/for/prod.yaml"
}
}
}

The table helm_value lists the values from the chart's default values.yaml file, as well as it lists the values from the files that are provided to override the default configuration.

Examples

List values configured in the default values.yaml file of a specific chart

select
path,
key_path,
value,
start_line,
start_column
from
helm_value
where
path = '~/charts/my-app/values.yaml'
order by
start_line;

List values from a specific override file

select
path,
key_path,
value,
start_line,
start_column
from
helm_value
where
path = '~/value/file/for/dev.yaml'
order by
start_line;

.inspect helm_value

Lists the values from chart's values.yaml file as well as the values listed in the configured values override files

NameTypeDescription
_ctxjsonbSteampipe context in JSON form, e.g. connection_name.
foot_commenttextSpecifies the comment following the node and before empty lines.
head_commenttextSpecifies the comment in the lines preceding the node and not separated by an empty line.
key_pathUSER-DEFINEDSpecifies full path of a key in YML file.
keysjsonbThe array representation of path of a key.
line_commenttextSpecifies the comment at the end of the line where the node is in.
pathtextName is the path-like name of the template.
pre_commentsjsonbSpecifies the comments added above a key.
start_columnbigintSpecifies the starting column of the value.
start_linebigintSpecifies the line number where the value is located.
valuetextSpecifies the value of the corresponding key.