Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[extension/observer/k8s] Add k8s.node discovery #6820

Merged

Conversation

rmfitzpatrick
Copy link
Contributor

Description: Adding a feature -
These changes adopt the new k8s.node endpoint type in the k8s_observer and provide new config fields observe_nodes and observe_pods to toggle desired Endpoint type discovery. The existing node config field is no longer mandatory and missing values will result in all available nodes and pods in being reported.

They do not include adoption in the receiver creator, as that will be addressed in a subsequent PR.

Link to tracking Issue:
#6540

Testing:
Added unit tests for endpoint conversion and observer.Observable methods.

Documentation:
Updated readme with usage and config improvements, though they are dependent on separate receiver creator adoption.

@rmfitzpatrick rmfitzpatrick requested review from a team and anuraaga December 15, 2021 20:24
@rmfitzpatrick rmfitzpatrick force-pushed the k8sobservernodediscovery branch 3 times, most recently from e450bef to 10af79f Compare December 15, 2021 22:10
@jpkrohling jpkrohling changed the title k8s_observer: Add k8s.node discovery [extension/observer/k8sobserver] Add k8s.node discovery Dec 16, 2021
@jpkrohling jpkrohling changed the title [extension/observer/k8sobserver] Add k8s.node discovery [extension/observer/k8s] Add k8s.node discovery Dec 16, 2021
@rmfitzpatrick rmfitzpatrick force-pushed the k8sobservernodediscovery branch 3 times, most recently from a52f637 to c989cae Compare December 20, 2021 20:04
Copy link
Member

@dmitryax dmitryax left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@tigrannajaryan
Copy link
Member

@rmfitzpatrick @dmitryax can you also add yourself as codeowners for this extension? Can be in a separate PR.

@tigrannajaryan
Copy link
Member

@rmfitzpatrick the lint job is failing.

@dmitryax
Copy link
Member

@rmfitzpatrick please rebase, the linter job is fixed now

Ryan Fitzpatrick added 4 commits December 21, 2021 16:04
These changes adopt the new k8s.node endpoint type in the k8s_observer
and provide new config fields `observe_nodes` and `observe_pods` to
toggle desired Endpoint type discovery. The existing `node` config
field is no longer mandatory and missing values will result in all
available nodes and pods in being reported.

They do not include adoption in the receiver creator, as that will be
addressed in a subsequent PR.
@tigrannajaryan tigrannajaryan merged commit ebea5bc into open-telemetry:main Dec 21, 2021
animetauren pushed a commit to animetauren/opentelemetry-collector-contrib that referenced this pull request Apr 4, 2023
Re-do of open-telemetry#6820

- make chlog-update and update of core builder test
- Amend changelog name
- prepare release v1.0.0-rc2
- Prepare stable for version v1.0.0-rc2
- add multimod changes

This corresponds to the first three points under step 6. The last point is done on a separate PR, open-telemetry/opentelemetry-collector#6822.

Link to tracking Issue: Fixes open-telemetry/opentelemetry-collector#6819

Co-authored-by: Alex Boten <aboten@lightstep.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants