Modularize Kubenix deployments #92

Open
opened 2024-07-13 08:57:26 +00:00 by pim · 1 comment
Owner

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:

nix run .#kubenix.x86_64-linux.immich

We should probably still retain the option to deploy everything, maybe like:

nix run .#kubenix.x86_64-linux.all
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: ``` nix run .#kubenix.x86_64-linux.immich ``` We should probably still retain the option to deploy everything, maybe like: ``` nix run .#kubenix.x86_64-linux.all ```
Author
Owner

Much is moved to separate namespaces, but some "core" deployments (metallb, longhorn etc.) is still in the default namespace.

Much is moved to separate namespaces, but some "core" deployments (metallb, longhorn etc.) is still in the default namespace.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: home/nixos-servers#92
No description provided.