Make the command name consistent across images

[dmitryax]

Currently, we use different commands for different images.

• /otelcol for the core image
• /otelcol-contrib for the contrib image (/otecontribcol if built with make docker-otelcontribcol)
• /otelcol-k8s for k8s image

Is there any value to having a unique command in each distro?

If not, we could use /otelcol consistently for every image.

We can make this change gradually and support both old and new names for some time.

Initially brought in open-telemetry/opentelemetry-helm-charts#1148 (comment)

[mx-psi]

cc @jpkrohling

[codeboten]

The different configuration files is also confusing..

[codeboten]

As discussed in 17-Apr-2024 - The same command could just be a symlink to ensure the change isn't breaking backwards compatibility

[codeboten]

Opened a separate issue for configuration consistency: #530

[mx-psi]

I pinged Juraci because I think this was intentional (see #59 (comment))

[TylerHelmuth]

@dmitryax if we wanted to take advantage of the entrypoint in the helm chart like @jaronoff97 mentioned we'll need to update the container to use args instead of command.

[TylerHelmuth]

Created open-telemetry/opentelemetry-helm-charts#1149 for the helm chart.

[jpkrohling]

The idea behind both the config files being at different locations, and the binary names being different, is that different distributions could be installed via OS packages (rpm/deb) without interfering. From here, we have a few options:

• continue allowing multiple distributions to be installed on the same system independently
• make them all providers of a capability, like the Provides keyword for RPM, meaning that only one such package is allowed at any given time