github metal3-io/cluster-api-provider-metal3 v0.5.2

latest releases: v1.1.1, v1.1.0, v0.5.5...
6 months ago

Changes since v0.5.1

⚠️ Breaking Changes

  • Add main branch references for CAPM3 (#337)

✨ New Features

  • Uplift bmo/api to v0.0.0-20211105090508-c38de6aabf99 (#373)
  • Add Remediation Controller to v1alpha5 (#283)
  • Uplift CAPI to v0.4.4 and align other deps with CAPI release-0.4 (#325)
  • Update Cert manager tilt module and fix tilt up for CAPM3 (#290)

🐛 Bug Fixes

  • Remove vulnerable import k8s.io/kubernetes v1.13.0 (#364)
  • Fix flaky issues on node reuse remediation tests (#365)
  • Add missing config folder entries to codegen (#346)
  • Use non root user with id (#351)
  • LACP bond mode IEEE fix (#268)
  • Remove unused folder and content from hack folder (#335)

📖 Documentation

  • Remove BMO vars from docs (#329)
  • Update readme with provider name (#327)

🌱 Others

  • E2e remediation test (#294)
  • Bump kind version to v0.11.1 (#353)
  • Parameterize BMH CRDs path for tilt setup (#348)
  • I'm not working directly on metal3 anymore. (#340)
  • Keep k8s var aligned across repo (#334)
  • Add an option to choose the cluster template from metal3-dev-env (#300)
  • Handle available state as alternative to Ready (#306)
  • e2e node_reuse test (#267)
  • Give an option for NOT deploying bmh resources (#350)
  • Change BMH ready state to available in node_reuse e2e test (#349)
  • Fix kustomize path for bmo controller (#344)
  • Fix CAPM3 name under GOPATH src (#330)

The image for this release is: v0.5.2
Baremetal-Operator and Ironic releases are capm3-v0.5.2
Thanks to all our contributors! 😊

Don't miss a new cluster-api-provider-metal3 release

NewReleases is sending notifications on new releases.