Skip to content

No labels!

There aren’t any labels for this repository quite yet.

44 labels

Sort
Sort
Alphabetically
Reverse alphabetically
Most issues
Fewest issues
blocked
blocked
This item is currently blocked and can not be started
7
bug
bug
Something isn't working
documentation
documentation
Improvements or additions to documentation
2
documented
documented
enhancement
enhancement
New feature or request
feature
feature
A new feature or change for the application
18
help wanted
help wanted
Extra attention is needed
homework
homework
Homework task defined by AMOS
4
Impediment
Impediment
Improvement
Improvement
3
invalid
invalid
This doesn't seem right
PO
PO
Task for the product owners
question
question
Further information is requested
r4a
r4a
Ready for approval by Client
refactoring
refactoring
Refactoring of old features
1
REQ.1
REQ.1
The proxy should be able to gather resource insights from it’s current Kubernetes cluster
1
REQ.2
REQ.2
The proxy should run within a Kubernetes cluster.
1
REQ.3
REQ.3
Changes to resources and configurations are tracked and persisted
REQ.4
REQ.4
The application should display information about nodes and the running pods on a node.
3
REQ.5
REQ.5
The user can access the information via a web application
REQ.6
REQ.6
Each resource shall have a health indicator displaying the current state.
1
REQ.7
REQ.7
The application should be comfortable used from the desktop browser.
4
REQ.8
REQ.8
Each proxy should write into it’s dedicated database.
REQ.9
REQ.9
Resources should be searchable by name within the Web-UI
1
REQ.10
REQ.10
The resources should be assigned to logical groups reasonably.
3
REQ.11
REQ.11
Resources can be viewed in a detailed single view with logical connections (egress,volumes,nodes,..)
4
REQ.12
REQ.12
The frontend should retrieve the information directly from the database
REQ.13
REQ.13
Resources can be displayed in a list view
6
REQ.14
REQ.14
The single resource view is accessable from the list view
REQ.15
REQ.15
Changes in resources shall be displayed in a changelog