Kustomize
Hard
Generation
A configMapGenerator entry has files: [config/app.properties]. Which key holds the file's content?
Select your answer:
Show answer and explanation
Answer: app.properties, the file's name
Explanation
Each file becomes one key named after the file. Write files: [settings=config/app.properties] to choose the key yourself, or use envs to turn each KEY=value line of a file into its own key.
More hard Kustomize questions
- labels sets includeSelectors: false and includeTemplates: true. Where do the labels end up?
- What does the openapi field in a kustomization.yaml provide?
- Two bases included by one overlay both define a ConfigMap named settings in the same namespace. What happens?
- A JSON 6902 patch adds an annotation named example.com/owner. How is that key written in the patch path?
- Why can a kustomization build with the kustomize CLI but fail with kubectl apply -k?
- Why does generatorOptions.immutable: true work well with Kustomize's default hash suffix?