feat(charts): control-plane namespace as the first tenant-isolation dial#28
Merged
Merged
Conversation
Make where a tenant's control-plane CRs (Platform/BudgetPolicy/ModelGateway/ AgentFleet/EvalSuite) land a value — `controlPlaneNamespace`, default `eks-agent-platform` — instead of the implicit helm release namespace. This is the "template you grow with" move: the shared-namespace default is a degenerate case of the scalable model, so a tenant graduates to a dedicated control-plane namespace (eap-tenant-<name>) by a value change, never a migration. It works because the Tenant CR is cluster-scoped (stable identity anchor) and the operator watches Platforms cluster-wide (placement is policy, not a constraint). Control-plane CRs stay in a platform-owned namespace, out of the tenant's workload namespace and reach — the privilege-escalation footgun of co-locating boundary definitions with the workloads they govern. Adds docs/architecture/tenant-isolation-tiers.md documenting the full trajectory (shared → dedicated CP ns → vcluster → dedicated cluster) and the no-migration promotion path. Verified: default renders to eks-agent-platform, override moves all CRs wholesale, lint clean.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Makes where a tenant's control-plane CRs (Platform/BudgetPolicy/ModelGateway/AgentFleet/EvalSuite) land a value —
controlPlaneNamespace, defaulteks-agent-platform— instead of the implicit helm release namespace.This is the "template you grow with" move: the shared-namespace default is a degenerate case of the scalable model, so a tenant graduates to a dedicated control-plane namespace (
eap-tenant-<name>) by a value change, never a migration. Works because theTenantCR is cluster-scoped (stable identity anchor) and the operator watchesPlatformcluster-wide (placement is policy, not a constraint). Control-plane CRs stay platform-owned — out of the tenant's workload namespace + reach.Adds
docs/architecture/tenant-isolation-tiers.mddocumenting the full trajectory (shared → dedicated CP ns → vcluster → dedicated cluster) and the no-migration promotion path. Verified: default →eks-agent-platform, override moves all CRs wholesale, lint clean.