kuma-dp: if --config-dir argument is not set, automatically create a temp dir
#261
Conversation
This file contains 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
yskopets
force-pushed
the
feature/support-multiple-envoys-on-the-same-host
branch
from
4a8d3d7 to
0f48740
Compare
jakubdyszkiewicz
approved these changes
Sep 16, 2019
jakubdyszkiewicz
deleted the
feature/support-multiple-envoys-on-the-same-host
branch
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.
Summary
Previously,
kuma-dphad--config-diroption set to/tmp/kuma.io/envoyby default.If 2
kuma-dpinstances were started on the same machine, both of them would persist generated config file at/tmp/kuma.io/envoy/bootstrap.yaml, overwriting each other.Full changelog
--config-diris emptykuma-dpwill create a temporary dir, use it to store generated Envoy config, and remove that directory on exit