-
Notifications
You must be signed in to change notification settings - Fork 3
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
Feature: Dashboard for organizational identity view #40
Labels
Comments
@maia-iyer @mamy-CS please link your PRs to this issue. |
This was
linked to
pull requests
Aug 3, 2021
Merged
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature: Dashboard for organizational identity view
Box Note:
https://ibm.box.com/s/uu9hvimaokhbiz6qd253ow4vad7tdw59
Flows:
Stories to work on Epic
1 - Cluster Management Page
2 - Design of DashBoard UI and data model [Overview page]
3- Details of Cluster/ Agents/ Entries Page
Overview
This feature consists of the goal of allowing better oversight of workload identity. This consists of:
Consideration of moving propagation of logging information to a separate feature since the scope is rather large.... Or start with a rather naive propagation of metrics exposed by a simple tornjak API.
Motivation
Tasks
Information propagating:Information from SPIRE server Debug API (https://github.com/spiffe/spire-api-sdk/blob/main/proto/spire/api/server/debug/v1/debug.proto)Identity provisioning from SPIRE server logs (NOTE: Perhaps can be another feature on its own since its scope is rather big), alternatively fairly simple analysis can be done locally on each tornjak agent and only basic statistics propagated via tornjak API.Unless specified explicitly, functionality should be capable on agent views as well as managers.
Dashboard ideas
Something similar to k8s, where there is graphical information on top, and then a list of higher level constructs i.e. deployments <--> nodes/agents and pods <--> workloads
The text was updated successfully, but these errors were encountered: