You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
If an issue is assigned to the "modular-magician" user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned to "hashibot", a community member has claimed the issue already.
Terraform should do nothing for already created GKE clusters with Istio enabled, but auth not configured, or should support setting auth to AUTH_NONE.
Actual Behavior
Terraform wants to addons_config.0.istio_config.0.auth: "" => "AUTH_NONE" and after applying terraform again wants to make that change. After setting auth to AUTH_NONE, terraform complains that AUTH_NONE doesn't match AUTH_MUTUAL_TLS.
Steps to Reproduce
Create a GKE cluster with istio enabled, but no auth specified with google-beta provider 2.7.0.
Upgrade to google-beta provider 2.8.0
terraform apply
or
Create a GKE cluster with istio enabled and auth set to AUTH_NONE
terraform apply
Terraform complains that AUTH_NONE is not supported
This should be resolved in our next release, likely 2.9.0 next week. In the meantime, you can set lifecycle.ignore_changes on the field as the values are effectively equivalent.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!
ghost
locked and limited conversation to collaborators
Jul 11, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Community Note
Terraform Version
Terraform v0.11.13
Affected Resource(s)
Terraform Configuration Files
Debug Output
Panic Output
Expected Behavior
Terraform should do nothing for already created GKE clusters with Istio enabled, but auth not configured, or should support setting auth to AUTH_NONE.
Actual Behavior
Terraform wants to
addons_config.0.istio_config.0.auth: "" => "AUTH_NONE"
and after applying terraform again wants to make that change. After setting auth to AUTH_NONE, terraform complains that AUTH_NONE doesn't match AUTH_MUTUAL_TLS.Steps to Reproduce
terraform apply
or
terraform apply
Important Factoids
References
The text was updated successfully, but these errors were encountered: