Skip to content

Always set LINKERD2_PROXY_INBOUND_PORTS when injecting pods #7816

@mateiidavid

Description

@mateiidavid

Currently, the injector will set a LINKERD2_PROXY_INBOUND_PORTS environment variable whenever the pod spec has exposed its container ports. This environment variable is used to discover policies. If the environment variable is not set, we error out: No inbound ports specified via LINKERD2_PROXY_INBOUND_PORTS.

If a port has not been explicitly documented in the pod spec, we will use the default policy for the cluster (or parent object). To keep the output clear from errors, we should probably always set the environment variable; when no ports are exposed, we can pass in an empty string.

See discussion for more information.

Discussed in #7765

Originally posted by karlparry February 2, 2022
We have a few pods that have no inbound listening ports. When these run we get this error in the Proxy log.

Is there anyway to stop these messages appearing in the Proxy logs?

ERROR ThreadId(01) linkerd_app::env: No inbound ports specified via LINKERD2_PROXY_INBOUND_PORTS

Using Linkerd version 2.11.X

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions