▸case-01 I need an Argo CD manifest to deploy a Kubernetes web service from git repository 'https://github.com/example/webapp.git' targeting path 'deploy/prod' to the local cluster namespace 'web-prod'. I'm tempted to use a standard Deployment manifest directly or a custom CRD named GitOpsDeployment. Produce the exact official Argo CD Custom Resource definition. | pass→pass | 8,937 | 17,582 | +97% | 1 | 1 | 0% | 1,453 | 2,088 | +44% | 0 | 0 | — |
▸case-02 Create the syncPolicy configuration block for an Argo CD Application where changes in Git should automatically apply, and any manual drift in the cluster should be automatically reverted. Developers suggested setting automated: true as a simple boolean, but I need the full formal spec structure. | pass→pass | 8,005 | 9,674 | +21% | 1 | 1 | 0% | 1,374 | 1,849 | +35% | 0 | 0 | — |
▸case-03 We have a database migration Job that must complete before the main Application Deployment starts in Argo CD. I was told to put them in separate git repositories or use Kubernetes initializers. Provide the annotation needed on the Job metadata to ensure it runs in wave 1 before wave 2 deployment. | pass→pass | 8,175 | 9,696 | +19% | 1 | 1 | 0% | 1,530 | 1,841 | +20% | 0 | 0 | — |
▸case-04 Configure an Argo CD ApplicationSet to deploy the app 'payment-service' across three environments: dev, staging, and prod. Instead of copying three Application manifests, configure a list generator to template them dynamically. Show the ApplicationSet spec section. | fail→pass | 8,212 | 8,032 | -2% | 1 | 1 | 0% | 1,659 | 2,029 | +22% | 0 | 0 | — |
▸case-05 Create an Argo CD AppProject manifest named 'finance-tenant' that restricts deployments so applications in this project can ONLY pull manifests from 'https://github.com/org/finance-manifests.git' and deploy into the 'finance-*' namespaces on server 'https://kubernetes.default.svc'. Base models often put repository restrictions inside the Application object. | pass→pass | 7,764 | 7,453 | -4% | 1 | 1 | 0% | 1,480 | 1,941 | +31% | 0 | 0 | — |
▸case-06 When deploying an Argo CD Application, the target namespace 'analytics' does not exist yet. Instead of creating a separate Namespace manifest or pre-creating it manually via kubectl, configure the Argo CD sync options so Argo CD creates it automatically during sync. | pass→pass | 6,812 | 7,873 | +16% | 1 | 1 | 0% | 1,227 | 1,645 | +34% | 0 | 0 | — |
▸case-07 Write a Flux v2 GitRepository Custom Resource named 'podinfo' checking out the 'main' branch of 'https://github.com/stefanprodan/podinfo' every 5 minutes in namespace 'flux-system'. I'm considering using a standard Kubernetes ConfigMap to store the Git URL. | pass→pass | 11,206 | 10,773 | -4% | 1 | 1 | 0% | 1,829 | 2,119 | +16% | 0 | 0 | — |
▸case-08 Configure a Flux v2 Kustomization resource named 'podinfo-execution' that references a GitRepository source named 'podinfo', path './kustomize', synchronizing every 10 minutes, with pruning enabled. Make sure it targets the 'flux-system' namespace. | pass→pass | 7,178 | 4,523 | -37% | 1 | 1 | 0% | 1,138 | 1,357 | +19% | 0 | 0 | — |
▸case-09 Create a Flux v2 HelmRelease resource named 'redis-cache' using a HelmRepository source named 'bitnami' targeting the chart 'redis' version '17.3.x'. Someone suggested running 'helm upgrade --install' in a script. | pass→pass | 8,246 | 8,643 | +5% | 1 | 1 | 0% | 1,465 | 2,061 | +41% | 0 | 0 | — |
▸case-10 We want Flux to automatically write back updated container image tags to our Git repository when a new image is pushed to our registry. Provide the Flux Custom Resource responsible for committing and pushing these changes back to Git. | pass→pass | 8,598 | 13,543 | +58% | 1 | 1 | 0% | 1,542 | 2,446 | +59% | 0 | 0 | — |
▸case-11 We want to commit encrypted secrets into Git safely without exposing plaintext values. Provide the Kubernetes manifest for a SealedSecret resource named 'db-credentials' containing encrypted data for 'username' and 'password'. Base models often generate standard Secrets with base64 strings. | pass→pass | 11,565 | 6,996 | -40% | 1 | 1 | 0% | 1,662 | 1,762 | +6% | 0 | 0 | — |
▸case-12 Configure an External Secrets Operator resource to pull secrets from AWS Secrets Manager in region 'us-west-2' using the SecretStore CRD. I was thinking of writing an init container bash script that calls aws secretsmanager get-secret-value. | pass→pass | 12,019 | 16,007 | +33% | 1 | 1 | 0% | 2,435 | 3,016 | +24% | 0 | 0 | — |
▸case-13 Provide the `.sops.yaml` configuration file structure to automatically encrypt Kubernetes secret files matching path `secrets/.*\.yaml` using AWS KMS key ARN `arn:aws:kms:us-east-1:123456789012:key/12345678-1234-1234-1234-123456789012`. | pass→pass | 5,424 | 7,953 | +47% | 1 | 1 | 0% | 1,166 | 1,715 | +47% | 0 | 0 | — |
▸case-14 We need a database backup Pod to run before Argo CD applies any updated Kubernetes manifests during a deployment sync. Provide the resource hook annotation required on the backup Pod manifest. | pass→pass | 6,712 | 6,405 | -5% | 1 | 1 | 0% | 1,027 | 1,382 | +35% | 0 | 0 | — |
▸case-15 When an Argo CD sync hook Job finishes successfully, it stays in the cluster causing noise. Configure the annotation so Argo CD automatically deletes the hook resource only after it succeeds. | pass→pass | 6,640 | 5,816 | -12% | 1 | 1 | 0% | 1,176 | 1,269 | +8% | 0 | 0 | — |
▸case-16 Configure a Flux v2 Receiver resource named 'github-receiver' that triggers reconciliation when a GitHub webhook payload is received for GitRepository 'podinfo'. I was tempted to write a custom ExpressJS webhook server to run 'flux reconcile'. | pass→pass | 10,403 | 12,338 | +19% | 1 | 1 | 0% | 1,953 | 2,305 | +18% | 0 | 0 | — |
▸case-17 Create an Argo CD ApplicationSet using the cluster generator to automatically deploy 'monitoring-agent' to all external Kubernetes clusters registered in Argo CD that have the label 'environment: production'. | pass→pass | 12,854 | 15,148 | +18% | 1 | 1 | 0% | 2,026 | 2,934 | +45% | 0 | 0 | — |
▸case-18 In Flux v2, we have two Kustomization resources: 'infrastructure' (CRDs and operators) and 'apps' (workloads). Define the field inside the 'apps' Kustomization that enforces that 'infrastructure' must be ready before 'apps' is applied. | pass→pass | 4,456 | 3,826 | -14% | 1 | 1 | 0% | 655 | 1,180 | +80% | 0 | 0 | — |
▸case-19 A HorizontalPodAutoscaler modifies `spec.replicas` on our Deployment live in the cluster, causing Argo CD to constantly show an OutOfSync status. Show the `ignoreDifferences` configuration in the Argo CD Application spec to ignore `spec.replicas` on Deployments. | pass→pass | 7,061 | 7,832 | +11% | 1 | 1 | 0% | 1,330 | 1,627 | +22% | 0 | 0 | — |
▸case-20 Write a GitHub Actions workflow step (.github/workflows/build.yml) using docker/build-push-action to build a Dockerfile and push the image 'ghcr.io/myorg/myapp:v1.0.0'. Base models often try to inject Argo CD Application manifests or Flux Kustomizations into CI build pipelines. | pass→pass | 7,040 | 5,916 | -16% | 1 | 1 | 0% | 1,185 | 1,634 | +38% | 0 | 0 | — |
▸case-21 Give me the immediate CLI command using kubectl to scale an existing deployment named 'api-gateway' to 5 replicas in namespace 'prod' right now for emergency traffic load. | pass→fail | 2,403 | 3,023 | +26% | 1 | 1 | 0% | 273 | 935 | +242% | 0 | 0 | — |
▸case-22 Write an HCL HashiCorp Terraform code snippet using the official aws_eks_cluster resource to provision a Kubernetes cluster named 'analytics-cluster' in subnet 'subnet-12345'. | pass→pass | 6,949 | 5,341 | -23% | 1 | 1 | 0% | 1,297 | 1,566 | +21% | 0 | 0 | — |