0.0.0-alpha.3
Pre-release
Pre-release
Note: This "release" is intended to be a snapshot of the repository just prior to the migration to CRDs.
clusterctl
is not included in this release as the binary from this repository longer supports the --provider
flag. Follow the Getting Started instructions to find the appropriate binary for your provider.
Changes since 0.0.0-alpha.2
- Breaking API Change: MachineSpec no longer includes MachineRoles (#405)
- Small improvement in the duration of clusterctl create cluster by polling for changes immediately (#331)
- Populate the associated node's UID in the machine.status.nodeRef field (#348)
- Fixed an issue where controller logs would all be proceeded by the following error output:
ERROR: logging before flag.Parse:
(#349) - MachineController can now delete nodes associated with master machines (#350)
- Added flag to
clusterctl delete cluster
to optionally override the provider components YAML associated with the cluster (#362) - Increase clusterclient timeout and retry intervals (#356)
- clusterctl now requires passing in addons when creating a cluster (#376)
- The cluster name in generate-yaml.sh is now a random string (#370)
- Fix an issue where clusteractuator.Delete(...) would never succeed if the firewall rules it is attempting to delete do not exist (#378)
- The Cluster Actuator is now passed a deep copy of the informer-provided cluster object instead of the informer-provided cluster object directly (#426)
- Add a
delete cluster
command toclusterctl
(#406) - clusterctl no longer supports --provider google. To create a cluster on Google Cloud Platform, please use clusterctl from https://github.com/kubernetes-sigs/cluster-api-provider-gcp (#438)
- Add "kubectl validate cluster" that validates cluster and machine objects (#298)
- clusterctl no longer supports --provider vsphere. To create a cluster on vsphere, please use clusterctl from https://github.com/kubernetes-sigs/cluster-api-provider-vsphere (#440)
- The command cluster create can now accept a kubeconfig file and launch on an existing k8s cluster. This allows us not to use minikube if we do not want to (#442)
- Missing rbac resources added to apiserverclusterapiservertemplate file (#462)
- [clusterctl] the
--cleanup-external-cluster
flag has been renamed to--cleanup-bootstrap-cluster
(#484) - Added node-conditions into api for MachineStatus (#483)
- Remove priority field from the APIService manifest to make it compatible with 1.11+ bootstrap clusters (#486)
- Support cluster and machine in multiple namespaces (#509)