-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Limit ranges frontend #1285
Limit ranges frontend #1285
Conversation
Current coverage is 93.85% (diff: 96.73%)@@ master #1285 diff @@
==========================================
Files 342 355 +13
Lines 3080 3171 +91
Methods 0 0
Messages 0 0
Branches 0 0
==========================================
+ Hits 2888 2976 +88
- Misses 192 195 +3
Partials 0 0
|
187bacd
to
059b999
Compare
09611ea
to
6896940
Compare
'Limit Ranges' section is missing on admin page. Please add. |
ab1f443
to
09fb8f0
Compare
'Limit Ranges' section is added on admin page. PTAL |
09fb8f0
to
2ee815e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm... Can you show a couple of screenshots here? Should this be added to top level navigation or just as a property of a namespace?
I'm concerned about this because I think it does not make sense to look at a limit range alone. A limit range always belongs to exactly one namespace.
What do you think?
@bryk I think it should be like resource quotas only in namespace details. I will move limit range detail to namespace detail and post some screen shots. |
2ee815e
to
c8300e4
Compare
@batikanu Awesome, thanks! |
Implementation of Limit ranges frontend.
It includes also small fixes in backend.