-
Notifications
You must be signed in to change notification settings - Fork 706
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error and panic in kubeapps-internal-apis deployment #6513
Comments
Hi @sde-melo . Can you please include the rest of the lines after the panic? It will help us see exactly where the code is panicking (since we're not seeing this in our own environments, it will help us know how we can reproducue it). Thanks! |
Hi @absoludity
|
For now I am stuck in 2.6.2. I have tried all upper versions and I encouter the same crash. However, if I force the 2.6.2-debian-11-r0 tag for the kubeapps-internal-kubeappsapis image in the latest helm chart, I get rid of the error. |
Thanks @sde-melo . So it is an error when Kubeapps tries to initialise a standard piece for interacting with the Kubernetes infrastructure (a REST mapper, which maps what APIs are available in the k8s api server). Kubeapps handles any error as it should there, but the 3rd party code itself isn't. Digging down, I see lots of OSS projects had this issue in the past few months (for e.g. look at this report and the links to it) which point back to an error in the Kubernetes client code itself at: kubernetes/kubernetes#116603 . So the reason that you're seeing this issue while our CI and environments don't, is because of an extra aggregated API you have running on your k8s API server which is returning nil GroupVersionKind's (possibly the metrics server?). Anyway, they have already updated and released the fix, in k8s.io/client-go 1.26.4, which we already updated to, but not before the 2.8.0 release. So you should be able to verify that your problem is also fixed with the latest kubeapps-apis development image (though don't run your prod systems with that since we've not QA'd it through our release process - just wait for the 2.8.1 kubeapps release or similar). Thanks for the extra information! EDIT: or by removing/upgrading the aggregate APIs that are returning nil GroupVersionKind's, but I'm guessing that's less practical :) |
Thanks for the detailed explanations @absoludity! I'll wait for the 2.8.1 release then. |
Describe the bug
During the deployment of kubeapps on a Kubernetes cluster using a Helm chart with default values, an error and panic occur, resulting in a segmentation violation. The deployment process fails, and the application does not start as expected.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The kubeapps-apis should deploy successfully without any errors or panics. The application should start and be ready to serve requests.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: