Added support to collect control plane component metrics; etcd #384
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
dmitryax
reviewed
Feb 20, 2022
|
Since we have a splunk and etcd secret now, I refactored (secret->secret-splunk) the original secret file names. |
dmitryax
reviewed
Mar 1, 2022
|
@jvoravong please rebase the PR |
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.
Description:
This PR adds support for collecting metrics from the k8s etcd.
Testing:
I tested and verified these changes with Kubernetes and Openshift.
Notes:
We need the collector to have access to the etcd TLS certs. In this PR we have the user supply the needed certs using values.yaml. Other collector distributions that collect etcd metrics also require the user to do a similar setup.