Open mateimicu opened 11 months ago
Extra loggs
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x2 addr=0x0 pc=0x104671f3c]
goroutine 60 [running]:
github.com/mateimicu/kdiscover/internal/aws.(*EKSClient).detailCluster(0x140004baae0, {0x140007b2318, 0x12})
/.../kdiscover/kdiscover/internal/aws/eks.go:95 +0x4dc
github.com/mateimicu/kdiscover/internal/aws.(*EKSClient).GetClusters.func1(0x14000160180, 0x1)
/.../kdiscover/kdiscover/internal/aws/eks.go:44 +0x4e0
github.com/aws/aws-sdk-go/service/eks.(*EKS).ListClustersPagesWithContext(0x1400000e280, {0x104be9d70, 0x140001ac008}, 0x1400061e6f0, 0x1400019c450, {0x0, 0x0, 0x0})
/home/runner/go/pkg/mod/github.com/aws/aws-sdk-go@v1.44.57/service/eks/api.go:2344 +0x14c
github.com/aws/aws-sdk-go/service/eks.(*EKS).ListClustersPages(0x1400000e280, 0x1400061e6f0, 0x1400019c450)
/home/runner/go/pkg/mod/github.com/aws/aws-sdk-go@v1.44.57/service/eks/api.go:2318 +0x60
github.com/mateimicu/kdiscover/internal/aws.(*EKSClient).GetClusters(0x140004baae0, 0x140001827e0)
/.../kdiscover/kdiscover/internal/aws/eks.go:33 +0xc0
created by github.com/mateimicu/kdiscover/internal/aws.getEKSClusters
/.../kdiscover/kdiscover/internal/aws/eks_cluster.go:73 +0x2ac
Describe the bug When a cluster is still creating in AWS, there is a panic if you run the CLI.
I think this is because some Cluster information is not present but we assume it is.
Environment:
kdiscover version
{"Version":"0.1.5","Commit":"933c61215acc55d4b90535541541a960f2943408","Date":"2022-07-18T23:32:14Z"}
To Reproduce Steps to reproduce the behavior:
kdiscover aws list
Expected behavior The list found clusters.