Repository navigation
Conversation
Signed-off-by: Kuromesi <blackfacepan@163.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
This branch has not been deployed
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
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.
A restored dedicated ztunnel can receive a JWT bound to a replacement Pod while retaining the same SPIFFE identity. Its cached certificate and pooled HBONE connections can still identify the previous Pod, preventing gateway traffic from recovering even after ADS reconnects successfully.
Snapshot the JWT on each dedicated ADS connection and use its Pod UID to partition certificate requests and HBONE pool entries. When the Pod changes, discard the previous certificate cache and prevent its in-flight signing results from filling the new cache. Normal token renewal for the same Pod keeps its certificates and connections. This adds no configuration or per-request token-file reads and leaves shared-mode identity handling unchanged.
Validation on Linux with Rust 1.90.0:
cargo check --locked,cargo clippy --locked --lib --bins, formatting, and the repository copyright check passed.The platform must supply a JWT bound to the new Pod. This change cannot repair a restored projected volume that still contains the old Pod JWT. Natural ACS deep-sleep recovery and the full privileged firewall test suite were not rerun for this PR. Existing in-flight streams are not forcibly terminated.