Self-managed SIS should recover after NATS interruptions
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 218
- Forks
- 72
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 427
Description
Problem
In self-managed deployments, SIS can retain a closed NATS connection after authentication expiry or a NATS restart. Function deployments may then remain in DEPLOYING because the create-instance message is not published to the worker plane.
Expected behavior
The self-managed stack should consume the SIS chart release that enables NATS reconnect so SIS recovers without requiring a service restart.
Acceptance criteria
- The self-managed stack pins a SIS chart release with reconnect enabled.
- Existing stack validation passes.
- No release ordering or Kubernetes resource-shape changes are introduced.
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 in the self-managed deployment configuration and locate the SIS chart release/version and its NATS reconnect setting. Update the pin so reconnect is enabled, then run the existing stack validation. Done means validation passes without changing release ordering or Kubernetes resource shapes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100