We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Contrary to the kubernetes defaults, the kubernetes terraform provider hardcodes automount_service_account_token to false:
false
hashicorp/terraform-provider-kubernetes#38
However, this leads to non-working resources being created, as they rely on that defaulting to true.
k2tf should add
automount_service_account_token = true
The text was updated successfully, but these errors were encountered:
thank you @flokli i spent two days trying to figure out what was wrong with my deployment and my daemonset 😭
Sorry, something went wrong.
@meroupatate sorry to hear. If there really needs to be this deviation from the defaults, it should really be documented loudly…
It seems terraform-provider-kubernetes pedalled back, and switched over to use the k8s defaults again: hashicorp/terraform-provider-kubernetes#1054
I think this is resolved upstream (as pointed out above by @flokli ), so going to close this.
No branches or pull requests
Contrary to the kubernetes defaults, the kubernetes terraform provider hardcodes automount_service_account_token to
false
:hashicorp/terraform-provider-kubernetes#38
However, this leads to non-working resources being created, as they rely on that defaulting to true.
k2tf should add
The text was updated successfully, but these errors were encountered: