-
Notifications
You must be signed in to change notification settings - Fork 59
Updated change log for namespace release #434
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
🎉 Thank you for your contribution! It appears you have not yet signed the F5 Contributor License Agreement (CLA), which is required for your changes to be incorporated into an F5 Open Source Software (OSS) project. Please kindly read the F5 CLA and reply on a new comment with the following text to agree: I have hereby read the F5 CLA and agree to its terms 2 out of 3 committers have signed the CLA. |
Schedule updated. Looks ready for April 23.
|
@weli02 Please sign the CLA as instructed by the github-actions bot. It's punctuation sensitive, so the line has to be copied exactly. |
Proposed changes
Problem: Need to support namespace rbac permission control at Nginx One Console
Solution: Nginx One Console now support multi-namespace, allowing users to configure a more granular Rbac permissions for different users.
Testing: Navigate to N1 Console and can select different namespaces.
Please focus on (optional): If you any specific areas where you would like reviewers to focus their attention or provide
specific feedback, add them here.
If this PR addresses an issue on GitHub, ensure that you link to it here:
Closes #ISSUE
Checklist
Before merging a pull request, run through this checklist and mark each as complete.
README.md
andCHANGELOG.md
Footnotes
Potentially sensitive changes include anything involving code, personally identify information (PII), live URLs or significant amounts of new or revised documentation. Please refer to our style guide for guidance about placeholder content. ↩