docs(extension-server): document edge re-translation for connector liveness#213
Merged
Merged
Conversation
…veness Update the Envoy Gateway extension server enhancement to reflect that Connector online/offline transitions are now driven by an edge-local re-translation controller co-located with the extension server, rather than a project-side Connector controller touching the downstream Gateway. - Rewrite "Connector online/offline transitions" to describe the cache-sharing edge controller and why running it at the edge removes the cross-cluster ordering race the project-side trigger had. - Record the rejected project-side trigger alongside the existing rejected spec-nonce alternative. - Correct the security/topology sections: the workload is no longer strictly read-only — it holds a single narrow `patch` on Gateway for the trigger annotation, and the embedded controller runs on every replica safely via an idempotent merge patch. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
scotwells
force-pushed
the
docs/extension-server-edge-retranslation
branch
from
7caeee7 to
de0dc70
Compare
…CK-freeze observability, and known gaps Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This was referenced Jun 23, 2026
ecv
approved these changes
Jun 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Updates the Envoy Gateway extension server enhancement doc to match how Connector online/offline transitions actually trigger re-translation today.
The doc described a project-side Connector controller that touched the downstream Gateway annotation when
Readyflipped. That mechanism has a cross-cluster ordering race — the Gateway touch and the Connector's status annotation propagate to the edge independently through Karmada, so the touch can arrive first and drive a re-translation that reads stale liveness from the edge cache, leaving the data plane wedged on the old program.The implementation (#211) moves the trigger to an edge-local re-translation controller co-located with the extension server and sharing its informer cache. This doc brings the design write-up in line with that.
Changes
(online, nodeID)changes, idempotent merge-patch of a trigger annotation on Gateways backed by a referencingHTTPProxy, and why running it at the edge (same cache EG translates against) removes the ordering race.patchonGatewayfor the trigger annotation, and the embedded controller runs on every replica safely via the idempotent merge patch (no leader election needed).Notes
Related
docs/enhancements/envoy-gateway-extension-server/README.md🤖 Generated with Claude Code