-
Notifications
You must be signed in to change notification settings - Fork 110
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
installing packages with dependencies from private registry #789
Comments
The downside of the current solution for patching the Crossplane ServiceAccount with the pull secret, other than it being a shared secret for all packages, is that it will disappear (i.e. reset) when you upgrade Crossplane. Possible solutions we have been thinking about:
|
Re: This means we could still leverage / rely on this option as a stop gap solution for private images/dependencies. It is a little inconvenient for folks to run an upgrade command instead of simply patching existing SA, but for any serious non-development cluster, people use GitOps like flows to install Crossplane and this would be one additional line there. |
What's Missing?
The challenge of installing a package from a private registry that has further dependencies (e.g. family providers) recently came up in:
We have some existing docs for this scenario, but they are not quite complete:
The provider focused page mentions this challenge, but does not provide a solution for it:
As @turkenh suggested in crossplane/crossplane#5799 (comment), one solution is to provide package pull secrets at the Crossplane service account level instead of to individual packages. We could document this approach so it is more discoverable for folks using private registries.
The text was updated successfully, but these errors were encountered: