Skip to content

My home server cluster, managed by flux and defined as code here

License

Notifications You must be signed in to change notification settings

snoopy82481/home_cluster

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

6,525 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation


home_cluster

My home Kubernetes cluster

... managed with Flux, Renovate, and GitHub Actions 🤖

GitHub License   Talos   kubernetes   Flux   GitHub last commit   Renovate

Age-Days   Uptime-Days   Node-Count   Pod-Count   CPU-Usage   Memory-Usage   Alerts

Table of Contents
  1. About The Project
  2. Roadmap
  3. Contributing
  4. License
  5. Acknowledgments

About The Project

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.

(back to top)

🛠️ Built With

Kubernetes logo   Flux logo   VS-Code logo   Talos Logo   Cilium Logo  

(back to top)

Roadmap

  • 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).

(back to top)

Contributing

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!

  1. Fork the Project
  2. Create your Feature Branch (git checkout -b feature/AmazingFeature)
  3. Commit your Changes (git commit -m 'Add some AmazingFeature')
  4. Push to the Branch (git push origin feature/AmazingFeature)
  5. Open a Pull Request

(back to top)

License

Distributed under the MIT License. See LICENSE.txt for more information.

(back to top)

Acknowledgments

A lot of my insperation came from multiple users part of the k8s-at-home community.
There is a lot of code jacking from:

(back to top)

About

My home server cluster, managed by flux and defined as code here

Topics

Resources

License

Stars

Watchers

Forks

Contributors 6