Support NEK key rotation for ESS
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 218
- Forks
- 72
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 427
Description
Is your feature request related to a problem? Please describe.
NVCF deployments need a supported key rotation path for NVCF Encryption Key (NEK) usage in the ESS Worker flow. Without a documented rotation path, operators may need manual procedures that are hard to validate, hard to repeat, and risky during upgrades.
Describe the solution you'd like
Add NEK key rotation support for ESS Worker.
The implementation should cover:
- Supported key rotation workflow.
- ESS Worker behavior before, during, and after rotation.
- Compatibility behavior for existing workloads.
- Failure handling and rollback guidance.
- Operator documentation for rotation prerequisites and validation.
Describe alternatives you've considered
Operators can rotate keys manually, but manual rotation is brittle and creates operational risk when workloads, secrets, or worker state are already active.
Additional context
Suggested acceptance criteria:
- NEK key rotation is supported for the ESS Worker path.
- Existing supported workloads continue to function across rotation.
- Failed rotation behavior is documented.
- Rollback or recovery guidance is documented.
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 locating the ESS Worker flow and the existing NVCF Encryption Key usage, then map behavior before, during, and after rotation. Done means a supported rotation workflow preserves existing workloads, defines failure and rollback or recovery behavior, and includes operator prerequisites and validation guidance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, cloud, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100