(feat) Make namespace creation optional#1685
Merged
gianlucam76 merged 1 commit intoprojectsveltos:mainfrom Apr 1, 2026
Merged
Conversation
When Sveltos deploys resources defined in PolicyRefs or KustomizationRefs, it automatically attempts to "Get" the target namespace and "Create" it if it is missing. While convenient, this behavior forces Sveltos to require cluster-wide get and create permissions for Namespaces. For many managed production environments, Sveltos might be granted limited RBAC. If a user is operating in a multi-tenant cluster where namespaces are pre-provisioned and Sveltos lacks cluster-level permissions, the deployment currently fails. Changes: - Introduced SkipNamespaceCreation to the PolicyRef and KustomizationRef structs. - When enabled, Sveltos bypasses the namespace check/creation logic and attempts to deploy resources directly. Default behavior remains unchanged (false) to ensure backward compatibility.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When Sveltos deploys resources defined in PolicyRefs or KustomizationRefs, it automatically attempts to "Get" the target namespace and "Create" it if it is missing. While convenient, this behavior forces Sveltos to require cluster-wide get and create permissions for Namespaces.
For many managed production environments, Sveltos might be granted limited RBAC. If a user is operating in a multi-tenant cluster where namespaces are pre-provisioned and Sveltos lacks cluster-level permissions, the deployment currently fails.
Changes:
Default behavior remains unchanged (false) to ensure backward compatibility.
Fixes #1678