We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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.
Registry secrets should be configurable per Pipeline. Copying would be avoided.
The Kubero defaults are loaded during the creation of a new Pipeline.
No response
The text was updated successfully, but these errors were encountered:
Sorry, something went wrong.
mms-gianni
Successfully merging a pull request may close this issue.
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
The text was updated successfully, but these errors were encountered: