Deploy a provider in a different namespace than the core

[jbw976]

Discussed in #5449

^{Originally posted by xoanmi March 4, 2024}
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?

From investigation on the discussion in #5449 (comment):

TL;DR it looks like this should work, but a potential bug is preventing it from working correctly

[negz]

@xoanmi is your goal to deploy all providers to one namespace that is different from where Crossplane is deployed, or to deploy each provider to its own namespace? Based on the linked discussion, it sounds like the latter.

[xoanmi]

@xoanmi is your goal to deploy all providers to one namespace that is different from where Crossplane is deployed, or to deploy each provider to its own namespace? Based on the linked discussion, it sounds like the latter.

Both options are fine for us, but the second let us more flexibility :)