Release v0.12.0-rc.2
Pre-releaseWe are delighted to present version v0.12.0 of Tanzu Community Edition!
This release is focused on improving the local developer experience, spanning both the environment in which this experience happens, and the applications that this experience happens with. As such, most enhancements revolve around the unmanaged cluster
functionality and app toolkit
.
We look forward to you downloading, installing, using and opening issues in this repository if you encounter any problems or have ideas on building an even better experience.
For information about our user community resources, visit our project landing site.
A big thank you to everyone who contributed to the release!
Major Changes
Enhancing Local Cluster Creation
- Unmanaged clusters can now be created on minikube, in addition to Kind.
- Dynamic TKr (Tanzu Kubernetes release) resolution lets the TCE team ship updates to TKrs without "re-releasing" TCE, ensuring the validity/compatibility of those.
- Hooks to start and stop unmanaged clusters to save resources on the developer's machine.
Simplifying Developer Environment Setup
- New
--install-packages
flag enables packages (and collections of packages!) to be pre-installed in an unmanaged cluster during setup.
Enabling Tanzu Workload Creation
-
apps
Tanzu CLI Plugin (alpha release) gets installed as part of the TCE to interact with Tanzu workloads with commands such as create, get, tail and delete. -
New
kpack-dependencies
package sets up the resources (ClusterStack, ClusterBase and ClusterBuilder) to create images from source code in a git repo.
Other Notable Improvements
- Under-the-hood improvements to unmanaged clusters for robustness and stability (e.g. unit tests).
Package Updates
Here are some general enhancements to packages within Tanzu Community Edition:
- cartographer 0.3.0
- cert-manager 1.5.5, 1.6.3, 1.7.2, 1.8.0
- fluxcd-kustomize-controller 0.21.1
- kpack-dependencies 0.0.9
- local-path-storage version: 0.0.22
- whereabouts 0.5.1
Known Issues
- A race condition exists within TCE when creating CAPD clusters. In some cases, creation of a CAPD cluster will fail as several components of the cluster reach a state where they are waiting on each other to complete. To work around this issue, delete the cluster and try again.