Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
File paths may not step up. #693
Currently, all file paths mentioned in a kustomization file must be defined relative to the location of the kustomization file.
This allows (e.g.) the following fishing attack. Someone writes a kustomization with a configmap generator that reads data from
To prevent this, the following restriction is added:
All files paths mentioned in a kustomization file (resources, patches, config data) must refer to files in or below
Bases are not subject to this, and may be specified as living in sibling directories (or in remote URLs). A base can be viewed as an “import”, and its data files are subject to the same restriction but relative to that base.
Symlinks will be purged (e.g. via