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

build(deps): bump sigs.k8s.io/cluster-api-ipam-provider-in-cluster from 0.1.0-alpha.3 to 0.1.0 #142

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Mar 14, 2024

Bumps sigs.k8s.io/cluster-api-ipam-provider-in-cluster from 0.1.0-alpha.3 to 0.1.0.

Release notes

Sourced from sigs.k8s.io/cluster-api-ipam-provider-in-cluster's releases.

v0.1.0

This is the first proper release of the In Cluster IPAM Provider for Cluster API! Thanks to all the contributors that helped getting here, especially @​tylerschultz, @​christianang, @​flawedmatrix, @​p-strusiewiczsurmacki-mobica and @​rikatz.

⚠️ Breaking Changes since v0.1.0-alpha.3

  • The prefix for the deployment resources was changed from caip-in-cluster to capi-ipam-in-cluster to avoid confusing caip as a misspelling of capi (kubernetes-sigs/cluster-api-ipam-provider-in-cluster#214)
  • If you have a running deployment of the IPAM provider, you'll need to undeploy the provider first to avoid two instances running at the same time. The CRDs are not affected by this change, so you can keep them in place to avoid losing data.
  • The ClaimReconciler in pkg/ipamutil now passes a context.Context to the ReleaseAddress method of a ClaimHandler.

What's Changed since v0.1.0-rc.0

New Contributors

Full Changelog: kubernetes-sigs/cluster-api-ipam-provider-in-cluster@v0.1.0-rc.0...v0.1.0

v0.1.0-rc.0

⚠️ Breaking Changes

  • The prefix for the deployment resources was changed from caip-in-cluster to capi-ipam-in-cluster to avoid confusing caip as a misspelling of capi (kubernetes-sigs/cluster-api-ipam-provider-in-cluster#214) If you have a running deployment of the IPAM provider, you'll need to undeploy the provider first to avoid two instances running at the same time. The CRDs are not affected by this change, so you can keep them in place to avoid losing data.

Notable Changes & Fixes

  • Reserved addresses can now be allocated as well by setting spec.allocateReservedIPAddresses (#171)
  • Addresses can now be excluded using spec.excludeAddresses (#182)
  • The generic parts of the reconciliation logic were moved to the pkg/ipamutil package and can now be reused by future ipam providers (#203)
  • We now have official images available at registry.k8s.io/capi-ipam-ic/capi-ipam-in-cluster-controller

What's Changed

... (truncated)

Commits
  • d4352c0 Merge pull request #234 from kubernetes-sigs/fix/docker-push-manifest
  • a0e154d fix docker-push-manifest
  • f78cd24 Merge pull request #233 from kubernetes-sigs/dependabot/github_actions/golang...
  • 7e52309 🌱 Bump golangci/golangci-lint-action from 3.7.0 to 4.0.0
  • e4bcb06 Merge pull request #231 from kubernetes-sigs/fix/manifests-image-registry
  • c5624e5 Merge pull request #232 from rikatz/context-on-release
  • 84a9e94 ReleaseAddress should receive a context
  • 11e9866 Merge pull request #220 from zhanggbj/add_label
  • 8bd716c fix test
  • 83566d6 use registry.k8s.io image in release manifests
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot dependabot bot added dependencies Pull requests that update a dependency file go Pull requests that update Go code labels Mar 14, 2024
Bumps [sigs.k8s.io/cluster-api-ipam-provider-in-cluster](https://github.com/kubernetes-sigs/cluster-api-ipam-provider-in-cluster) from 0.1.0-alpha.3 to 0.1.0.
- [Release notes](https://github.com/kubernetes-sigs/cluster-api-ipam-provider-in-cluster/releases)
- [Commits](kubernetes-sigs/cluster-api-ipam-provider-in-cluster@v0.1.0-alpha.3...v0.1.0)

---
updated-dependencies:
- dependency-name: sigs.k8s.io/cluster-api-ipam-provider-in-cluster
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot force-pushed the dependabot/go_modules/sigs.k8s.io/cluster-api-ipam-provider-in-cluster-0.1.0 branch from b47c93b to 64a451b Compare March 14, 2024 10:43
Copy link
Contributor Author

dependabot bot commented on behalf of github Mar 21, 2024

Looks like sigs.k8s.io/cluster-api-ipam-provider-in-cluster is up-to-date now, so this is no longer needed.

@dependabot dependabot bot closed this Mar 21, 2024
@dependabot dependabot bot deleted the dependabot/go_modules/sigs.k8s.io/cluster-api-ipam-provider-in-cluster-0.1.0 branch March 21, 2024 14:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file go Pull requests that update Go code hold/do-not-merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant