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
I took a look at this and don't have a great solution- we test upgrading between release channels, but it's an impossible transition right now. The STABLE and REGULAR channel are 2 minor versions apart, which is an impossible transition (you can only upgrade a single minor version at a time).
This doesn't have much to do with release channels- we actually turn the feature off to perform the transition. We could consider handling big version jumps natively in the provider by selecting appropriate intermediary GKE versions, but that's likely undesirable. The logic would be brittle, and TF choosing arbitrary (temporary) minor versions could be an anti-feature. Instead, we could consider removing the update mechanics from the test- unfortunate, since it stops testing a complex interaction- but will make the test pass again.
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
Aug 21, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
No description provided.
The text was updated successfully, but these errors were encountered: