-
Notifications
You must be signed in to change notification settings - Fork 897
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
Deploy a provider in a different namespace than the core #5576
Comments
@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 :) |
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):
The text was updated successfully, but these errors were encountered: