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):