Repository navigation
feat(actions): run each project-domain in its own namespace - #8226
Draft
madiyar-wayve wants to merge 1 commit into
Draft
madiyar-wayve wants to merge 1 commit into
madiyar-wayve wants to merge 1 commit into
Conversation
madiyar-wayve
force-pushed
the
madiyar/namespace-mapping
branch
from
October 22, 2026 14:37
8048a4c to
37362b3
Compare
Add namespaceMapping (template, createNamespaces). Root TaskActions go to the namespace their project and domain map to; children follow the parent, and lookups fall back to the old namespace for in-flight runs. CreateRun rejects invalid names and fails runs whose namespace is missing. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Madiyar Aitzhanov <madiyar.aitzhanov@wayve.ai>
madiyar-wayve
force-pushed
the
madiyar/namespace-mapping
branch
from
October 22, 2026 16:24
37362b3 to
af78089
Compare
This branch has not been deployed
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
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.
Tracking issue
Related to #8051
Why are the changes needed?
v2 runs every TaskAction and its pods in one namespace. v1 could map each project-domain to its own namespace, which teams use to separate quotas, RBAC and secrets.
What changes were proposed in this pull request?
namespaceMappingconfig: a template with the v1 placeholders, e.g.{{ project }}-{{ domain }}, and createNamespaces (default true; set false when namespaces are provisioned outside Flyte). An empty template keeps today's behaviour.Not in this PR: copying secrets into mapped namespaces (the open question in the issue).
Should go in with #8215, which keeps plugin pod lookups within the job's namespace.
How was this patch tested?
Unit tests for the mapping, in-flight runs, missing namespaces and the same run name in two projects, plus an envtest integration test running a root and child action in a mapped namespace. Also running on our dev cluster with createNamespaces off.
Labels
Check all the applicable boxes
🤖 Generated with Claude Code