Missing objects in kustomize build output

[faust64]

What happened?

Colleague of mine is introducing some new CRDs & controllers .... and found about some edge case.

His new objects are named like SomethingAccessList.
They are missing from kustomize build outputs.

Hint: probably this: https://github.com/kubernetes-sigs/kustomize/blob/master/api/resource/factory.go#L193

Arguably ... yes, those "List" "usually" relates to the "listKind" we would find on custom resources definitions, ... eg:

  group: tekton.dev
  names:
    categories:
    - tekton
    - tekton-pipelines
    kind: PipelineRun
    listKind: PipelineRunList
    plural: pipelineruns
    shortNames:
    - pr
    - prs
    singular: pipelinerun

Still I'm not aware of any rule preventing usage of such a suffix, actually naming objects ....
.. and as far as I see: refactoring that snippet as an helm Chart: helm is able to produce the expected output.

Then that's a bug?

What did you expect to happen?

objects showing in stdout, when I "kustomize build ."

How can we reproduce it (as minimally and precisely as possible)?

# kustomization.yaml
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
resources:
- resources.yaml

# resources.yaml
apiVersion: something.example.com/v1
kind: SomethingAccessList
metadata:
  name: test-object

Expected output

apiVersion: something.example.com/v1
kind: SomethingAccessList
metadata:
  name: test-object

Actual output

no output given. kustomize build exits with 0.

Kustomize version

5.4.0

Operating system

None

[k8s-ci-robot]

This issue is currently awaiting triage.

SIG CLI takes a lead on issue triage for this repo, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[alianos-]

seems like a duplicate of #5042