-
Notifications
You must be signed in to change notification settings - Fork 506
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
[collector] Remove default collector image #1148
[collector] Remove default collector image #1148
Conversation
|
||
As part of working towards using the [OpenTelemetry Collector Kubernetes Distro](https://github.com/open-telemetry/opentelemetry-collector-releases/tree/main/distributions/otelcol-k8s) by default, the chart now requires users to explicitly set an image repository and command name. If you are already explicitly setting an image repository and command name this breaking change does not affect you. | ||
|
||
If you are using a OpenTelemetry Community distribution of the Collector we recommend you use `otel/opentelemetry-collector-k8s`, but carefully review the [components included in this distribution](https://github.com/open-telemetry/opentelemetry-collector-releases/blob/main/distributions/otelcol-k8s/manifest.yaml) to make sure it includes all the components you use in your configuration. In the future this distribution will become the default image used for the chart. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why are we looking to move away from the contrib distribution in the helm chart?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
contrib really isn't meant to be run in a production setting (doc). Contrib contains every component with stability greater than or equal to alpha, which means it probably has a lot of stuff the average user doesn't need. This opens up a potential attack vector if there's a vuln in one of said components that users are unknowingly pulling in. It also means that the overall image size is much larger than you may need which would result in worse first-pull latency. There are a few other reasons that are documented around, but these are the two biggest IMO.
* Remove default collector image * fix command * regen examples * Remove command name restriction * Adding warning
Works towards #1135
This PR removes the default
image.repository
andcommand.name
from the collector chart so that installs/upgrades fail for users depending on the previously setcontrib
image.Adds a new section to UPGRADING.md to guide users through this failure.