Describe the bug
if i try to run a query that's targeted to, for example, a single pod on the k8s transport, i get a bunch of errors
cnquery run k8s -c "k8s.pod { podSpec['volumes'] == null || podSpec['volumes'].all(_['hostPath']['path'] != '/var/run/docker.sock') }
… dquote ❯ "
→ discover related assets for 1 asset(s)
→ use cluster name from kube config cluster-name=minikube
→ discovery option auto is used. This will detect the assets: cluster, jobs, cronjobs, pods, statefulsets, deployments, replicasets, daemonsets
→ resolved assets resolved-assets=26
Query encountered errors:
failed to create resource 'k8s.pod': cannot use resource without specifying id or name/namespace
k8s.pod: no data available
Query encountered errors:
failed to create resource 'k8s.pod': could not find resource
k8s.pod: no data available
Query encountered errors:
failed to create resource 'k8s.pod': could not find resource
k8s.pod: no data available
Query encountered errors:
failed to create resource 'k8s.pod': could not find resource
k8s.pod: no data available
k8s.pod: {
podSpec[volumes] == null || <ref>: true
}
k8s.pod: {
podSpec[volumes] == null || <ref>: true
}
}
k8s.pod: {
podSpec[volumes] == null || <ref>: true
}
k8s.pod: {
podSpec[volumes] == null || <ref>: true
}
k8s.pod: {
podSpec[volumes] == null || <ref>: true
}
Query encountered errors:
failed to create resource 'k8s.pod': could not find resource
k8s.pod: no data available
Query encountered errors:
failed to create resource 'k8s.pod': could not find resource
this is confusing and ugly!
it seems to be because we are trying to run a query intended for pod, on the main k8s transport
Describe the bug if i try to run a query that's targeted to, for example, a single pod on the k8s transport, i get a bunch of errors
this is confusing and ugly!
it seems to be because we are trying to run a query intended for pod, on the main k8s transport