-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
min_master_version and release_channel conflicting #383
Comments
Can you share the Terraform config you used? |
The relevant bits, slightly edited:
If you need everything, I can pull it together and scrub it. |
Thanks, I think I see the issue. If |
As another data point, since this is a development cluster that I'm experimenting with I'm constantly tearing it down, and building it back again and I hit the same problem:
|
Also experiencing this issue... How do we set it to null? I've tried setting |
Same for me. I think that Google made a change recently on that part because it was working few days ago. |
I'm facing the same issue. Version
|
I want to use the
release_channel
feature in 6.1.1, specifically in thebeta-private-cluster
module, however, skimming the code I'm pretty sure this applies to any of thebeta_*
modules. In this specific case, I'm using therelease_channel
and specifying aregion
with 3zones
, resulting in amaster_version
(as of last Thursday) ofThe cluster deployed just fine. However now when I trying to apply an unrelated change, I'm seeing
Trying to apply the change to the cluster results in the following error:
I initially tried to use
ignore_changes
in my module invocation to ignoremin_master_version
, and immediately ran into the fact this can't currently be done.The text was updated successfully, but these errors were encountered: