Skip to content

Sharing DestinationConfig objects between clusters with InMemoryConfigProvider -- safe? #2224

Answered by Tratcher
j3parker asked this question in Q&A
Discussion options

You must be logged in to vote

DestinationConfig is read-only input, it doesn't matter if you re-use it. It's actually designed to be re-used when reloading configuration after some inputs changed. I would only caution you not to re-use the destination names, those are consumed elsewhere in the stack like for session affinity.

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@j3parker
Comment options

Answer selected by j3parker
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants