Skip to content
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

Provide information about available/used resources for the user's namespace #15305

Closed
skabashnyuk opened this issue Nov 25, 2019 · 1 comment
Closed
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system.

Comments

@skabashnyuk
Copy link
Contributor

skabashnyuk commented Nov 25, 2019

Is your task related to a problem? Please describe.

Now when we have the ability to provide a list of namespaces available for the user to create a workspace, it would be nice
to provide also information about available/used resources for the user's namespace.

Describe the solution you'd like

Namespace API should provide information about available/used resources

  • CPU
  • Memory
  • PV
  • Secrets

Describe alternatives you've considered

n/a

Additional context

 oc describe quota object-counts                                                                          
Name:                   object-counts
Namespace:              skabashn-che
Resource                Used  Hard
--------                ----  ----
persistentvolumeclaims  1     2
replicationcontrollers  0     20
secrets                 18    20
services                0     15
Name:       compute-resources
Namespace:  skabashn-che
Scopes:     NotTerminating
 * Matches all pods that do not have an active deadline. These pods usually include long running pods whose container command is not expected to terminate.
Resource       Used  Hard
--------       ----  ----
limits.cpu     0     16
limits.memory  0     8Gi
@skabashnyuk skabashnyuk added kind/task Internal things, technical debt, and to-do tasks to be performed. team/platform severity/P1 Has a major impact to usage or development of the system. labels Nov 25, 2019
@skabashnyuk skabashnyuk added this to the Backlog - Platform milestone Nov 25, 2019
@sleshchenko
Copy link
Member

duplicates #13504

@skabashnyuk skabashnyuk removed this from the Backlog - Platform milestone Nov 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Development

No branches or pull requests

2 participants