Prometheus telemetry K8S compatibility + functional test enhancements #566
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
tsebastiani
force-pushed
the
k8s_telemetry_prometheus
branch
9 times, most recently
from
84c0979
to
120e419
Compare
tsebastiani
changed the title
tsebastiani
force-pushed
the
k8s_telemetry_prometheus
branch
from
120e419
to
b463742
Compare
Signed-off-by: Tullio Sebastiani <[email protected]> added comment on the node selector input.yaml Signed-off-by: Tullio Sebastiani <[email protected]>
tsebastiani
force-pushed
the
k8s_telemetry_prometheus
branch
from
b463742
to
45a26dd
Compare
tsebastiani
changed the title
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.
This PR introduces the new fully K8S compatible version of the telemetry collection feature. I also introduces an enhanced version of the functional test Action that will allow to run also a functional tests suite on the merge event. Has been introduced to run more complex functional test (like the
telemetry_test) that needs to access Action secrets to be performed.