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

[release/v1.5] Update kubernetes-cni to v1.2.0 and cri-tools to v1.26.0 #2608

Merged
merged 3 commits into from
Jan 26, 2023

Conversation

xmudrii
Copy link
Member

@xmudrii xmudrii commented Jan 26, 2023

What this PR does / why we need it:

This is a manual backport of #2606 to the release/v1.5 branch.

Which issue(s) this PR fixes:
xref #2607

What type of PR is this?
/kind feature

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

Update kubernetes-cni to v1.2.0 and cri-tools to v1.26.0

Documentation:

NONE

Signed-off-by: Marko Mudrinić <mudrinic.mare@gmail.com>
Signed-off-by: Marko Mudrinić <mudrinic.mare@gmail.com>
Signed-off-by: Marko Mudrinić <mudrinic.mare@gmail.com>
@kubermatic-bot kubermatic-bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. docs/none Denotes a PR that doesn't need documentation (changes). kind/feature Categorizes issue or PR as related to a new feature. dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. labels Jan 26, 2023
@kubermatic-bot
Copy link
Contributor

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@kubermatic-bot kubermatic-bot added the do-not-merge/code-freeze Indicates that a PR should not merge because it has not been approved for code freeze yet. label Jan 26, 2023
@xmudrii xmudrii changed the base branch from main to release/v1.5 January 26, 2023 10:28
@kubermatic-bot kubermatic-bot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Jan 26, 2023
@kron4eg
Copy link
Member

kron4eg commented Jan 26, 2023

/lgtm
/approve

@kubermatic-bot kubermatic-bot added the lgtm Indicates that a PR is ready to be merged. label Jan 26, 2023
@kubermatic-bot
Copy link
Contributor

LGTM label has been added.

Git tree hash: 501e0d26bcd27a73e5b28bc535279f8556d63705

@kubermatic-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubermatic-bot kubermatic-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 26, 2023
@xmudrii xmudrii added the code-freeze-approved Indicates a PR has been approved by release managers during code freeze. label Jan 26, 2023
@kubermatic-bot kubermatic-bot removed the do-not-merge/code-freeze Indicates that a PR should not merge because it has not been approved for code freeze yet. label Jan 26, 2023
@xmudrii xmudrii marked this pull request as ready for review January 26, 2023 10:40
@kubermatic-bot kubermatic-bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 26, 2023
@kubermatic-bot kubermatic-bot merged commit dfa6dd5 into release/v1.5 Jan 26, 2023
@kubermatic-bot kubermatic-bot deleted the cni-cri-tools-updates branch January 26, 2023 11:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. code-freeze-approved Indicates a PR has been approved by release managers during code freeze. dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. docs/none Denotes a PR that doesn't need documentation (changes). kind/feature Categorizes issue or PR as related to a new feature. 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. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants