Releases: kubernetes-sigs/cluster-api-provider-vsphere
v0.4.0
Version 0.4.0 (2019/07/26)
Once a patch release, 0.4.0 now represents a shift towards stability and the road to v1alphas two and three. This is CAPV 0.4.0.
Project changes
- SIG-VMware is no longer the owner of CAPV (#436)
- The CAPV API group has been renamed to
vsphere.cluster.k8s.io(#414) - Image stamping tools have been relocated (#446)
New features
- Image-based manifest generation (#412)
- Customizable sync period (#418)
- Customizable requeue period (#420)
- CAPI 1.7 (#440)
- New tooling for building/deploying releases (#426, #449)
- New troubleshooting guide (#466)
Enhancements
- Distroless manager image (#397)
- Safe initialization of a multi-node control plane (#387)
- Improved pre-submits (#422, #425, #441, kubernetes/test-infra#13363, kubernetes/test-infra#13509, kubernetes/test-infra#13489)
- Machine image updates (#404)
- Cloud provider credentials are now transmitted and stored securely (#419)
- Documentation updates (#398, #399, #428)
- Exit early during e2e test if build fails (#421)
Bug fixes
- Generating manifests behaved differently on macOS and Linux (#464)
- Generating manifests failed or created immutable contents (#453)
- Externally deleted VM is not recreated (#409, #411)
- Fix object patch logic (#393)
- Fixed missing RBAC permission (#432, #442)
- Fixed incorrect environment variable name for
VCENTER_USERNAME(#434) - Fixed unbound shell script variable in periodic e2e test (#443)
- Default VM folder logic has been corrected (#405, #406)
Known issues
Documentation
Please see the Getting Started guide!
Images
| Type | Link |
|---|---|
| Manager image | gcr.io/cluster-api-provider-vsphere/release/manager:v0.4.0 |
| Manifests image | gcr.io/cluster-api-provider-vsphere/release/manifests:v0.4.0 |
v0.4.0-beta.2
Version 0.4.0-beta.2 (2019/07/25)
Once a patch release, 0.4.0 now represents a shift towards stability and the road to v1alphas two and three. This is CAPV 0.4.0-beta.2.
Project changes
- SIG-VMware is no longer the owner of CAPV (#436)
- The CAPV API group has been renamed to
vsphere.cluster.k8s.io(#414) - Image stamping tools have been relocated (#446)
New features
- Image-based manifest generation (#412)
- Customizable sync period (#418)
- Customizable requeue period (#420)
- CAPI 1.7 (#440)
- New tooling for building/deploying releases (#426, #449)
Enhancements
- Distroless manager image (#397)
- Safe initialization of a multi-node control plane (#387)
- Improved pre-submits (#422, #425, #441, kubernetes/test-infra#13363, kubernetes/test-infra#13509, kubernetes/test-infra#13489)
- Machine image updates (#404)
- Cloud provider credentials are now transmitted and stored securely (#419)
- Documentation updates (#398, #399, #428)
- Exit early during e2e test if build fails (#421)
Bug fixes
- Generating manifests behaved differently on macOS and Linux (#464)
- Generating manifests failed or created immutable contents (#453)
- Externally deleted VM is not recreated (#409, #411)
- Fix object patch logic (#393)
- Fixed missing RBAC permission (#432, #442)
- Fixed incorrect environment variable name for
VCENTER_USERNAME(#434) - Fixed unbound shell script variable in periodic e2e test (#443)
- Default VM folder logic has been corrected (#405, #406)
Known issues
Documentation
Please see the Getting Started guide!
Images
| Type | Link |
|---|---|
| Manager image | gcr.io/cluster-api-provider-vsphere/release/manager:v0.4.0-beta.2 |
| Manifests image | gcr.io/cluster-api-provider-vsphere/release/manifests:v0.4.0-beta.2 |
v0.4.0-beta.1
Version 0.4.0-beta.1 (2019/07/24)
Note: This is primarily a patch release as v0.4.0-beta.0 had a breaking change (#453)
Once a patch release, 0.4.0 now represents a shift towards stability and the road to v1alphas two and three. This is CAPV 0.4.0-beta.1.
Project changes
- SIG-VMware is no longer the owner of CAPV (#436)
- The CAPV API group has been renamed to
vsphere.cluster.k8s.io(#414) - Image stamping tools have been relocated (#446)
New features
- Image-based manifest generation (#412)
- Customizable sync period (#418)
- Customizable requeue period (#420)
- CAPI 1.7 (#440)
- New tooling for building/deploying releases (#426, #449)
Enhancements
- Distroless manager image (#397)
- Safe initialization of a multi-node control plane (#387)
- Improved pre-submits (#422, #425, #441, kubernetes/test-infra#13363, kubernetes/test-infra#13509, kubernetes/test-infra#13489)
- Machine image updates (#404)
- Cloud provider credentials are now transmitted and stored securely (#419)
- Documentation updates (#398, #399, #428)
- Exit early during e2e test if build fails (#421)
Bug fixes
- Generating manifests failed or created immutable contents (#453)
- Externally deleted VM is not recreated (#409, #411)
- Fix object patch logic (#393)
- Fixed missing RBAC permission (#432, #442)
- Fixed incorrect environment variable name for
VCENTER_USERNAME(#434) - Fixed unbound shell script variable in periodic e2e test (#443)
- Default VM folder logic has been corrected (#405, #406)
Known issues
Documentation
Please see the Getting Started guide!
Images
| Type | Link |
|---|---|
| Manager image | gcr.io/cluster-api-provider-vsphere/release/manager:v0.4.0-beta.1 |
| Manifests image | gcr.io/cluster-api-provider-vsphere/release/manifests:v0.4.0-beta.1 |
v0.4.0-beta.0
Version 0.4.0-beta.0 (2019/07/24)
Once a patch release, 0.4.0 now represents a shift towards stability and the road to v1alphas two and three. This is CAPV 0.4.0-beta.0.
Project changes
- SIG-VMware is no longer the owner of CAPV (#436)
- The CAPV API group has been renamed to
vsphere.cluster.k8s.io(#414) - Image stamping tools have been relocated (#446)
New features
- Image-based manifest generation (#412)
- Customizable sync period (#418)
- Customizable requeue period (#420)
- CAPI 1.7 (#440)
- New tooling for building/deploying releases (#426, #449)
Enhancements
- Distroless manager image (#397)
- Safe initialization of a multi-node control plane (#387)
- Improved pre-submits (#422, #425, #441, kubernetes/test-infra#13363, kubernetes/test-infra#13509, kubernetes/test-infra#13489)
- Machine image updates (#404)
- Cloud provider credentials are now transmitted and stored securely (#419)
- Documentation updates (#398, #399, #428)
- Exit early during e2e test if build fails (#421)
Bug fixes
- Externally deleted VM is not recreated (#409, #411)
- Fix object patch logic (#393)
- Fixed missing RBAC permission (#432, #442)
- Fixed incorrect environment variable name for
VCENTER_USERNAME(#434) - Fixed unbound shell script variable in periodic e2e test (#443)
- Default VM folder logic has been corrected (#405, #406)
Known issues
Documentation
Please see the Getting Started guide!
Images
| Type | Link |
|---|---|
| Manager image | gcr.io/cluster-api-provider-vsphere/release/manager:v0.4.0-beta.0 |
| Manifests image | gcr.io/cluster-api-provider-vsphere/release/manifests:v0.4.0-beta.0 |
v0.4.0-alpha.0
Version 0.4.0-alpha.0 (2019/07/19)
Once a patch release, 0.4.0 now represents a shift towards stability and the road to v1alphas two and three. This is CAPV 0.4.0-alpha.0.
Project changes
- SIG-VMware is no longer the owner of CAPV (#436)
- The CAPV API group has been renamed to
vsphere.cluster.k8s.io(#414)
New features
- Image-based manifest generation (#412)
- Customizable sync period (#418)
- Customizable requeue period (#420)
- CAPI 1.7 (#440)
Enhancements
- Distroless manager image (#397)
- Safe initialization of a multi-node control plane (#387)
- Improved pre-submits (#422, #425, #441, kubernetes/test-infra#13363, kubernetes/test-infra#13509, kubernetes/test-infra#13489)
- Machine image updates (#404)
- Cloud provider credentials are now transmitted and stored securely (#419)
- Documentation updates (#398, #399, #428)
- Exit early during e2e test if build fails (#421)
Bug fixes
- Externally deleted VM is not recreated (#409, #411)
- Fix object patch logic (#393)
- Fixed missing RBAC permission (#432, #442)
- Fixed incorrect environment variable name for
VCENTER_USERNAME(#434) - Fixed unbound shell script variable in periodic e2e test (#443)
- Default VM folder logic has been corrected (#405, #406)
Documentation
Please see the Getting Started guide!
Images
| Type | Link |
|---|---|
| Manager image | gcr.io/cluster-api-provider-vsphere/release/manager:v0.4.0-alpha.0 |
| Manifests image | gcr.io/cluster-api-provider-vsphere/release/manifests:v0.4.0-alpha.0 |
v0.3.0
Version 0.3.0 (2019/06/27)
The motivation behind this release was bringing the Cluster API (CAPI) provider for vSphere (CAPV) into parity with other CAPI providers, such as the CAPI provider for AWS (CAPA). However, along the way it became clear that CAPV 0.3.0 was going to be more than that. This release represents a new beginning and sets the stage for future greatness.
Welcome to CAPV 0.3.0.
New Features
- Support for image-stamped machine images (#267)
- Support for custom kubeadm configurations (#307)
- Support for cloud-init v2 networking config, including IPv6 (#339)
- Reintroduced the in-tree cloud provider (#343, #357)
- Support for marking machines as in maintenance (#370)
- Support for IPv6 (#365)
- Support for custom CNI (#295, #296)
Enhancements
- Improved documentation (#308, #361)
- Improved
generate-yaml.sh(#367) clusterctlis now built as a statically linked binary (#381, #382)
Bug Fixes
- VMs orphaned by deletes during clone-in-progress (#235)
- Custom out dir not working when generating yaml (#350)
- Ignore link-local addresses from VMs (#356)
- Do not block deletes on missing kubeconfigs (#375)
Documentation
Please see the Getting Started guide!
Images
| Type | Link |
|---|---|
| Manager Image | gcr.io/cnx-cluster-api/vsphere-cluster-api-provider:0.3.0 |
Thank you
This release would not be possible without so many people! However, before that, there's one person in particular that deserves special recognition: @sflxn.
This release is possible because of the foundation built by Loc. While he may have moved onto other priorities, the work he accomplished will always be woven into the value provided by CAPV. Thank you Loc, you're a tough act to follow, but we'll try our best!
The rest of the crew that had a hand in creating CAPV 0.3.0 are (in no particular order):
v0.3.0-beta.0
Version 0.3.0-beta.0 (2019/06/26)
One step closer to 0.3.0!
New Features
- Support for image-stamped machine images (#267)
- Support for custom kubeadm configurations (#307)
- Support for cloud-init v2 networking config, including IPv6 (#339)
- Reintroduced the in-tree cloud provider (#343, #357)
- Support for marking machines as in maintenance (#370)
- Support for IPv6 (#365)
Enhancements
Bug Fixes
- VMs orphaned by deletes during clone-in-progress (#235)
- Custom out dir not working when generating yaml (#350)
- Ignore link-local addresses from VMs (#356)
Documentation
Please see the Getting Started guide!
Images
| Type | Link |
|---|---|
| Manager Image | gcr.io/cnx-cluster-api/vsphere-cluster-api-provider:0.3.0-beta.0 |
v0.3.0-alpha.1
Version 0.3.0-alpha.1 (2019/06/25)
One step closer to 0.3.0!
New Features
- Support for image-stamped machine images (#267)
- Support for custom kubeadm configurations (#307)
- Support for cloud-init v2 networking config, including IPv6 (#339)
- Reintroduced the in-tree cloud provider (#343, #357)
Bug Fixes
- VMs orphaned by deletes during clone-in-progress (#235)
- Custom out dir not working when generating yaml (#350)
- Ignore link-local addresses from VMs (#356)
Documentation
Please see the Getting Started guide!
Images
| Type | Link |
|---|---|
| Manager Image | gcr.io/cnx-cluster-api/vsphere-cluster-api-provider:0.3.0-alpha.1 |
Release 0.2.0
This release contains on-going bug fixes, updated tests, and documentation updates.
changes:
- Upgraded to kustomize v2 #205 and #224
- Noderef now added to machine objects #223
- Generate sample machineset.yaml for yaml makefile target #196
- Use different kubeadm.conf for various k8s versions #190
- Set the resync timeout to 2min for cluster and machine objects #179
fixes:
- Fixed node bootstrap script to support ubuntu bionic #239
- Temporary fix to support both kubernetes-cni 0.6.0 and 0.7.5 for varying k8s version #239
- Pinned Docker install to version 18.06.x to fix node bootstrap issue #230
- Fixed bug during cloning from template with snapshot and simultaneous disk expansion #212
- Fixed controller panic when using improper machineset yaml #192
tests:
- vcsim test added for the machine actuator create workflow #35
- integration tests for the OVA #134
docs:
- Updated docs for KIND bootstrapping
- Updated docs on how to use static IP in machine yaml