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.
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