Originally posted on Github: https://github.com/k-orc/openstack-resource-controller/issues/579

While running kuttl tests, we sometimes get warning about object detected with no GVK Kind. For example running the volume-create-minimal test:
❯ E2E_KUTTL_DIR=internal/controllers/volume/tests E2E_KUTTL_TEST="create-minimal" make test-e2e

1. go test ./test/e2e/ -v -ginkgo.v
   ./hack/e2e.sh
   2025/11/21 09:05:31 kutt-test config testdirs is overridden with args: [ internal/controllers/volume/tests ]
   === RUN kuttl
   harness.go:459: starting setup
   harness.go:254: running tests using configured kubeconfig.
   harness.go:277: Successful connection to cluster at: https://127.0.0.1:35897
   harness.go:362: running tests
   harness.go:74: going to run test suite with timeout of 240 seconds for each step
   harness.go:374: testsuite: internal/controllers/volume/tests has 6 tests
   === RUN kuttl/harness
   === RUN kuttl/harness/volume-create-minimal
   === PAUSE kuttl/harness/volume-create-minimal
   === CONT kuttl/harness/volume-create-minimal
   logger.go:42: 09:05:31 | volume-create-minimal | Ignoring README.md as it does not match file name regexp: ^(\d+)-(?:[^\.]+)(?:\.yaml)?$
   2025/11/21 09:05:31 object detected with no GVK Kind for path /home/martin/dev/openshift/openstack-resource-controller/internal/controllers/volume/tests/volume-create-minimal/00-assert.yaml
   2025/11/21 09:05:31 object detected with no GVK Kind for path /home/martin/dev/openshift/openstack-resource-controller/internal/controllers/volume/tests/volume-create-minimal/00-create-resource.yaml
   logger.go:42: 09:05:31 | volume-create-minimal | Creating namespace: kuttl-test-proper-eft
   logger.go:42: 09:05:31 | volume-create-minimal/0-create-resource | starting test step 0-create-resource
   logger.go:42: 09:05:31 | volume-create-minimal/0-create-resource | running command: [kubectl create secret generic openstack-clouds --from-file=clouds.yaml=/tmp/tmp.qtvKYym4Yf/clouds.yaml --namespace kuttl-test-proper-eft]
   logger.go:42: 09:05:31 | volume-create-minimal/0-create-resource | secret/openstack-clouds created
   logger.go:42: 09:05:31 | volume-create-minimal/0-create-resource | Volume:kuttl-test-proper-eft/volume-create-minimal created
   logger.go:42: 09:05:51 | volume-create-minimal/0-create-resource | test step completed 0-create-resource
   logger.go:42: 09:05:51 | volume-create-minimal/1-delete-secret | starting test step 1-delete-secret
   logger.go:42: 09:05:51 | volume-create-minimal/1-delete-secret | running command: [kubectl delete secret openstack-clouds --wait=false --namespace kuttl-test-proper-eft]
   logger.go:42: 09:05:51 | volume-create-minimal/1-delete-secret | secret "openstack-clouds" deleted
   logger.go:42: 09:05:51 | volume-create-minimal/1-delete-secret | test step completed 1-delete-secret
   logger.go:42: 09:05:51 | volume-create-minimal | volume-create-minimal events from ns kuttl-test-proper-eft:
   logger.go:42: 09:05:51 | volume-create-minimal | Deleting namespace: kuttl-test-proper-eft
   === NAME kuttl
   harness.go:403: run tests finished
   harness.go:510: cleaning up
   harness.go:567: removing temp folder: ""
   • • PASS: kuttl (39.23s)
     • PASS: kuttl/harness (0.00s)
     • PASS: kuttl/harness/volume-create-minimal (39.20s)
       PASS

This is due to blank lines at the top of the test, most likely an artifact of the scaffolding tool.
If we find a way, it would also be good to get rid of the Ignoring README.md as it does not match file name regexp warning.