aws-for-fluent-bit: liveness and readiness probes
- Dominant language
- Mustache
- Stars
- 1.3k
- Forks
- 1.1k
- Avg merge
- 22m
- Merged PRs (30d)
- 5
Description
**Is your feature request related to a problem?**
Yes. When fluentbit crashes we don't have a probe to know one way or another (really needed on first deployment).
**Is your feature request related to a specific Helm chart, if yes mention name of the chart?**
aws-for-fluent-bit
**Describe the solution you'd like**
Configurable liveness and readiness probes for aws-for-fluent-bit chart.
**Describe alternatives you've considered**
If there are any I would love to hear them!
Contributor guide
Research direction
Start with the aws-for-fluent-bit Helm chart and inspect how its workload configuration is organized. Define configurable liveness and readiness probes for the chart, then verify that the rendered Kubernetes resources expose both probe settings and that the probes can detect a crashed fluent-bit deployment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100