In Red Hat OpenShift GitOps, which is based on ArgoCD, the deployment process is centered around Git repositories. The framework typically uses at least two repositories:
Application Repository – Contains the source code, manifests, and configurations for the application itself.
Environment Configuration Repository (Correct Answer) – Stores Kubernetes/OpenShift manifests, Helm charts, Kustomize overlays, or other deployment configurations for different environments (e.g., Dev, Test, Prod).
This separation of concerns ensures that:
Developers manage application code separately from infrastructure and deployment settings.
GitOps principles are applied, enabling automated deployments based on repository changes.
The Environment Configuration Repository serves as the single source of truth for deployment configurations.
Why the Other Options Are Incorrect?Option
Explanation
Correct?
A. Nexus
❌ Incorrect – Nexus is a repository manager for storing binaries, artifacts, and dependencies (e.g., Docker images, JAR files), but it is not a GitOps repository.
❌
B. Ansible configuration
❌ Incorrect – While Ansible can manage infrastructure automation, OpenShift GitOps primarily uses Kubernetes manifests, Helm, or Kustomize for deployment configurations.
❌
D. Maven
❌ Incorrect – Maven is a build automation tool for Java applications, not a repository type used in GitOps workflows.
❌
Final Answer:✅ C. Environment configuration
Red Hat OpenShift GitOps Documentation
IBM Cloud Pak for Integration and OpenShift GitOps
ArgoCD Best Practices for GitOps
IBM Cloud Pak for Integration (CP4I) v2021.2 Administration References:
Submit