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/k8sobserver] ingress ressources #32971

Closed
M0NsTeRRR opened this issue May 9, 2024 · 2 comments
Closed

[extension/k8sobserver] ingress ressources #32971

M0NsTeRRR opened this issue May 9, 2024 · 2 comments
Labels
enhancement New feature or request extension/observer/k8sobserver needs triage New item requiring triage

Comments

@M0NsTeRRR
Copy link
Contributor

M0NsTeRRR commented May 9, 2024

Component(s)

extension/k8sobserver

Is your feature request related to a problem? Please describe.

I would like for otel to automatically discover my Ingress resources to enable tools like blackbox exporter to monitor SSL certificate expiration through receivercreator.

Describe the solution you'd like

Similar to pod and node endpoints, I would like to have an integration to dispatch this endpoint url to different exporters url as parameter.

Describe alternatives you've considered

Create a static list with a scrape config.

Additional context

No response

@M0NsTeRRR M0NsTeRRR added enhancement New feature or request needs triage New item requiring triage labels May 9, 2024
@M0NsTeRRR M0NsTeRRR reopened this May 9, 2024
Copy link
Contributor

github-actions bot commented May 9, 2024

Pinging code owners for extension/observer/k8sobserver: @rmfitzpatrick @dmitryax. See Adding Labels via Comments if you do not have permissions to add labels yourself.

dmitryax pushed a commit that referenced this issue Jun 27, 2024
**Description:** Add support for k8s.ingress endpoint

As described in the issue, this will allow users to dynamically obtain
Kubernetes ingress ressource, facilitating the monitoring of certificate
expiration with the Blackbox Exporter for example.
I didn't create a global ingress resource with sub-endpoints for each
path because I don't see a relevant 'target'. I'm uncertain about the
impact of my decision regarding the 'UID' as it's structured as
'{namespace}/{ingress UID}/{host}{path}'. Since a path automatically
starts with a '/', and can contain other '/', should I escape them ?

**Link to tracking Issue:** <Issue number if applicable>
#32971

---------

Signed-off-by: Ludovic Ortega <ludovic.ortega@adminafk.fr>
Co-authored-by: Chris Mark <chrismarkou92@gmail.com>
@dmitryax
Copy link
Member

Resolved by #33005

Thanks, @M0NsTeRRR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request extension/observer/k8sobserver needs triage New item requiring triage
Projects
None yet
Development

No branches or pull requests

3 participants