Implement agent reuse, toggled by a cluster profile config option #355
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.
Description
This implements agent reuse following the approach outlined in these comments: #53 (comment) #53 (comment). Resolves #53
Cluster profile has an option to enable agent reuse, defaulting to false:
The naming, and presentation of this option, are open to feedback! 馃檪
Changes
When pods are created, they are annotated with a hash of the elastic config. This ensures that when elastic config is changed, agents created from the old config will not be reused, and will eventually expire after the timeout.
When agent reuse is enabled, the main behavior changes are:
Other supporting changes:
properties
) for clarity between cluster profile properties and elastic profile properties.This ended up being a pretty large set of changes. Happy to explain in more detail if needed!
Testing
Many unit tests updated and added, and run with
./gradlew test
. I've also tested this running GoCD on my machine with a Kubernetes cluster inkind
.