Skip to content
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

Investigate how updates should be handled when after an update, worker nodes have a higher version that control plane nodes #193

Open
Raaghavcodes opened this issue Nov 19, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@Raaghavcodes
Copy link
Contributor

Raaghavcodes commented Nov 19, 2024

Recent change has happened on the node update command to allow for patch releases. In these cases, the major.minor version does not change, but the patch version does. Something that we are currently enforcing is that the control plane nodes should all be updated before the worker nodes, so they should be running versions equal to or greater than what is running on worker nodes. However, a worker node could take in multiple patches and potentially be at a higher version than a control plane node in the cluster once the patch is applied. We should investigate what to do in this scenario.

Acceptance Criteria:

  1. Determine how this issue should be resolved

  2. Test and Verify this fix

Resources: Reach out to George, Paul, or Dan

@Raaghavcodes Raaghavcodes added the bug Something isn't working label Nov 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant