What is the recommended directory structure for an application named myapp in a kustomize project?

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

What is the recommended directory structure for an application named myapp in a kustomize project?

Explanation:
In a kustomize project, you keep the common resources that apply to all environments in a base, and you create environment-specific modifications in overlays. The base holds the shared manifests (Deployment, Service, ConfigMap, etc.), while each overlay (for production, staging, dev) applies patches or its own config on top of that base. This approach lets you reuse the same core definitions and only change what's different per environment, making deployments consistent and easier to manage. So for an app named myapp, the recommended structure is to have myapp/base for the common manifests and myapp/overlays with subfolders like production, staging, and dev that reference the base and provide the environment-specific tweaks. The other options lack a base, use nonstandard layouts, or place resources in unrelated folders, which undermines reuse and clean environment separation.

In a kustomize project, you keep the common resources that apply to all environments in a base, and you create environment-specific modifications in overlays. The base holds the shared manifests (Deployment, Service, ConfigMap, etc.), while each overlay (for production, staging, dev) applies patches or its own config on top of that base. This approach lets you reuse the same core definitions and only change what's different per environment, making deployments consistent and easier to manage. So for an app named myapp, the recommended structure is to have myapp/base for the common manifests and myapp/overlays with subfolders like production, staging, and dev that reference the base and provide the environment-specific tweaks. The other options lack a base, use nonstandard layouts, or place resources in unrelated folders, which undermines reuse and clean environment separation.

Subscribe

Get the latest from Passetra

You can unsubscribe at any time. Read our privacy policy