pixie-io
Provide some matrix or description about AMI compatibility in doc
Is your feature request related to a problem? Please describe. We are using Pixie installed on an EKS cluster which is based on k8s version 1.31. As the support for 1.31 from AWS will be ended at the end of November so we have updated to 1.34 recently. Along with that we also try to update the AMI version used for the node group. However after upgrade to the latest Bottlerocket AMI, there is an error "Failed to execute script Compiler error on line 33, column 22: Table 'http_events' not found.". Though we know this is potential a compatible issue according to the official doc, while there is no description about the compatibility with the latest image / Linux kernel version. It's not supported to set a specific version for Bottlerocket, so we tried several versions with AmazonLinux2023, and finally it works with a version based on k8s 1.32.
Describe the solution you'd like If there is a matrix or description about the image / Linux kernel version compatibility in the doc, probably it would be more straightforward for the user to understand which version could be used directly.
Describe alternatives you've considered Another alternative may be to support all the major image / Linux kernel versions by default, keep Pixie update along with latest versions accordingly, but it's definitely a cost of resources.
Additional context Add any other context or screenshots about the feature request here.
Hi @bhu-talendbj, thanks for filing this bug report.
Our goal is to be compatible with the majority image and Linux kernel versions by default, but our team runs Pixie primiarly on GKE Ubuntu and COS (container OS) nodes. Amazon Linux and Bottlerocket aren't distros we test regularly and they are known to require installing the distro provided linux header package (sudo dnf install -y kernel-headers-$(uname -r) kernel-devel-$(uname -r))
Can you please provide the PEM pod logs or the zip file created by px collect-logs?
Hi @ddelnano , thanks for the response.
As we have already switched back to the compatible version, so I don't have the logs now... probably I can provide the PEM pod logs during next update ( I'm on Windows so px command doesn't work ).
Talking about the workaround I also noticed it in another ticket which was filed this year earlier, however it doesn't work in our case... I was doubting a compatibility issue with a Linux kernel version equal to or higher than 6.10 if I remember.
Not sure whether you could help provide the image / kernel version for the GKE Ubuntu or COS if possible, then we can refer to it or even consider about the switch of images.