✨ sharded-test-server: support for running the caching layer #2320
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
adds support for running the
cache-server
to thesharded-test-server
binary.support for caching can be turned on by passing
--run-cache-server=true
flag, then the test binary will:8012
(HTTPS)8010
,8011
)filepath.Join(workingDir, ".kcp-cache")
directory3
next, the test binary will configure each shard with the following flags:
--run-cache-server=true
- inherited from the test binary itself--cache-server-kubeconfig-file
- that points to the kubeconfig created in step6
. A shard will use the config to establish connection with the cache serverin the future we could run the caching layer by default, for now (until it proves to work), it has to be gated with a flag.
Related issue(s)
part of #342