[extension/k8sobserver] discover endpoints for sidecar-type initcontainers

[jinja2]

Component(s)

extension/observer/k8sobserver

Is your feature request related to a problem? Please describe.

Running initContainer as sidecars is beta in k8s v1.29. These sidecar containers (initContainers with restartPolicy = Always) can expose ports, receive traffic, etc. similar to the main containers in pod and run for the entirety of pod's lifecycle. I think it makes sense to update the k8sobserver to discover endpoints exposed by sidecar containers.

Describe the solution you'd like

The discovery mechanism in k8sobserver should iterate over initContainers and add any endpoints exposed by sidecar-type initContainers.

Describe alternatives you've considered

No response

Additional context

No response

[github-actions]

Pinging code owners:

• extension/observer/k8sobserver: @rmfitzpatrick @dmitryax

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

• extension/observer/k8sobserver: @rmfitzpatrick @dmitryax

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[github-actions]

This issue has been closed as inactive because it has been stale for 120 days with no activity.