[receiver/k8s cluster receiver]add support for K8s leader extension into k8s cluster receiver #38429
Conversation
This file contains hidden or 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
rakesh-garimella
requested review from
dmitryax,
TylerHelmuth,
ChrsMark and
a team
as code owners
github-actions
bot
added
cmd/otelcontribcol
rakesh-garimella
changed the title
rakesh-garimella
force-pushed
the
k8s_leader_support_for_k8s_cluster_receiver
branch
from
0eacdf0 to
bc5304c
Compare
|
This PR was marked stale due to lack of activity. It will be closed in 14 days. |
atoulme
reviewed
Apr 10, 2025
atoulme
reviewed
Apr 10, 2025
atoulme
reviewed
Apr 11, 2025
atoulme
reviewed
Apr 11, 2025
|
moving to draft, please address feedback and fix conflicts, and mark ready to review again |
dmitryax
approved these changes
Apr 16, 2025
akshays-19
pushed a commit
to akshays-19/opentelemetry-collector-contrib
that referenced
this pull request
Apr 23, 2025
…nto k8s cluster receiver (open-telemetry#38429) #### Description - Add support for k8s leader elector to k8s cluster receiver so that multiple instances of k8s cluster receiver can be executed. - The instance which has the lease fetches the metrics. example config: ```yaml extensions: k8s_leader_elector: auth_type: kubeConfig lease_name: foo lease_namespace: default receivers: k8s_cluster: k8s_leader_elector: k8s_leader_elector node_conditions_to_report: [Ready, MemoryPressure] allocatable_types_to_report: [cpu, memory] exporters: debug: verbosity: detailed service: extensions: [k8s_leader_elector] pipelines: metrics: receivers: [k8s_cluster] exporters: [debug] telemetry: logs: level: info ```
Fiery-Fenix
pushed a commit
to Fiery-Fenix/opentelemetry-collector-contrib
that referenced
this pull request
Apr 24, 2025
…nto k8s cluster receiver (open-telemetry#38429) #### Description - Add support for k8s leader elector to k8s cluster receiver so that multiple instances of k8s cluster receiver can be executed. - The instance which has the lease fetches the metrics. example config: ```yaml extensions: k8s_leader_elector: auth_type: kubeConfig lease_name: foo lease_namespace: default receivers: k8s_cluster: k8s_leader_elector: k8s_leader_elector node_conditions_to_report: [Ready, MemoryPressure] allocatable_types_to_report: [cpu, memory] exporters: debug: verbosity: detailed service: extensions: [k8s_leader_elector] pipelines: metrics: receivers: [k8s_cluster] exporters: [debug] telemetry: logs: level: info ```
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
example config:
Link to tracking issue
Fixes
Testing
Documentation