Labels

• blocked

  This item is currently blocked and can not be started
• bug

  Something isn't working
• documentation

  Improvements or additions to documentation
• documented
• enhancement

  New feature or request
• feature

  A new feature or change for the application
• help wanted

  Extra attention is needed
• homework

  Homework task defined by AMOS
• Impediment
• Improvement
• invalid

  This doesn't seem right
• PO

  Task for the product owners
• question

  Further information is requested
• r4a

  Ready for approval by Client
• refactoring

  Refactoring of old features
• REQ.1

  The proxy should be able to gather resource insights from it’s current Kubernetes cluster
• REQ.10

  The resources should be assigned to logical groups reasonably.
• REQ.11

  Resources can be viewed in a detailed single view with logical connections (egress,volumes,nodes,..)
• REQ.12

  The frontend should retrieve the information directly from the database
• REQ.13

  Resources can be displayed in a list view
• REQ.14

  The single resource view is accessable from the list view
• REQ.15

  Changes in resources shall be displayed in a changelog
• REQ.16

  The list view shall display the health state of each resource.
• REQ.17

  Overall status of the application’s resources shall be visible on the landing dashboard
• REQ.18

  Each logical group has a health indicator which is based on it’s children
• REQ.19

  The user can gather information about volumes. All volumes can be viewed in a list...
• REQ.2

  The proxy should run within a Kubernetes cluster.
• REQ.20

  The logs of unhealthy resources can be viewed.
• REQ.21

  Stateful sets should be available as logical groups.
• REQ.22

  Nodes should display information about the absolute and currently used capacity.