K8s Add proper namespace support #982

New Issue

zramsay · 2026-01-27T01:49:59Z

zramsay commented

2026-01-27 01:49:59 +00:00

tagging @srw for more details

srw commented

2026-02-18 18:42:47 +00:00

Essentially right now everything deploys into the default namespace. This is bad for several reasons.

At the very least SO should use a default dedicated namespace such as laconic with the ability to override it per deployment.

Further the web deployer also places everything in the default namespace, prob the initial fix here is to have the web deployer use a different default namespace laconic-apps and again with some ability to override per deployment/user namespaces.

The per user namespace is prob a heavier lift so we should implement the dedicated default namespaces first.

this is related to #992

Essentially right now everything deploys into the default namespace. This is bad for several reasons. At the very least SO should use a default dedicated namespace such as _laconic_ with the ability to override it per deployment. Further the web deployer also places everything in the default namespace, prob the initial fix here is to have the web deployer use a different default namespace _laconic-apps_ and again with some ability to override per deployment/user namespaces. The per user namespace is prob a heavier lift so we should implement the dedicated default namespaces first. this is related to https://git.vdb.to/cerc-io/stack-orchestrator/issues/992

srw referenced this issue

2026-02-18 18:47:58 +00:00

K8s Web Deployer Authorization #992

srw added the

Priority

Critical

label 2026-02-18 18:54:00 +00:00

srw changed title from ~~add proper namespacing to registry-driven k8s deployments~~ to K8s Add proper namespace support

2026-02-18 18:56:24 +00:00

srw added the

K8s

label 2026-02-18 19:03:56 +00:00