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

Enabling operator.targetallocator.mtls results in non-existent certificate mounts for non-Prometheus collectors #3456

Open
thefirstofthe300 opened this issue Nov 14, 2024 · 1 comment
Labels
bug Something isn't working needs triage

Comments

@thefirstofthe300
Copy link

thefirstofthe300 commented Nov 14, 2024

Component(s)

No response

What happened?

Description

After enabling the operator.targetallocator.mtls, all OTEL collector deployments are updated with MTLS certificates; however, only the deployments which create a Target Allocator actually appear to create the necessary certificates.

Steps to Reproduce

  1. Install operator
  2. Enable operator.targetallocator.mtls feature gate
  3. Create deployment without target allocator
  4. Wait infinitely for ContainerCreating to never complete.

Expected Result

Only collectors which use the target allocator mount the target allocator cert.

Actual Result

All collectors attempt to mount a target allocator cert

Kubernetes Version

1.30.6

Operator version

0.113.0

Collector version

0.113.0

Environment information

No response

Log output

No response

Additional context

No response

@thefirstofthe300 thefirstofthe300 added bug Something isn't working needs triage labels Nov 14, 2024
@jaronoff97
Copy link
Contributor

@ItielOlenick would you be able to take a look at this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs triage
Projects
None yet
Development

No branches or pull requests

2 participants