You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow transparent rolling restarts of a dotCMS cluster to logged-in, backend users #28532
Task
When terminating a dotCMS pod in aws eks we want to give the application time to finish in-flight requests. When k8s initiates a pod shutdown a few things happen.
The ALB Ingress default behavior needs no modification. When using kubernetes.io/ingress.class: al the pod is deregistered from the ALB TG. The deregistered target pod may finish in-flight requests but won't receive new requests.
In k8s we need to set timeouts so the Pod runs and Linkerd maintains its connection to the Pod for a brief period: pod preStop < linkerd 'wait before exit' < terminationGracePeriodSeconds
Parent Issue
Allow transparent rolling restarts of a dotCMS cluster to logged-in, backend users #28532
Task
When terminating a dotCMS pod in aws eks we want to give the application time to finish in-flight requests. When k8s initiates a pod shutdown a few things happen.
The ALB Ingress default behavior needs no modification. When using
kubernetes.io/ingress.class: al
the pod is deregistered from the ALB TG. The deregistered target pod may finish in-flight requests but won't receive new requests.In k8s we need to set timeouts so the Pod runs and Linkerd maintains its connection to the Pod for a brief period:
pod preStop < linkerd 'wait before exit' < terminationGracePeriodSeconds
example:
Proposed Objective
Cloud Engineering
Proposed Priority
Priority 3 - Average
The text was updated successfully, but these errors were encountered: