Skip to content

fix: don't flap DataPlane ready status on rolling update - #3909

Draft
pmalek wants to merge 1 commit into
mainfrom
dataplane-ready-status
Draft

fix: don't flap DataPlane ready status on rolling update#3909
pmalek wants to merge 1 commit into
mainfrom
dataplane-ready-status

Conversation

@pmalek

@pmalek pmalek commented Apr 15, 2026

Copy link
Copy Markdown
Member

What this PR does / why we need it:

This changes how DataPlane defines its Ready status condition.

Previously it has been:

if status.AvailableReplicas < status.Replicas {
  // not ready
}

This PR proposes the following:

if status.AvailableReplicas < spec.Replicas {
  // not ready
}

This prevents DataPlane flapping its Ready status condition during a rolling update

Which issue this PR fixes

Fixes #

Special notes for your reviewer:

Related: https://github.com/Kong/gateway-operator-archive/pull/1348/

PR Readiness Checklist:

Complete these before marking the PR as ready to review:

  • the CHANGELOG.md release notes have been updated to reflect significant changes

@pmalek pmalek self-assigned this Apr 15, 2026
@pmalek
pmalek force-pushed the dataplane-ready-status branch from 01b11cc to f601a99 Compare April 15, 2026 15:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant