redhat-developer / redhat-developer/abbenay
fix(daemon): reuse auto-generated gRPC TLS material across restarts
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 12
- Forks
- 7
- Avg merge
- 7h 7m
- Merged PRs (30d)
- 3
Description
Context
--grpc-tls always regenerates server.crt / server.key / ca.crt under the runtime tls/ directory on every start (writeAutoTlsMaterial). Clients that cached ca.crt break after a daemon (or container) restart.
Flagged during review of PR #63: https://github.com/redhat-developer/abbenay/pull/63
Proposal
- If valid cert+key already exist under
tls/, reuse them instead of regenerating - Document lifetime clearly in CONTAINER.md (and note when regeneration happens)
- Optional: volume-mount guidance so container CA remains stable across restarts
References
- PR #63
- DR-029
Contributor guide
No contributing guide indexed for this repository
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 locating the daemon's writeAutoTlsMaterial implementation and the runtime tls/ directory behavior described in the issue. Review CONTAINER.md for the existing TLS guidance; done means valid existing certificate material is reused, regeneration conditions are clear, and the container persistence guidance is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, documentation, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100