Repository navigation
hierarchical nats leaf topology and fix router upstream logic - #874
Merged
Merged
Conversation
…ough other leaves, while every server stays in one cluster. Parent leaves carry downstream application accounts, hub routes update when the mesh changes, and an operator key change reloads without rolling the hub.
… is reachable, and skip the Kubernetes Service when the listener is not on the hub router.
… hub or server reports the Controller namespace and a leaf reports the agent name.
…nd reloads it without rolling the StatefulSet.
…accounts so the operator guide matches the brokers that are rendered.
… operator rotation on the API.
…he vulnerable glob and minimatch releases and the pinned MSAL override.
…ode 24 and UBI9 base image digests.
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.
No description provided.