Replies: 1 comment 2 replies
-
it looks like this should be supported with the
However, I just tried that out and it doesn't seem to work. I created a namespace called
Then installed a provider with:
The package does not get to healthy, as the package manager appears to be failing to look up the crossplane service account, so that it can reuse any of its image pull secrets on the newly installed provider too:
That seems like a bug where the package manager is looking in the wrong namespace for the crossplane service account - it's looking in the new namespace where providers will be installed into, not the namespace where it itself is running. This typically works fine because the default for both is the same 😞 TL;DR it looks like this should work, but a potential bug is preventing it from working correctly |
Beta Was this translation helpful? Give feedback.
-
Hi folks!
It is possible to deploy a provider in a different namespace than the core?
For security and management reasons, we would like to split the deployment of each provider into its namespace. Is this possible in any way?
Beta Was this translation helpful? Give feedback.
All reactions