You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This only happens when using the prometheus adapter which serves the custom.metrics.k8s.io/v1beta1 API on 1.27.
It looks like the v0.26 client-go cannot handle api resources with nil group/version in convertAPIRsource() which custom.metrics.k8s.io/v1beta1 is serving. client-go was made to be more resilient when receiving these types of malformed responses in 1.27.
What did you expect to happen:
I expect for sonobuoy to run on Kubernetes 1.27 when there are custom.metrics.k8s.io/v1beta1 resources created.
Anything else you would like to add:
Updating the go-client in this project to 0.27.x as proposed in this PRshould resolve this issue.
OS (e.g. from /etc/os-release): Ubuntu 22.04.2 LTS
Sonobuoy tarball (which contains * below)
The text was updated successfully, but these errors were encountered:
rrpolanco
changed the title
Sonobuoy panics with nil pointer dereference on Kubernetes 1.27 and prometheus adapter serving custom.metrics.k8s.io/v1beta1
Sonobuoy panics with nil pointer dereference on Kubernetes 1.27 when prometheus adapter serves custom.metrics.k8s.io/v1beta1 resources
May 1, 2023
What steps did you take and what happened:
Installed
sonobuoy
and ransonobuoy run --mode quick
and received this panic:This only happens when using the prometheus adapter which serves the
custom.metrics.k8s.io/v1beta1
API on 1.27.It looks like the v0.26 client-go cannot handle api resources with
nil
group/version in convertAPIRsource() whichcustom.metrics.k8s.io/v1beta1
is serving.client-go
was made to be more resilient when receiving these types of malformed responses in 1.27.What did you expect to happen:
I expect for
sonobuoy
to run on Kubernetes 1.27 when there arecustom.metrics.k8s.io/v1beta1
resources created.Anything else you would like to add:
Updating the go-client in this project to 0.27.x as proposed in this PR should resolve this issue.
Environment:
v0.56.16
kubectl version
):/etc/os-release
):Ubuntu 22.04.2 LTS
The text was updated successfully, but these errors were encountered: