mayadata-io / mayadata-io/d-operators
proposal: Log as a custom resource
Open
Nobody has claimed this yet.
logs
proposal
upload
- Dominant language
- Go
- Stars
- 10
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
Draft specs:
kind: Log
spec:
podName:
podNamespace:
containerSelector:
tailCount:
status:
- The backing controller fetches the logs from relevant container(s) and sets them against
statusfield
References:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the proposed Log custom-resource YAML and the linked stern project to understand the intended log-fetching behavior. Done means the backing controller retrieves logs for the selected pod containers and records them in the resource's status field.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- backend, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100