Skip to content

Backport of fix: add skip_exit to drain_listeners to prevent premature pod termin… into release/1.9.x#1068

Merged
hc-github-team-consul-core merged 1 commit into
release/1.9.xfrom
backport/spulluri/fix_envoy_drain_issue_main/painfully-central-stork
Jun 24, 2026
Merged

Backport of fix: add skip_exit to drain_listeners to prevent premature pod termin… into release/1.9.x#1068
hc-github-team-consul-core merged 1 commit into
release/1.9.xfrom
backport/spulluri/fix_envoy_drain_issue_main/painfully-central-stork

Conversation

@hc-github-team-consul-core

Copy link
Copy Markdown
Collaborator

Backport

This PR is auto-generated from #1064 to be assessed for backporting due to the inclusion of the label backport/1.9.

The below text is copied from the body of the original PR.


Description

When upgrading Envoy from 1.35 to 1.37, pods were being terminated early
during graceful shutdown. The POST /drain_listeners?graceful endpoint causes
Envoy to automatically exit after the drain period (--drain-time-s), which
raced against consul-dataplane's own lifecycle sequencing:

Drain() → wait shutdownGracePeriodSeconds → Quit() → Kill()

Adding &skip_exit decouples the drain phase from the exit decision, ensuring
Envoy stays alive until consul-dataplane explicitly calls Quit() via
/quitquitquit, preserving the intended shutdown lifecycle control.


Overview of commits

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Auto approved Consul Bot automated PR

@hc-github-team-consul-core hc-github-team-consul-core merged commit b838fd4 into release/1.9.x Jun 24, 2026
38 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants