Update FAQ
parent
b1d272b3bf
commit
19a2887a81
1 changed files with 5 additions and 1 deletions
6
FAQ.md
6
FAQ.md
|
@ -12,4 +12,8 @@ This homelab prioritizes security and adopts a more controlled approach to updat
|
||||||
|
|
||||||
## Why not just Kubernetes and Flux?
|
## Why not just Kubernetes and Flux?
|
||||||
|
|
||||||
Personally I don't think Kubernetes is needed in a Homelab, especially if you follow KISS like I do. I have spun up a few clusters and played around trying to switch all my services from Docker to Kubernetes, but I just always seem to migrate back to native Docker. Maybe one day, but I like my custom automation for CD now.
|
Personally I don't think Kubernetes is needed in a Homelab, especially if you follow KISS like I do. I have spun up a few clusters and played around trying to switch all my services from Docker to Kubernetes, but I just always seem to migrate back to native Docker. Maybe one day, but I like my custom automation for CD now.
|
||||||
|
|
||||||
|
## Why get release notes for Linuxserver images?
|
||||||
|
|
||||||
|
Linuxserver doesn't follow SemVer versioning which essentially breaks Renovate. I have so many of their packages that instead of writing custom Regex for each release title for Renovate to pull release notes, I just use the latest digest which Renovate detects no problem, then I have a n8n automation that grabs release notes from Github API and sends to PR for that specific release.
|
Reference in a new issue