Repository navigation
Conversation
…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 documentation updates
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #2245
With fine-grained kubelet authorization (on by default since 1.33, GA in 1.36) the kubelet checks
/podsagainstnodes/podsand only falls back tonodes/proxy. Fluent Bit's Kubernetes filter withUse_Kubelet Ononly calls/pods, so the Fluent Bit ClusterRole now always getsnodes/podsnext tonodes/proxy, and the newkubeletFineGrainedAuthzfield on the fluentbit/FluentbitAgent spec leavesnodes/proxyout of it. It's opt-in so clusters without the feature keep working.The operator's own ClusterRole gets
nodes/podstoo, since it can only grant what it has. It keepsnodes/proxyfor 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.