How to define a pod to not have any inbound ports without an error in the log?

[karlparry]

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

[mateiidavid]

Hey @karlparry, we use the env variable to discover authorization policies (see: implementation ticket). We discussed the usage of containerPorts in #7640.

Anyway, looking through the code, it seems that when the env variable isn't set, we'll log out a warn message and use a default policy. Further in the code, when we try to resolve the address for the policy controller, we seem to check the ports again and log an error message if they're missing. AFAIK based on this, the error shouldn't have a big impact. Might be some room here to turn it into a warn, or something similar, but I'm not (personally) sure of what the implications would be.

Hope this helps? Let me know what you think.

[karlparry]

Thanks for the response. That is exactly what I saw when I read the code, but didn't want to assume.
You are right, the error has no impact, and only appears once on start up so it isn't a problem at all.

[olix0r]

@mateiidavid is correct. It would probably be best if the injector always set the environment variable, even if empty, so that the proxy wouldn't log an error. The proxy's log message is mostly intended to indicate that an expect configuration wasn't set (i.e. if an older injector is trying to configure a newer proxy).

[DrFaust92]

Im encountering this as well, is it worth to open a feature request/submit a PR to change this to WARN instead of error?