kubernetes-sigs / kubernetes-sigs/kustomize

globbing/wildcards in "resources" field

Open
#119 60 comments 116 reactions 0 assignees View on GitHub
help wanted kind/feature lifecycle/frozen needs-triage
Dominant language
Go
Stars
12.2k
Forks
2.4k
Avg merge
2d 14h
Merged PRs (30d)
25

Description

It looks like if I have tens of YAML files in a directory, my kustomization.yaml will exhaustively list them like this:

```yaml
resources:
- secret.yaml
- service.yaml
- deployment.yaml
```

It feels like a bit inconvenience. Is it possible to use globs (i.e. `**.yaml`) for this field? (Skaffold does support this and it's helpful.)

I think if I use kustomize and add new YAML files, aside from `kubectl apply -R -f .dir` working out of the box, I now have to go back and edit kustomization.yaml for it to work (in other words: two places to update).

Contributor guide

Open the contributing guide

Research direction

The issue identifies the resources field in kustomization.yaml but names no source file, test, or entry point. Start by locating the resources-field implementation and its existing tests, then define done as tested support for the requested recursive YAML glob behavior without breaking explicit resource lists.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.