Gitops Jenkins Argocd Secure State Reconciliation

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

An enterprise is establishing a secure continuous integration and continuous delivery (CI/CD) architecture across Google Kubernetes Engine (GKE) clusters using Git, Jenkins, and a GitOps delivery controller. Corporate security policies require eliminating direct deployment access from CI runners to GKE clusters and prohibiting the use of individual human credentials for automated pipeline tasks.

How should the DevOps team design this pipeline to enforce automated state reconciliation and secure execution?

Configure Jenkins to commit built container images directly to the Git repository, and configure the GitOps controller to run with default unauthenticated public access.

Configure the in-cluster GitOps controller to trigger Jenkins webhook endpoints to pull raw binary artifacts and push them directly to GKE nodes via SSH.

Configure Jenkins to update deployment manifests in a dedicated Git configuration repository using a machine user token, and configure the in-cluster GitOps controller with credentials stored in a Kubernetes Secret to pull and reconcile the desired state.

Configure Jenkins to execute deployment scripts using kubectl apply directly against the GKE control plane by mounting individual developer personal access tokens into the Jenkins agent workspace.

Professional Cloud DevOps Engineer

Gitops Jenkins Argocd Secure State Reconciliation

Related questions