Skip to content

feat(fluentbit): grant nodes/pods for the kubelet and allow dropping nodes/proxy - #2378

Open
cvas22 wants to merge 1 commit into
kube-logging:masterfrom
cvas22:feat/2245-kubelet-fine-grained-authz
Open

cvas22 wants to merge 1 commit into
kube-logging:masterfrom
cvas22:feat/2245-kubelet-fine-grained-authz

Conversation

@cvas22

@cvas22 cvas22 commented Nov 15, 2026

Copy link
Copy Markdown

Fixes #2245

With fine-grained kubelet authorization (on by default since 1.33, GA in 1.36) the kubelet checks /pods against nodes/pods and only falls back to nodes/proxy. Fluent Bit's Kubernetes filter with Use_Kubelet On only calls /pods, so the Fluent Bit ClusterRole now always gets nodes/pods next to nodes/proxy, and the new kubeletFineGrainedAuthz field on the fluentbit/FluentbitAgent spec leaves nodes/proxy out of it. It's opt-in so clusters without the feature keep working.

The operator's own ClusterRole gets nodes/pods too, since it can only grant what it has. It keeps nodes/proxy for now because it still has to grant it to Fluent Bit when the new field isn't set.

I regenerated the CRDs, the manager role and the CRD docs, and added a unit test for the three cases of the Fluent Bit ClusterRole.

…nodes/proxy

With fine-grained kubelet authorization the kubelet checks the /pods
endpoint against nodes/pods before falling back to nodes/proxy. Grant
nodes/pods to the Fluent Bit and operator roles when Use_Kubelet is on,
and add kubeletFineGrainedAuthz to leave nodes/proxy out of the Fluent
Bit role on clusters that have it.

Signed-off-by: Srinivas Chippagiri <cvas22@gmail.com>
@promptless-for-oss

Copy link
Copy Markdown

Promptless documentation updates

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Use fine-grained Kubelet API authorization

2 participants