Releases: aenix-io/kubefarm
Releases · aenix-io/kubefarm
v0.13.4
What's Changed
- Use CronJob batch/v1 resource version if available by @ikeeip in aenix-io/kubernetes-in-kubernetes#11
- Fix incorrect pvc name by @xom4ek in aenix-io/kubernetes-in-kubernetes#13
New Contributors
- @xom4ek made their first contribution in aenix-io/kubernetes-in-kubernetes#13
Full Changelog: v0.13.3...v0.13.4
v0.13.3
- Fix kube-controller-manager template error when networking.podSubnet is set in values aenix-io/kubernetes-in-kubernetes#10
- Kubernetes version v1.22.4
- etcd version 3.5.1
- Fix old kubelet version
- Fix copying kaniko directory from the build context
v0.13.0
v0.12.0
v0.11.0
v0.10.2
v0.10.0
v0.9.2
v0.9.0
Changes:
- Upgrade Kubernetes v1.20.2
- Upgrade Konnectivity v0.0.14
- Upgrade etcd v3.4.13-0
Fixes:
- Allow token generator to access pki admin data
Breaking changes:
- Helm parameters
.PullPolicy
and.PullSecrets
are renamed to.pullPolicy
and.pullSecrets
v0.8.0
-
Breaking change: The sa secret type changed and now fully generated by cert-manager
To update existing clusters, please run the following before the update:
RELEASE_NAME=foo RELEASE_NAMESPACE=foo kubectl -n ${RELEASE_NAMESPACE} get secret ${RELEASE_NAME}-kubernetes-pki-sa -o yaml >/tmp/sa.yaml sed -i -e 's/sa.pub/tls.crt/' -e 's/sa.key/tls.key/' -e 's|^type: Opaque|type: kubernetes.io/tls|' /tmp/sa.yaml kubectl delete -f /tmp/sa.yaml kubectl apply -f /tmp/sa.yaml
Most likely you will have to recreate keys for all service accounts and restart the associated workload any way:
kubectl get secret --all-namespaces | grep 'kubernetes.io/service-account-token' | awk '{ print "kubectl delete secret -n " $1 " " $2}' | sh -x
-
All client certificates used in kubeconfigs now generated by cert-manager
-
ServiceAccount and roles to create secrets and configmaps in admin-cluster now fully removed
-
Add server cerificates for controller-manager and scheduler (for the healthcheck and metrics collection)
-
apiserver secrtificate renamed to apiserver-server