You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On my K8s cluster, I'm using fluent-bit 1.8.11 container and I like to enable parameter Use_Kubelet in a Kubernetes filter. However, Kubelet configured on my machines is accessible using a server IP address of one of the interface (port 10250). As fluent-bit uses hardcoded api_host (127.0.0.1), all requests fail. I tried to modify listening interface used by Kubelet but I could only listen on all interfaces (0.0.0.0). For security reason, I do not want to do this.
Unless it is possible to have 2 listening interfaces for Kubelet (I didn't manage this), would it be possible to add parameter to configure the kubelet host?
Or will be there another solution ?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
On my K8s cluster, I'm using fluent-bit 1.8.11 container and I like to enable parameter Use_Kubelet in a Kubernetes filter. However, Kubelet configured on my machines is accessible using a server IP address of one of the interface (port 10250). As fluent-bit uses hardcoded api_host (127.0.0.1), all requests fail. I tried to modify listening interface used by Kubelet but I could only listen on all interfaces (0.0.0.0). For security reason, I do not want to do this.
Unless it is possible to have 2 listening interfaces for Kubelet (I didn't manage this), would it be possible to add parameter to configure the kubelet host?
Or will be there another solution ?
Thanks for your help
Beta Was this translation helpful? Give feedback.
All reactions