🐛 use fully qualified names for k8s resources

[imilchev]

We aren't using fully qualified names for the k8s resources when we request them from the API. This is causing issues when there is more than 1 resource that matches by name.

To reproduce the original problem start a fresh minikube instance and install a jobs crd:

kubectl apply -f https://raw.githubusercontent.com/crossplane-contrib/provider-aws/master/package/crds/batch.aws.crossplane.io_jobs.yaml

Then run cnspec scan k8s. You will see the following error:

cnspec scan k8s                                                  
→ loaded configuration from /Users/ivanmilchev/.config/mondoo/mondoo.yml using source default
→ using service account credentials
→ discover related assets for 1 asset(s)
x unable to create runtime for asset error="rpc error: code = Unknown desc = ambiguous kind \"jobs\". use one of these as the KIND disambiguate: [jobs.v1.batch, jobs.v1alpha1.batch.aws.crossplane.io]" asset=
Asset: 
-------

error: rpc error: code = Unknown desc = ambiguous kind "jobs". use one of these as the KIND disambiguate: [jobs.v1.batch, jobs.v1alpha1.batch.aws.crossplane.io]


Scanned 1 asset

When using the fully qualified names, the issue is resolved.

[github-actions]

Test Results

3 073 tests  ±0   3 072 ✅ ±0   1m 21s ⏱️ -2s
  363 suites ±0       1 💤 ±0 
   27 files   ±0       0 ❌ ±0 

Results for commit ed0f3d0. ± Comparison against base commit bc3c52d.

♻️ This comment has been updated with latest results.