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
tocapi-ipam-in-cluster
to avoid confusingcaip
as a misspelling of capi (#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
inpkg/ipamutil
now passes acontext.Context
to theReleaseAddress
method of aClaimHandler
.
What's Changed since v0.1.0-rc.0
- Ensure IPAddress has a ClusterName label as CAPI resources by @zhanggbj in #220
⚠️ ReleaseAddress should receive a context by @rikatz in #232- 🌱 use registry.k8s.io image in release manifests by @schrej in #231
- 🌱 Bump golangci/golangci-lint-action from 3.7.0 to 4.0.0 by @dependabot in #233
New Contributors
Full Changelog: v0.1.0-rc.0...v0.1.0