-
Notifications
You must be signed in to change notification settings - Fork 302
feat: cluster resources namespace #5433
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
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: fuskovic <[email protected]>
Signed-off-by: fuskovic <[email protected]>
Signed-off-by: fuskovic <[email protected]>
Signed-off-by: fuskovic <[email protected]>
Signed-off-by: fuskovic <[email protected]>
Signed-off-by: fuskovic <[email protected]>
✅ Deploy Preview for docs-kargo-io ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #5433 +/- ##
=======================================
Coverage 55.07% 55.07%
=======================================
Files 426 426
Lines 31487 31487
=======================================
Hits 17342 17342
Misses 13145 13145
Partials 1000 1000 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Signed-off-by: fuskovic <[email protected]>
|
When doing this is it maybe possible to add annotations to the namespace? In case of permitted regex for for example external-secrets. external-secrets.io/allowed-secret-store: ""
external-secrets.io/permitted-key-regex: ""When creating the namespace it would help if we can provide these. |
Deprecates
CLUSTER_SECRETS_NAMESPACEin favor of newCLUSTER_RESOURCES_NAMESPACE.Related to: #4778