Owner access warning is meaningless on Kubernetes?

[scholzj]

Description

The FileBasedTokenProvider issues a warning when the token is not accessible only by the user. However, that is hard to achieve on Kubernetes in many cases. The token volume is mounted under a root by Kubernetes and we cannot really change its ownership. So I wonder if the warning really makes sense. Or if we should at least have some flag to suppress it.

2026-08-26 17:50:48 WARN  [main] FileBasedTokenProvider:36 - Permissions on token file should only give access to owner [/var/run/secrets/strimzi.io/token]

[mstruk]

I agree, it makes sense to suppress this warning on Kubernetes. We can introduce a config option that when set would suppress it in order to still have the warning by default when used outside the Kubernetes environment.