kyma-project / kyma-project/serverless
Have buildless serverless create a stateful set instead of a deployment
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6
- Forks
- 27
- Avg merge
- 11h 11m
- Merged PRs (30d)
- 11
Description
Description
Have buildless serverless create a stateful set instead of a deployment.
k8s stateful sets are far more predictable and way more resilient as compared to mere deployments.
I have been using KRO to bridge this gap so far. Still, serverless functions end up always as deployments....
That could be an option in the serverless CR.
Reasons
k8s stateful sets are far more predictable and way more resilient as compared to mere deployments.
Acceptance Criteria
- expected behaviors, outcomes ... ?
- ... new docs / update docs ... ?
Testing Strategy (DoD)
- automated unit test for the new logic
- automated integration test (a new test suite? or extending an existing test?)
- automated/manual test on SKR ?
Attachments
Related Issues
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
No files or tests are identified in the issue. Start by locating the serverless custom resource handling and the code that currently creates Deployments, then determine how a StatefulSet option should be represented and validated. Define acceptance criteria and add unit and integration coverage for the selected workload type.
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
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100