k8s/topgun: update prometheus dependencies and disable worker #5568
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.
Why is this PR needed?
With
stable/prometheus
going from havingkube-state-metrics
embedded in its set of templates to a separate dependency,k8s-topgun
started failing:Without this PR, we can't have
k8s-topgun
running without having the version ofhelm/charts
pinned to an old commit, which would force us to have that commit hardcoded in the release branches, as well as the main pipeline.What is this PR trying to accomplish?
It tries to make the installation of
prometheus
possible regardless of how its dependencies are set up (either throughrequirements.yaml
- the new way of doing thing -, or the old one - embedded).How does it accomplish that?
It does so by running
helm dependency update
before runninghelm install
.Given that such command will not fail in case of
requirements.yaml
not existing (which would be true for older versions of thehelm/charts
repo), it's safe to always do it.Reviewer Checklist
and Helm packaging; otherwise, ignored for the integration tests (for example, if they are Garden configs that are not displayed in the
--help
text).