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

Jump to bottom

[release/v2.20] Add support for Kubernetes v1.22.17 and v1.23.15 #11555

Merged
merged 1 commit into from Dec 9, 2022
Merged

[release/v2.20] Add support for Kubernetes v1.22.17 and v1.23.15 #11555

merged 1 commit into from Dec 9, 2022

Conversation

embik
Copy link
Member

@embik embik commented Dec 9, 2022

What this PR does / why we need it:
Add support for Kubernetes patch releases from December 8. Manual cherry-pick of #11553.

Which issue(s) this PR fixes:

Fixes #

What type of PR is this?
/kind chore

Special notes for your reviewer:

Does this PR introduce a user-facing change? Then add your Release Note here:

Add support for Kubernetes v1.22.17 and v1.23.15

Documentation:

NONE

@embik
[release/v2.20] Add support for Kubernetes v1.22.17 and v1.23.15
592fbda 
Signed-off-by: Marvin Beckers <marvin@kubermatic.com>
@embik embik requested a review from xmudrii December 9, 2022 09:42
@kubermatic-bot kubermatic-bot added do-not-merge/cherry-pick-not-approved Indicates that a PR is not yet approved to merge into a release branch. release-note Denotes a PR that will be considered when it comes time to generate release notes. dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. kind/chore Updating grunt tasks etc; no production code changes. approved Indicates a PR has been approved by an approver from all required OWNERS files. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. sig/cluster-management Denotes a PR or issue as being assigned to SIG Cluster Management. labels Dec 9, 2022
@embik
Copy link
Member Author

embik commented Dec 9, 2022

/retest

1 similar comment
@embik
Copy link
Member Author

embik commented Dec 9, 2022

/retest

@pkprzekwas
Copy link
Contributor

/lgtm

@kubermatic-bot kubermatic-bot added the lgtm Indicates that a PR is ready to be merged. label Dec 9, 2022
@kubermatic-bot
Copy link
Contributor

LGTM label has been added.

Git tree hash: 994e993c486b852f35fd340baa3c5de49b0966ee

@pkprzekwas
Copy link
Contributor

/retest

1 similar comment
@embik
Copy link
Member Author

embik commented Dec 9, 2022

/retest

@embik embik added the cherry-pick-approved Indicates a PR has been approved by release managers. label Dec 9, 2022
@kubermatic-bot kubermatic-bot removed the do-not-merge/cherry-pick-not-approved Indicates that a PR is not yet approved to merge into a release branch. label Dec 9, 2022
xmudrii
xmudrii approved these changes Dec 9, 2022
View reviewed changes
Copy link
Member

@xmudrii xmudrii left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve

@kubermatic-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: embik, xmudrii

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@embik
Copy link
Member Author

embik commented Dec 9, 2022

/retest

1 similar comment
@embik
Copy link
Member Author

embik commented Dec 9, 2022

/retest

@kubermatic-bot kubermatic-bot merged commit d0e9322 into kubermatic:release/v2.20 Dec 9, 2022
@embik embik deleted the kubernetes-dec2022-release-v2.20 branch December 9, 2022 12:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@xmudrii xmudrii xmudrii approved these changes

Assignees

@pkprzekwas pkprzekwas

@xmudrii xmudrii

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cherry-pick-approved Indicates a PR has been approved by release managers. dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. kind/chore Updating grunt tasks etc; no production code changes. lgtm Indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. sig/cluster-management Denotes a PR or issue as being assigned to SIG Cluster Management. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
4 participants
@embik @pkprzekwas @kubermatic-bot @xmudrii