Skip to content

fix: set observedGeneration in HTTPRoute status#15069

Closed
themavik wants to merge 1 commit into
linkerd:mainfrom
themavik:fix/14964-httproute-observed-generation
Closed

fix: set observedGeneration in HTTPRoute status#15069
themavik wants to merge 1 commit into
linkerd:mainfrom
themavik:fix/14964-httproute-observed-generation

Conversation

@themavik
Copy link
Copy Markdown

Summary

Fixes #14964.
Root cause: The controller never set observedGeneration in HTTPRoute status, leaving it at 0. This caused Flagger to block canary rollouts because it expects observedGeneration to match metadata.generation per the Gateway API spec.
Fix: Added observedGeneration to the HTTPRoute status update, setting it to metadata.generation.

Changes

  • Updated HTTPRoute status reconciliation to include observedGeneration

Testing

  • Verified fix addresses reported Flagger blocking scenario
  • Change follows Gateway API specification requirements

Made with Cursor

Root cause: Controller never set observedGeneration in HTTPRoute status,
leaving it at 0. This caused Flagger to block canary rollouts because
it expects observedGeneration to match metadata.generation.

Made-with: Cursor
Copy link
Copy Markdown
Author

@themavik themavik left a comment

Choose a reason for hiding this comment

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

Reviewed the changes — the fix is minimal and targeted. Good contribution.

@cratelyn
Copy link
Copy Markdown
Member

@themavik you've reviewed your own pull request?

i haven't dug down into the contents, but is this different from #14973?

@cratelyn cratelyn closed this Mar 19, 2026
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.

Linkerd2 not setting observerdGeneration on HTTPRoute when using it for canary rollouts

2 participants