Chart / Sec Hardening
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 152
- Forks
- 16
- Avg merge
- 14h 48m
- Merged PRs (30d)
- 536
Description
Goal
Harden the mecak8s Helm chart and Redis persistence posture for secure, reliable production operation.
This tracker follows a Kubernetes architecture, Helm, and security/SRE review of deploy/helm/mecak8s. The chart already has strong pod security contexts, verified Redis TLS, secure-provider validation, resource defaults, health probes, graceful shutdown, a strict values schema, and extensive Go/render tests. The linked sub-issues cover the remaining concrete risks and test gaps.
Scope
- Isolate the unauthenticated drain endpoint.
- Make Kubernetes Lease renewal and retained-object cardinality scale-safe.
- Isolate Lease/scheduler domains between releases.
- Improve HA placement and disruption behavior.
- Enforce shutdown/probe timing invariants.
- Reject invalid Helm value combinations and scope local Redis resources.
- Close remaining chart operational hardening gaps.
- Add application-level encryption for sensitive Redis payloads.
- Add
helm-unittestcoverage.
Each work item is tracked as a native GitHub sub-issue.
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 with the native sub-issues for the remaining risks in deploy/helm/mecak8s, then review the existing Go/render tests and the requested helm-unittest coverage. The work is done when the listed endpoint, Lease, placement, timing, values, Redis, encryption, and chart-hardening gaps are addressed with corresponding test coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, helm, kubernetes, redis
- Domain
- databases, devops, infrastructure, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100