A template for deploying a Kubernetes cluster with k3s or Talos
Since this is big overhaul I'd like to switched to calver release tags, lots of exciting changes but I'll list the most important.
ansible
and kubernetes
directories are completely templated out during task configure
. This change makes it easier to expose more options in the configuration files and paved the way for supporting addons.Thank you to everyone who helped support me and test changes thru out this refactoring. 🥰
Full Changelog: https://github.com/onedr0p/flux-cluster-template/compare/v5.4.0...v5.5.0
wait
and dependsOn
in flux ks and hr @onedr0p (#771)Full Changelog: https://github.com/onedr0p/flux-cluster-template/compare/v5.3.0...v5.4.0
Full Changelog: https://github.com/onedr0p/flux-cluster-template/compare/v5.2.0...v5.3.0
Full Changelog: https://github.com/onedr0p/flux-cluster-template/compare/v5.1.0...v5.2.0
This update brings in the ability for Flux to take over and manage the lifecycle of Cilium. Please review this PR to see what changes were needed to make this happen.
Full Changelog: https://github.com/onedr0p/flux-cluster-template/compare/v5.0.0...v5.1.0
Important changes:
kube-vip is now a core cluster component and not managed by Flux. Read thru the comments on this PR to discover why this change was needed to support Cilium.
Full Changelog: https://github.com/onedr0p/flux-cluster-template/compare/v4.2.0...v4.3.0
Full Changelog: https://github.com/onedr0p/flux-cluster-template/compare/v4.1.0...v4.2.0
Full Changelog: https://github.com/onedr0p/flux-cluster-template/compare/v4.0.2...v4.1.0