Skip to content

Introduce support for generating cross-namespace artifacts - #387

Merged
matheuscscp merged 1 commit into
mainfrom
cross-ns-artifacts
Oct 2, 2026
Merged

matheuscscp merged 1 commit into
mainfrom
cross-ns-artifacts

Conversation

@matheuscscp

Copy link
Copy Markdown
Member

Closes: #354

Implementation is according to the issue description. RBAC is the boundary, so to restrict cross-namespace artifacts --default-service-account must be set and the final ServiceAccount used by an ArtifactGenerator must have the permissions needed for reconciling the desired output artifacts.

@matheuscscp matheuscscp added enhancement New feature or request area/api API related issues and pull requests area/generator Artifact generation related issues and pull requests labels Oct 1, 2026
@matheuscscp
matheuscscp force-pushed the cross-ns-artifacts branch 2 times, most recently from 6713226 to 863f28d Compare October 1, 2026 10:43
Comment thread internal/controller/artifactgenerator_controller.go

@stefanprodan stefanprodan left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Comment thread docs/spec/v1beta1/artifactgenerators.md Outdated
Signed-off-by: Matheus Pimenta <matheuscscp@gmail.com>
@matheuscscp
matheuscscp merged commit 38c337c into main Oct 2, 2026
5 checks passed
@matheuscscp
matheuscscp deleted the cross-ns-artifacts branch October 2, 2026 14:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/api API related issues and pull requests area/generator Artifact generation related issues and pull requests enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Feature Request: Allow ArtifactGenerator to create ExternalArtifact in other namespaces

2 participants