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

Update vSphere CCM for Kubernetes 1.27 #12599

Merged
merged 2 commits into from
Aug 24, 2023

Conversation

xrstf
Copy link
Contributor

@xrstf xrstf commented Aug 24, 2023

What this PR does / why we need it:
I randomly saw in our verify job that we've used the same CCM version for 1.26, 1.27 and 1.28 (in #12593). To make a possible backport easier, I made this dedicated PR to just bump the vSphere CCM for k8s 1.27 to a 1.27.x release.

What type of PR is this?
/kind chore

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

Update vSphere CCM to 1.27.2 for Kubernetes 1.27 user clusters.

Documentation:

NONE

@kubermatic-bot kubermatic-bot added docs/none Denotes a PR that doesn't need documentation (changes). release-note Denotes a PR that will be considered when it comes time to generate release notes. kind/chore Updating grunt tasks etc; no production code changes. dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. approved Indicates a PR has been approved by an approver from all required OWNERS files. sig/cluster-management Denotes a PR or issue as being assigned to SIG Cluster Management. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Aug 24, 2023
@kubermatic-bot kubermatic-bot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Aug 24, 2023
@xrstf
Copy link
Contributor Author

xrstf commented Aug 24, 2023

/retest

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 kubermatic-bot added the lgtm Indicates that a PR is ready to be merged. label Aug 24, 2023
@kubermatic-bot
Copy link
Contributor

LGTM label has been added.

Git tree hash: ef6d078b1e544e40a0d8c0118662e8533fb9e74a

@kubermatic-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

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

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

@xmudrii
Copy link
Member

xmudrii commented Aug 24, 2023

/retest

2 similar comments
@xmudrii
Copy link
Member

xmudrii commented Aug 24, 2023

/retest

@xrstf
Copy link
Contributor Author

xrstf commented Aug 24, 2023

/retest

@kubermatic-bot kubermatic-bot merged commit e9296cc into kubermatic:main Aug 24, 2023
19 checks passed
@kubermatic-bot kubermatic-bot added this to the KKP 2.24 milestone Aug 24, 2023
@xrstf xrstf deleted the update-vsphere-ccm branch August 24, 2023 12:46
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. 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/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/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants