v0.1.0
Container images are hosted on docker.io and can be pulled with the following command:
docker pull clastix/kamaji:v0.1.0
Enhancements
- Reflecting current version of the deployed Tenant Control Plane version rather then the specified one in the spec [#5]
- Moving to Docker Hub as main container registry [#8] and GH Actions workflow [#16]
- Support for Go 1.18 [#12]
- Dynamic management of Addons (kube-proxy, core-dns) [#7, #107]
- Helm Chart automatic release [#50]
- Using default values for the network profile section of Tenant Control Plane [#58]
- Remove API Machinery NewYAMLSerializer() deprecated function [#60
- Report Kamaji version and info at startup [#62]
- Adding konnectivity as Addons [#25, #93, #100, #140]
- Missing or wrong header in source files [#71]
- Utils for tenant kubernetes client [#72]
- Making optional spec.networkProfile.domain and renaming it to certSANs [#75]
- Missing handling of conflicts during reconciliation [#54]
- Set image pull policy to Always [#82]
- Provide logs for deletion of Tenant Control Planes [#83]
- Make container resources allocation configurable in Tenant Control Plane pods [#99]
- Support for additional extra arguments in TCP components [#103]
- Support for etcd storage class and size in Helm chart [#112, #114]
- Introduce support for MySQL and PostgreSQL as datastore [#22]
- DataStore API [#67, #133]
- Upgrade dependencies to Kuberentes 1.25 [#136]
- Dynamic kube-proxy addon version [#137]
- DataStore selection at the Tenant Control Plane level [#138]
- Enable topology spread constraints on tcp deployment [#142]
- Add the scale subresource in TenantControlPlane custom resource definition [#144]
Bug fix
- Tenant Control Plane kubelet configuration is not updated upon cgroup driver change [#79]
- Reconciliation of Kubeconfig upon TCP address change [#90]
- kube-proxy kubeconfig is missing address when dynamically allocation [#97]
- Update link to Capsule in README [#120]
- Wrong ServiceAccountIssuer string in kube-apiserver [#149]
- Documentation alignements [#162]
What's next
Check the just opened milestone and feel free to open a feature request!
Thanks
As the first minor release of Kamaji we're really emotional and we would like to thank all the contributors and early adopters: @bsctl, @ptx96 , @stek29, @davideimola, @alegrey91, @maxgio92, @mendrugory, @prometherion.