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
digitalocean_kubernetes_cluster: does not trigger k8s upgrade on version change #823
Labels
Comments
macno
added a commit
to authkeys/terraform-provider-digitalocean
that referenced
this issue
Apr 30, 2022
version check does not depend on node_pool changes
macno
added a commit
to authkeys/terraform-provider-digitalocean
that referenced
this issue
Apr 30, 2022
Also updated list of kubernetes versions
macno
added a commit
to authkeys/terraform-provider-digitalocean
that referenced
this issue
Apr 30, 2022
version check does not depend on node_pool changes
Looks like it could have been caught already by acceptance test. At least on a local env
Unfortunately I wasn't able to find any non-canceled run of the acceptance tests within CI env to confirm. #824 is a tentative PR that seem to solve the issue. |
macno
added a commit
to authkeys/terraform-provider-digitalocean
that referenced
this issue
May 5, 2022
Also updated list of kubernetes versions
macno
added a commit
to authkeys/terraform-provider-digitalocean
that referenced
this issue
May 5, 2022
version check does not depend on node_pool changes
macno
added a commit
to authkeys/terraform-provider-digitalocean
that referenced
this issue
May 5, 2022
version check does not depend on node_pool changes
scotchneat
pushed a commit
that referenced
this issue
May 11, 2022
The fix has been merged in main, this issue can be closed 🙏 |
Fixed via #824 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report
Describe the bug
We have k8s clusters with minor version pinned by terraform and DO automatic patch upgrades enabled.
When we wanted to trigger a k8s minor version upgrade, we noticed that several changes to the minor version in TF manifests did not trigger the cluster upgrade on DO. When that was the case, following
terraform apply
runs reported the change was still unapplied but never triggered the actual upgrade.After digging a bit, it turned out to be related to the control flow in
resourceDigitalOceanKubernetesClusterUpdate()
, where the execution never even reaches a cluster version check unless changes to the cluster'snode_pool
are detected as well. This does not seem to be the correct behaviour.This was a bit hard to figure out because we were pretty sure it worked in the past. When it happened to work, it was probably due to those being the first
terraform apply
runs after some automatic patch upgrade was performed by DO, yet triggering anode_pool
change that required the TF state to be synched.Is the above analysis correct?
Affected Resource(s)
Expected Behavior
A cluster upgrade should be triggered for any version change.
Actual Behavior
No upgrade is triggered if there is a version change but no contingent node_pool changes
The text was updated successfully, but these errors were encountered: