In kustomize, where do you define the files to be built for a customization?

Unlock all questions

This demo includes only 20 questions. Upgrade to access hundreds of questions, flashcards, exam simulations, and disable ads.

Full question bankExam simulationsFlashcards
From $25.99Unlock all

Prepare for the Red Hat Openshift Developer EX288 Exam. Study with comprehensive quizzes and flashcards. Each question includes hints and explanations to enhance your understanding. Ace your exam with confidence!

Multiple Choice

In kustomize, where do you define the files to be built for a customization?

Explanation:
Kustomize builds are defined in a kustomization.yaml in your directory. This file declares which files to process by listing them under the resources section, along with any patches and other customization steps. The actual manifest files (such as deployment.yaml or secrets.yaml) live alongside, but kustomize uses the list in kustomization.yaml to know which files to build and transform. Fields like metadata or apiVersion belong to the manifests themselves and aren’t where you specify the set of files to include. So the place to define the files to be built for a customization is the kustomization.yaml.

Kustomize builds are defined in a kustomization.yaml in your directory. This file declares which files to process by listing them under the resources section, along with any patches and other customization steps. The actual manifest files (such as deployment.yaml or secrets.yaml) live alongside, but kustomize uses the list in kustomization.yaml to know which files to build and transform. Fields like metadata or apiVersion belong to the manifests themselves and aren’t where you specify the set of files to include. So the place to define the files to be built for a customization is the kustomization.yaml.

More Multiple Choice Questions
Subscribe

Get the latest from Passetra

You can unsubscribe at any time. Read our privacy policy