Releases: metal-stack/cluster-api-provider-metal-stack
v0.8.0-rc.0
v0.7.0
v0.6.3
General Changes
- test(e2e): fix picking default kubeconfig accidentially (#117) @vknabel
- build: build kustomize (#116) @vknabel
- Add
--namespaceflag to watch only specific namespace if necessary. (#114) @Gerrit91 - Cluster K8s Upgrade (#105) @simcod
- fix(machine): give load balancers some time after control plane machine deletion (#115) @vknabel
- test: reference new templates (#113) @vknabel
- Use calico flavor for tests (#112) @simcod
- Add first flavors for cluster templates. (#110) @Gerrit91
- Add Calico
HelmChartProxyand metal-ccmClusterResourceSetsample. (#106) @Gerrit91 - test: teardown and slight refactorings (#104) @vknabel
- docs: updated readme for current status (#109) @vknabel
- Integration test for HA cluster setup (#103) @simcod
- Integration Tests:
clusterctl move(#102) @simcod
v0.6.2
v0.6.1
v0.6.0
General Changes
- Change Cluster ID to be a valid label value (#90) @vknabel
- Metallb BGPPeers are generated for each node and don't have to be created manually (#91) @vknabel
- Bump the metadata.yaml (#88) @vknabel
Required Actions
Existing clusters using cluster-provider-metal-stack need to manually update the tags of all cluster associated entities in metal-stack. Before upgrading set Cluster.spec.paused to true. Then upgrade your metal-stack provider and manually patch every metal-stack machine: replace any / with a . within the value of the tags metal-stack.infrastructure.cluster.x-k8s.io/machine-resource and metal-stack.infrastructure.cluster.x-k8s.io/cluster-resource by using metalctl machine edit $MACHINE_ID. Now set Cluster.spec.paused to false.
Make sure the metal-ccm is at least v0.9.7 and its METAL_CLUSTER_ID env is set to ${NAMESPACE}.${CLUSTER_NAME}.
v0.5.0
General Changes
- Use KubeVIP Load Balancing for Control Planes. (#87) @vknabel
- Update mini-lab (#84) @vknabel
- chore(deps): upgrade golangci-lint (#83) @vknabel
- chore(lab): bump clusterctl (#80) @vknabel
- fix: deletion of untouched machines (#81) @vknabel
Breaking Change
The new Cluster API cluster template now requires CONTROL_PLANE_IP to be set. The Control Plane IP will no longer be attached automatically to control plane machines.
Rewrite your Cluster API cluster definition to include KubeVIP or alternatives. The images must replace METAL_MACHINE_ASN with the machine ASN number in the KubeVIP static pod configuration to be compatible with the default template.