Graceful Shutdown

Graceful shutdown drains existing connections from Envoy Proxy instances before termination. This prevents connection drops during pod rollouts, scaling events, and cluster upgrades.

Why Graceful Shutdown?

Without graceful shutdown, when an Envoy pod terminates:

• Active connections are immediately dropped
• In-flight requests may fail
• Clients experience errors during deployments

With graceful shutdown enabled (default), the shutdown manager sidecar intercepts SIGTERM signals and runs a controlled drain process so existing connections can complete.

Configuration

Configure graceful shutdown in the Config CRD under spec.envoyProxy.gracefulShutdown:

apiVersion: kubelb.k8c.io/v1alpha1
kind: Config
metadata:
  name: default
  namespace: kubelb
spec:
  envoyProxy:
    gracefulShutdown:
      disabled: false
      drainTimeout: 60s
      minDrainDuration: 5s
      terminationGracePeriodSeconds: 300

Configuration Fields

How It Works

1. Kubernetes sends SIGTERM to the Envoy pod
2. The shutdown manager sidecar intercepts the signal
3. Envoy enters draining state and stops accepting new connections
4. Existing connections continue to be served
5. After drainTimeout or when all connections close (whichever comes first), Envoy terminates
6. The minDrainDuration ensures a minimum drain window for late-arriving requests

Example: High-Traffic Production Setup

For environments with long-lived connections or high traffic:

apiVersion: kubelb.k8c.io/v1alpha1
kind: Config
metadata:
  name: default
  namespace: kubelb
spec:
  envoyProxy:
    gracefulShutdown:
      drainTimeout: 120s
      minDrainDuration: 10s
      terminationGracePeriodSeconds: 180

Example: Disable Graceful Shutdown

For development environments where fast restarts are preferred:

apiVersion: kubelb.k8c.io/v1alpha1
kind: Config
metadata:
  name: default
  namespace: kubelb
spec:
  envoyProxy:
    gracefulShutdown:
      disabled: true

Further Reading

• Envoy Drain Documentation