feat(kubernetes): Skip loading events for manifest retrieval in WaitF… #2997
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.
This change makes use of the changes in spinnaker/clouddriver#3796 to skip loading events when retrieving manifests in WaitForManifestStableTask.
We ran into this scenario when we had a lot of deployment pipelines running concurrently, and each deployment involved a decent number of manifests (~30). This task iterates through the manifests involved in the deployment and calls the retrieve manifest API for each one, which (when live manifest mode is enabled) causes a lot of full event loads to occur, which tanks (in our case) the kubernetes API server.
WaitForManifestStableTask does not actually need any event information to do its job, so in this particular case we can skip loading events and prevent the extra load on the kubernetes api server.