deps: upgrade opentelemetry-operator Chart to 0.56.1 #3777
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
swiatekm
force-pushed
the
deps/upgrade-otel-operator-0562
branch
from
12a9ccb
to
04dfcc3
Compare
swiatekm
force-pushed
the
deps/upgrade-otel-operator-0562
branch
from
04dfcc3
to
d4f376d
Compare
| @@ -2464,8 +2464,7 @@ opentelemetry-operator: | |||
|
|
|||
| ## Specific for OpenTelemetry Operator chart values | |||
| admissionWebhooks: | |||
| failurePolicy: Fail | |||
| enabled: true | |||
| create: true | |||
There was a problem hiding this comment.
will this change affect helm chart upgrades in anyway? What changes would we need in the helm chart after this version of the operator?
There was a problem hiding this comment.
I don't think so. If someone disabled webhooks, they'll get an error and will need to set create: false instead of create: true. The other values I removed because we were using defaults anyway.
There was a problem hiding this comment.
changes to CRD handling that will require changes on our end as well.
ok, what about the upcoming changes mentioned here. Is there a breaking change in the operator that we should be tracking to upgrade to the next version?
There was a problem hiding this comment.
Operator Helm Chart v0.57.0 moves CRDs to templates. This effectively makes it impossible for us to use them, as we need to create an OpenTelemetryCollector CR during installation. We should move this discussion to an issue if you want to go into details, as it's not really related to this PR.
This is the last version before changes to CRD handling that will require changes on our end as well.
Checklist