instrumenta / instrumenta/kubeval

Issues with Kustomization Files

Open
#232 3 comments 20 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
3.2k
Forks
227
PR merge metrics
No merged PRs in 30d

Description

Kustomization.yaml files currently throws errors when scanned. This may be expected but seeing some strange behavior with several of the switches when I try and ignore them.

Error I am seeing consistently:
ERR - path/kustomization.yaml: Missing 'metadata' key

Things tried to resolve missing metadata key:
--ignore-missing-schemas = Still results in above error
--skip-kinds Kustomization = Does not appear to be working, would be nice to have this work as there are a few types of possible names for these types of files.

Current Workaround:
--ignored-filename-patterns kustomization.yaml seems to be the only way to ignore these files.

example file for reference:
```
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
bases:
- github.com/argoproj/argo-cd/manifests/ha/cluster-install?ref=v1.5.2
```

Contributor guide

No contributing guide indexed for this repository

Research direction

Reproduce the reported error with the example Kustomization.yaml and compare --ignore-missing-schemas, --skip-kinds Kustomization, and --ignored-filename-patterns kustomization.yaml. Trace the scanner's handling of Kustomization files and these switches; done means the file no longer produces the metadata error or the documented ignore option works consistently.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
devops, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.