... managed with Flux, Renovate and GitHub Actions 🤖
Explore the docs »
Report Bug · Request Feature
Table of Contents
This repo is in major disarray at the moment. I am currently refactoring my existing repo new_template_k3s.
This is a complete rework of my existing cluster, that I tend to learn Talos Linux with.
The cluster is managed by Renovate and flux for automation of most of the process. Except the actual deployment configurations.
- Talos Config
- Cilium CNI
- Return cluster to operational state
- Add Hajimari to the cluster 125
- Add monitoring 128
- Harden Kubernetes
- Add Kyverno for Kubernetes Policy Management
- Documentation
- Create README.md
- Document workflow (Github Pages/Cloudflare pages)
See the open issues for a full list of proposed features (and known issues).
Contributions are what make the open source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated.
If you have a suggestion that would make this better, please fork the repo and create a pull request. You can also simply open an issue with the tag "enhancement". Don't forget to give the project a star! Thanks again!
- Fork the Project
- Create your Feature Branch (
git checkout -b feature/AmazingFeature) - Commit your Changes (
git commit -m 'Add some AmazingFeature') - Push to the Branch (
git push origin feature/AmazingFeature) - Open a Pull Request
Distributed under the MIT License. See LICENSE.txt for more information.
A lot of my insperation came from multiple users part of the k8s-at-home community.
There is a lot of code jacking from: