KusionStack / KusionStack/karpor
Integration: Integrate a Timeline-based Kubernetes Resource Backtracking Tool
- Dominant language
- Go
- Stars
- 1.7k
- Forks
- 113
- PR merge metrics
- No merged PRs in 30d
Description
## What would you like to be added?
Integrate the [khronoscope](https://github.com/hoyle1974/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:
1. Current Limitations:
- Limited ability to debug Kubernetes resource changes over time
- Inability to effectively track resource state alterations
- No comprehensive timeline view for resource modifications
2. Proposed Integration:
- Integrate khronoscope for timeline-based resource tracking
- Enable historical resource state analysis
- Provide an interface for easy navigation and comparison of resource states across time
3. Expected Benefits:
- Improved understanding of resource behavior over time
- Enhanced user experience in troubleshooting
Related issue: https://github.com/hoyle1974/khronoscope/issues/33
Contributor guide
Research direction
Start by reading the khronoscope repository and related issue #33, then inspect karpor's Kubernetes visualization and resource-troubleshooting entry points. Define the integration boundary, historical state navigation and comparison behavior, and the validation needed to show that resource states can be inspected across time.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- infrastructure, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100