-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to set
some boolean values on addon Helm configuration
#942
Comments
wjam
added a commit
to wjam/terraform-aws-eks-blueprints
that referenced
this issue
Sep 9, 2022
Certain values in a Kubernetes resource _must_ be a string and Kubernetes will complain if the value is of another type rather than automatically convert it into a string. An example of this problem would be the value `true` on a `Pod` label - in YAML, this must be `"true"` for Kubernetes to be satisfied. This adds a new optional attribute for the `set` element of all `*_helm_config` variables which allows the user to switch from the default behaviour of handling the `value` - `auto` - to `string`, which will force the `value` to be handled as text rather than a boolean or number. Fixes aws-ia#942
6 tasks
bryantbiggs
pushed a commit
that referenced
this issue
Sep 9, 2022
Certain values in a Kubernetes resource _must_ be a string and Kubernetes will complain if the value is of another type rather than automatically convert it into a string. An example of this problem would be the value `true` on a `Pod` label - in YAML, this must be `"true"` for Kubernetes to be satisfied. This adds a new optional attribute for the `set` element of all `*_helm_config` variables which allows the user to switch from the default behaviour of handling the `value` - `auto` - to `string`, which will force the `value` to be handled as text rather than a boolean or number. Fixes #942
allamand
pushed a commit
to allamand/terraform-aws-eks-blueprints
that referenced
this issue
Dec 15, 2022
Certain values in a Kubernetes resource _must_ be a string and Kubernetes will complain if the value is of another type rather than automatically convert it into a string. An example of this problem would be the value `true` on a `Pod` label - in YAML, this must be `"true"` for Kubernetes to be satisfied. This adds a new optional attribute for the `set` element of all `*_helm_config` variables which allows the user to switch from the default behaviour of handling the `value` - `auto` - to `string`, which will force the `value` to be handled as text rather than a boolean or number. Fixes aws-ia#942
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
I'm unable to set the
prometheus.io/scrape
flag on thecluster-autoscaler
deployment using thecluster_autoscaler
addon using theset
pattern. [1]Applying this Terraform:
Results in the error:
While I haven't tested other addons, I suspect they will suffer from the same problem.
[1] It would be possible to pass in the configuration using
values
rather thanset
, but this then hits aws-ia/terraform-aws-eks-blueprints-addons#38.Before you submit an issue, please perform the following first:
.terraform
directory (! ONLY if state is stored remotely, which hopefully you are following that best practice!):rm -rf .terraform/
terraform init
Versions
Reproduction Code [Required]
Steps to reproduce the behavior:
Provision an EKS cluster with cluster-autoscaler with the Helm config set to:
Expected behaviour
There should be a mechanism to set values that Kuebrnetes expect to be string but Go/HCL forces them to be a boolean or number.
Actual behaviour
Terraform fails to apply the changes and returns the error:
Terminal Output Screenshot(s)
Additional context
The text was updated successfully, but these errors were encountered: