-
Notifications
You must be signed in to change notification settings - Fork 233
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
Use semver constraints on Kubernetes version for upper and lower bounds #1808
Conversation
Signed-off-by: Marvin Beckers <marvin@kubermatic.com>
Signed-off-by: Marvin Beckers <marvin@kubermatic.com>
Signed-off-by: Marvin Beckers <marvin@kubermatic.com>
/test pull-kubeone-lint |
Signed-off-by: Marvin Beckers <marvin@kubermatic.com>
Signed-off-by: Marvin Beckers <marvin@kubermatic.com>
Signed-off-by: Marvin Beckers <marvin@kubermatic.com>
/retest |
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.
/approve
admitting this to 1.4 release
LGTM label has been added. Git tree hash: 774d3e80b73f2e5f0da5085d6e7910241dfbc150
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: embik, kron4eg The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
I'm not sure, most likely no since that would be an unexpected novelty in 1.3. |
I agree with @kron4eg, it's unexpected in a patch release for 1.3. IMHO it should not be cherry-picked. It's "just" codifying the "contract" we already have in place through the support documentation. |
…ds (kubermatic#1808) * Use semver constraints on Kubernetes version for upper and lower bounds Signed-off-by: Marvin Beckers <marvin@kubermatic.com> * Fix linting issues Signed-off-by: Marvin Beckers <marvin@kubermatic.com> * Improve constraint usage and correctly append errors Signed-off-by: Marvin Beckers <marvin@kubermatic.com> * Use mustParseConstraint Signed-off-by: Marvin Beckers <marvin@kubermatic.com> * Fix test case Signed-off-by: Marvin Beckers <marvin@kubermatic.com> * Appease linter Signed-off-by: Marvin Beckers <marvin@kubermatic.com>
… and lower bounds (#1817) * Use semver constraints on Kubernetes version for upper and lower bounds (#1808) * Use semver constraints on Kubernetes version for upper and lower bounds Signed-off-by: Marvin Beckers <marvin@kubermatic.com> * Fix linting issues Signed-off-by: Marvin Beckers <marvin@kubermatic.com> * Improve constraint usage and correctly append errors Signed-off-by: Marvin Beckers <marvin@kubermatic.com> * Use mustParseConstraint Signed-off-by: Marvin Beckers <marvin@kubermatic.com> * Fix test case Signed-off-by: Marvin Beckers <marvin@kubermatic.com> * Appease linter Signed-off-by: Marvin Beckers <marvin@kubermatic.com> * Adjust version constraints to v1.3 branch Signed-off-by: Marvin Beckers <marvin@kubermatic.com>
What this PR does / why we need it:
This adds validation against two semver constraints that can easily be bumped from the top of the file when adding new Kubernetes versions.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #1807
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Signed-off-by: Marvin Beckers marvin@kubermatic.com