Skip to content

Guard the empty-file case when loading CRDs - #6209

Open
arpitjain099 wants to merge 1 commit into
kubernetes-sigs:masterfrom
arpitjain099:fix/empty-crd-file-panic
Open

Guard the empty-file case when loading CRDs#6209
arpitjain099 wants to merge 1 commit into
kubernetes-sigs:masterfrom
arpitjain099:fix/empty-crd-file-panic

Conversation

@arpitjain099

Copy link
Copy Markdown
Contributor

A crds: entry that points at a zero-byte file crashes the build:

panic: runtime error: index out of range [0] with length 0

makeNameToApiMap looks at the first byte to decide between JSON and YAML:

if content[0] == '{' {
    err = json.Unmarshal(content, &result)
} else {
    err = yaml.Unmarshal(content, &result)
}

kustomization.yaml crds: takes relative paths, kusttarget.go hands each file to LoadConfigFromCRDs, and nothing checks the contents are non-empty on the way. So an empty file in that list panics rather than contributing no CRDs. A whitespace-only file does not trip it, since a space just routes to the YAML branch, which is what made this specific to zero-length files.

The fix uses the same shape the repo already uses in kyaml/openapi/openapi.go:

if len(content) > 0 && content[0] == '{' {

An empty file then goes to yaml.Unmarshal([]byte{}), which returns a nil map and no error, so it contributes nothing.

Test added next to TestLoadCRDs. It panics on master and passes with the change; go test ./internal/accumulator/ is green.

makeNameToApiMap indexed content[0] to decide between JSON and YAML, so
a crds entry pointing at a zero-byte file crashed kustomize build with
an index out of range instead of contributing no CRDs. The length check
matches the existing idiom in kyaml/openapi.

Signed-off-by: Arpit Jain <arpitjain099@gmail.com>
@kubernetes-prow kubernetes-prow Bot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Aug 1, 2026
@kubernetes-prow

Copy link
Copy Markdown
Contributor

Hi @arpitjain099. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Tip

We noticed you've done this a few times! Consider joining the org to skip this step and gain /lgtm and other bot rights. We recommend asking approvers on your previous PRs to sponsor you.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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-sigs/prow repository.

@kubernetes-prow kubernetes-prow Bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Aug 1, 2026
@koba1t

koba1t commented Aug 1, 2026

Copy link
Copy Markdown
Member

/ok-to-test

@kubernetes-prow kubernetes-prow Bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Aug 1, 2026

@saitejabandaru-in saitejabandaru-in left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! This elegantly handles the empty file edge case and prevents the slice bounds out of range panic. The unit test also properly covers this scenario.

@saitejabandaru-in saitejabandaru-in left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! This perfectly guards against the out-of-bounds index on empty files.

@kubernetes-prow

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: arpitjain099, saitejabandaru-in
Once this PR has been reviewed and has the lgtm label, please assign koba1t for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants