Skip to content

Conversation

@iblancasa
Copy link
Contributor

@iblancasa iblancasa requested a review from a team as a code owner December 3, 2024 13:34
Copy link
Contributor

@jaronoff97 jaronoff97 left a comment

Choose a reason for hiding this comment

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

Do we need to worry about people who are already using this feature? Wouldn't starting it as disabled break people who had this from the previous version?

@swiatekm
Copy link
Contributor

swiatekm commented Dec 3, 2024

We should label this as a breaking change, but imo disabled is the better default. Most of the time, packaging (usually Helm or kustomize) is going to take care of this. The intended use case here is primarily OpenShift in my view.

@iblancasa
Copy link
Contributor Author

Done @swiatekm

@jaronoff97 jaronoff97 requested a review from swiatekm December 3, 2024 17:57
Signed-off-by: Israel Blancas <iblancasa@gmail.com>
@swiatekm swiatekm requested a review from frzifus February 18, 2025 10:28
@jaronoff97 jaronoff97 merged commit 04df525 into open-telemetry:main Feb 18, 2025
39 checks passed
Starefossen pushed a commit to Starefossen/opentelemetry-operator that referenced this pull request Apr 10, 2025
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.

operator doesn't respect manager.serviceMonitor.enabled helm value

4 participants