-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Clarify supported version skew between masters, nodes, and clients #25087
Conversation
possible. | ||
|
||
Different components are expected to be compatible across different amounts of | ||
skew: cluster components (master and node components) should work across two |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"cluster components (master and node components) should work across two minor versions but should be at a version no newer than the master" is confusing because you are grouping the components together but then comparing them to each other. I think it would be clearer to root everything around the master version and then talk about compatibility / skew with that as a reference point.
@roberthbailey Good point; done. |
LGTM, please squash. I'll wait for @bgrant0607 to review before adding the label. |
Squashed; PTAL @bgrant0607. |
@ihmccreery Please assign PRs to whomever you'd like to review them. |
LGTM, thanks. |
GCE e2e build/test passed for commit e618e33. |
Automatic merge from submit-queue |
Per discussion on #22897.
cc @bgrant0607 @roberthbailey