-
Notifications
You must be signed in to change notification settings - Fork 109
Integration: Integrate a Timeline-based Kubernetes Resource Backtracking Tool #802
Copy link
Copy link
Open
Labels
help wantedExtra attention is neededExtra attention is neededintegrationEcological integrationEcological integrationmediumRequires a moderate level of project knowledge and skills, but does not require deep core technicalRequires a moderate level of project knowledge and skills, but does not require deep core technicalpriority/important-longtermP2 Important over the long term,but may not be staffed and/or may need multiple releases to completeP2 Important over the long term,but may not be staffed and/or may need multiple releases to complete
Milestone
Metadata
Metadata
Assignees
Labels
help wantedExtra attention is neededExtra attention is neededintegrationEcological integrationEcological integrationmediumRequires a moderate level of project knowledge and skills, but does not require deep core technicalRequires a moderate level of project knowledge and skills, but does not require deep core technicalpriority/important-longtermP2 Important over the long term,but may not be staffed and/or may need multiple releases to completeP2 Important over the long term,but may not be staffed and/or may need multiple releases to complete
What would you like to be added?
Integrate the khronoscope tool to enable timeline-based backtracking of Kubernetes resource states at any point in time, enhancing troubleshooting of resource.
Why is this needed?
This feature will enhance karpor debugging and troubleshooting capabilities by enabling users to:
Related issue: hoyle1974/khronoscope#33