Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Registry secrets should be configurable per Pipeline #429

Open
mms-gianni opened this issue Oct 7, 2024 · 1 comment · Fixed by #427
Open

Registry secrets should be configurable per Pipeline #429

mms-gianni opened this issue Oct 7, 2024 · 1 comment · Fixed by #427
Assignees
Labels
enhancement New feature or request in progress working on it
Milestone

Comments

@mms-gianni
Copy link
Member

Description

It's currently not possible to use different registry credentials per Pipeline.

Copying the secrets with the Operator led to high CPU and RAM usage.

Possible solution

Registry secrets should be configurable per Pipeline. Copying would be avoided.

The Kubero defaults are loaded during the creation of a new Pipeline.

Alternatives

No response

Additional information

No response

@mms-gianni mms-gianni added enhancement New feature or request in progress working on it labels Oct 7, 2024
@mms-gianni mms-gianni linked a pull request Oct 7, 2024 that will close this issue
12 tasks
@mms-gianni mms-gianni added this to the v2.4.3 milestone Oct 7, 2024
@mms-gianni mms-gianni pinned this issue Oct 7, 2024
@mms-gianni
Copy link
Member Author

image

@mms-gianni mms-gianni self-assigned this Oct 7, 2024
@mms-gianni mms-gianni changed the title Registry serets should be configurable per Pipeline Registry secrets should be configurable per Pipeline Oct 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request in progress working on it
Projects
Status: In Progress
Development

Successfully merging a pull request may close this issue.

1 participant