Hi Team, I wanted to ask Fluent bit compatibility ...
# fluent-bit
y
Hi Team, I wanted to ask Fluent bit compatibility with Kubernetes Version. I couldn't find any official doc mentioned about it. So I posted a question to github. Could please someone help answer it? https://github.com/fluent/fluent-bit/discussions/10860, thanks🙏
p
Short answer, yes it is compatible 🙂 Longer answer is that if you're using Linux then there's only a few things Fluent Bit will be reliant on: • Running the container, if your K8S distribution cannot do this then you have bigger problems. • Mounting kubelet log files into the container to tail. • Using the K8S rest API to get pod metadata, been stable for a while! You may be using the systemd input plugin in which case you need compatible versions on the host and in the container but typically it's backwards compatible. You may also be using the kubernetes event plugin but again this is just the rest API. The helm chart has various configurable options so you may be using a feature that requires a specific K8S version, e.g. PSP, but that's fully configurable by you. It's easy enough to test your usage though and I'd always encourage that rather than relying on random internet people 🙂
If you're using Windows worker nodes then I don't relish your job but it should work too, again it's using the rest API and files so you just need to configure it correctly. I think there may be some more host -container requirements for Windows but honestly I don't use it
Your specific K8S distribution, not version to be clear, may also have it's own ideas about things, e.g. open shift and it's SCC but again that's configurable and supported by the helm chart. Just saying a K8S version is supported honestly would not always help because of the opinionated distributions of K8S out there. Always test yourself, submit docs or other PRs to improve OSS, or talk to an enterprise provider to do it for you: https://fluentbit.io/enterprise/ I work for one and we do test against both versions of K8S and distributions.
Saying that, I'll see if I can add a simple kind matrix to verify some versions automatically in CI surely
y
Pat, thanks for the detailed explanation — that aligns with my understanding. Fluent Bit’s core functionality is largely independent of the Kubernetes version, and the Kubernetes REST API has been stable for some time. I’m running Fluent Bit on a VMware Kubernetes Service cluster and will definitely perform downstream testing against the new Kubernetes version in my test environment. However, If upstream could add some simple automation in CI, that will be even better.
p
We do have it commercially but yeah ultimately any issues we have found in the past have been less to do with vanilla K8S and instead some specific distribution "thing" - or more commonly a change in K8S or the output deployment you are using that causes the output to fail which is not really Fluent Bit 🙂
There's also the question of "what versions to test", e.g. EKS typically has a long tail of versions and then others can take bleeding edge K8S. However, I'll see what I can do with some sane defaults 🙂
No self signed/custom TLS, just simple tail->kubernetes->null output might be best too. Can't test every single combination of inputs/filters/outputs plus all their options, e.g. for Kubernetes filter you can also talk to the kubelet instead of the API, etc.
y
In my test environment, we’ll ensure testing for the latest n-3 cluster versions. For example, if the latest Kubernetes version is 1.34, we’ll test versions 1.31 through 1.34. And we'll use Kubernetes filter instead of the kubelet.
Just a suggestion. you can decide the strategy for upstream. As you mentioned, it’s not possible to test all combinations.
p
Unfortunately n-x usually fails for AWS unless it's a big x which then takes time/money on the OSS compute to test. But yeah, something like that