[Task] <Kubernetes operator for HertzBeat>
Open
discussion
help wanted
new feature
task
- Dominant language
- Java
- Stars
- 7.4k
- Forks
- 1.3k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 32
Description
### Description
Add Kubernetes operator for HertzBeat server and collector to auto deploy, auto scale, auto discovery monitors
### Task List
_No response_
Contributor guide
Research direction
Start by reviewing how the HertzBeat server and collector are currently deployed and operated, then identify the Kubernetes resources and lifecycle requirements for an operator. The issue provides no repository files, tests, or entry points, so define the auto-deploy, auto-scale, and auto-discovery scope before implementation. Done means those requirements are specified and the operator manages both components.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- devops, infrastructure, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100