Skip to content

feat: update CAPI to v1.9.3 #1010

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

Merged
merged 5 commits into from
Feb 5, 2025
Merged

Conversation

dkoshkin
Copy link
Contributor

What problem does this PR solve?:
Update CAPI to the latest released version https://github.com/kubernetes-sigs/cluster-api/releases/tag/v1.9.3

Which issue(s) this PR fixes:
Fixes #

How Has This Been Tested?:

Special notes for your reviewer:

@jimmidyson
Copy link
Member

Can we do this as part of normal dependabot update PR #1006 ?

@SandhyaRavi2403
Copy link

Can we do this as part of normal dependabot update PR #1006 ?

I did try to update the changes @jimmidyson , couldn't push the changes

ERROR: Permission to nutanix-cloud-native/cluster-api-runtime-extensions-nutanix.git denied to SandhyaRavi2403.

@jimmidyson
Copy link
Member

Can we do this as part of normal dependabot update PR #1006 ?

I did try to update the changes @jimmidyson , couldn't push the changes

ERROR: Permission to nutanix-cloud-native/cluster-api-runtime-extensions-nutanix.git denied to SandhyaRavi2403.

@SandhyaRavi2403 I'll grant you permissions for next time - thanks for trying though! I've fixed this up now in the dependabot PR.

@dkoshkin
Copy link
Contributor Author

Can we do this as part of normal dependabot update PR #1006 ?

We could do that @jimmidyson, but do we really want to add all these other changes in that PR?
If this merges that AFAIK that dependabot PR would get rebased and only have the other changes after.

@jimmidyson
Copy link
Member

@dkoshkin OK let's do it this way around.

Why is this labelled as do not merge btw?

Copy link

@msdolbey msdolbey left a comment

Choose a reason for hiding this comment

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

👍
bumpity bump bump

@dkoshkin dkoshkin force-pushed the dkoshkin/feat-update-capi-to-v1.9.3 branch from 282bbe9 to 33b1bf4 Compare February 5, 2025 16:39
@jimmidyson jimmidyson merged commit f657b53 into main Feb 5, 2025
22 checks passed
@jimmidyson jimmidyson deleted the dkoshkin/feat-update-capi-to-v1.9.3 branch February 5, 2025 20:21
@github-actions github-actions bot mentioned this pull request Feb 5, 2025
dkoshkin added a commit that referenced this pull request Feb 5, 2025
🤖 I have created a release *beep* *boop*
---


## 0.26.0 (2025-02-05)

<!-- Release notes generated using configuration in .github/release.yaml
at main -->

## What's Changed
### Exciting New Features 🎉
* feat: adds new field for helm values input for cilium CNI by
@manoj-nutanix in
#1011
* feat: implementation for user defined configmap for cilium addon in
cluster creation by @manoj-nutanix in
#1033
* feat: update CAPI to v1.9.3 by @dkoshkin in
#1010
* feat: adds cluster's ownerref on cilium helm values source object by
@manoj-nutanix in
#1034
### Fixes 🔧
* fix: correctly copy Helm charts in init container by @dkoshkin in
#1018
* fix: Use mindthegap v1.17.0 for the helm-repository container by
@dlipovetsky in
#1024
* fix: use republished COSI controller image by @dkoshkin in
#1022
### Other Changes
* test: wait for COSI controller to be ready by @dkoshkin in
#1014
* refactor: Remove api module dependency from common module by
@jimmidyson in
#1019


**Full Changelog**:
v0.25.0...v0.26.0

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Dimitri Koshkin <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants