kubevela / kubevela/vector-controller
Discover the target pod by labels
Open
- Dominant language
- Go
- Stars
- 7
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
If we want to collect the pod logs, the simple way is to add a label for this pod. such as:
```yaml
labels:
vector.oam.dev/std-collector: enabled
```
Currently, we must create a CR.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the Go controller's current CR-based pod log collection path and compare it with the proposed vector.oam.dev/std-collector label. Define how labeled pods are discovered and how the existing CR flow is affected; done means labeled pods can have their logs collected without creating a CR, with appropriate coverage for the controller behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, observability-sre
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100