SIGSEGV: segmentation violation k8s.(*cluster).ClusterNameVersion #6643
Labels
kind/bug
Categorizes issue or PR as related to a bug.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
target/kubernetes
Issues relating to kubernetes cluster scanning
Discussed in #6637
Originally posted by corinz May 6, 2024
Description
I get a seg fault on the following command.
trivy k8s gke-primary-dv --kubeconfig .kubeconfig --report all
The cluster is a new/pretty vanilla GKE Autopilot cluster created using the GKE terraform module.
Here's a little clue. I have never seen the "name" show up as
n/a
in k9s. Seems related to the func throwing the error:ClusteNameVersion
... However, in the GKE console this cluster has a "name". What even is the cluster "name" anyway, if not some arbitrary name we assign to the context or cloud resource?There is a couple related bugs/discussions but they were merged last year. Since I am using a later version, it is appropriate to reopen e.g. #5621
Thanks for looking into this!
Desired Behavior
The scan works.
Actual Behavior
Reproduction Steps
Target
Kubernetes
Scanner
None
Output Format
None
Mode
None
Debug Output
Operating System
mac OS Sonoma 14.3
Version
Checklist
trivy image --reset
The text was updated successfully, but these errors were encountered: