Modularize Kubenix deployments #92
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: home/nixos-servers#92
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We got a massive amount of Kubernetes resources deployed currently. When using Kubenix' default deployment tools, each resource is deployed/updated with every run. This takes a long time and is frankly very wasteful. We should have the option to deploy only the application we changed. To this end, we should first put deployments (media stack, nextcloud, immich, etc.) into separate Kubernetes namespaces. Then, make a Kubenix deployment program for each deployment so we can do:
We should probably still retain the option to deploy everything, maybe like:
Much is moved to separate namespaces, but some "core" deployments (metallb, longhorn etc.) is still in the default namespace.