-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Add support for namespaced deployment #7684
Copy link
Copy link
Open
Labels
kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Metadata
Metadata
Assignees
Labels
kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Is your feature request related to a problem? Please describe.
Cert-manager supports limiting its scope to a single namespace via the
--namespacecommand-line:However, this deployment mode is not currently supported by the Helm chart, and there are no automated tests to catch any potential issues introduced by changes in the code base.
Describe the solution you'd like
This request is to add official support for namespaced deployments by:
RoleandRoleBindinginstead ofClusterRoleandClusterRoleBinding.Describe alternatives you've considered
Additional context
This feature was discussed in #7678 (comment).
In the past there has been a case where regression has occurred and it was not catched by existing tests, see #5524 and #7676.
Environment details (remove if not applicable):
mainhelm/kind feature