Dominio
DevOps & CI/CD
Perfil de habilidad
Git as source of truth, pull-based deployment, declarative configuration, drift detection, reconciliation loop
Roles
4
donde aparece esta habilidad
Niveles
5
ruta de crecimiento estructurada
Requisitos obligatorios
16
los otros 4 opcionales
DevOps & CI/CD
GitOps
17/3/2026
Selecciona tu nivel actual y compara las expectativas.
La tabla muestra cómo crece la profundidad desde Junior hasta Principal.
| Rol | Obligatorio | Descripción |
|---|---|---|
| DevOps Engineer | Obligatorio | Understands GitOps concept: Git as single source of truth for infrastructure and deployment, pull-based deployment model. Knows basic tools: ArgoCD, Flux. Understands the difference from push-based CI/CD (Jenkins, GitLab CI). |
| Infrastructure Engineer | Obligatorio | Understands GitOps for infrastructure: knows how Terraform/Pulumi state is managed through Git, understands declarative infrastructure management. Can commit infrastructure changes to Git and observe automatic application. |
| Platform Engineer | Obligatorio | Understands GitOps as a platform pattern: knows how the platform can provide GitOps-as-a-service for development teams. Can work with ArgoCD/Flux at the Application resource creation level. |
| Site Reliability Engineer (SRE) | Obligatorio | Understands GitOps from SRE perspective: knows how declarative deployments through Git ensure reproducibility and audit trail. Understands how GitOps helps in incident response (quick rollback through git revert). |
| Rol | Obligatorio | Descripción |
|---|---|---|
| DevOps Engineer | Obligatorio | Implements GitOps workflow: configures ArgoCD/Flux for automatic synchronization of Kubernetes manifests from Git, organizes Git repository structure (app-of-apps, monorepo vs multi-repo), manages secrets through Sealed Secrets or External Secrets Operator. |
| Infrastructure Engineer | Obligatorio | Implements GitOps for infrastructure: configures Atlantis/Spacelift for automated Terraform apply from PRs, organizes Terraform modules in Git with versioning, manages infrastructure secrets through Vault integration. Ensures plan review workflow before apply. |
| Platform Engineer | Obligatorio | Builds GitOps platform: configures ArgoCD in multi-tenant mode with per-team RBAC, creates ApplicationSets for automated onboarding, implements template repositories for standardized deployment configs. Configures notification system for sync failures. |
| Site Reliability Engineer (SRE) | Obligatorio | Applies GitOps for SRE tasks: configures monitoring and alerting through GitOps (Prometheus rules as code), manages SLO definitions in Git, implements emergency procedures through Git-based runbooks. Ensures observability for GitOps sync status. |
| Rol | Obligatorio | Descripción |
|---|---|---|
| DevOps Engineer | Obligatorio | Designs GitOps architecture: defines multi-environment promotion strategy (dev → staging → prod through Git), configures progressive delivery (canary/blue-green) through Argo Rollouts, implements drift detection and auto-remediation. Designs RBAC for GitOps with team-scoped access. |
| Infrastructure Engineer | Obligatorio | Designs infrastructure GitOps: configures Crossplane for Kubernetes-native infrastructure management, implements drift detection and reconciliation for infrastructure state. Designs multi-account/multi-region infrastructure through GitOps with proper state management. |
| Platform Engineer | Obligatorio | Designs enterprise GitOps platform: implements multi-cluster management through ArgoCD, configures hub-spoke topology for fleet management, designs self-service developer portal for GitOps. Integrates GitOps with platform toolchain: secrets, networking, policies. |
| Site Reliability Engineer (SRE) | Obligatorio | Designs GitOps for reliability: configures progressive delivery with SLO-based analysis gates (canary + SLI check → promote/rollback), implements automated rollback on SLO violation. Designs GitOps disaster recovery: rapid cluster state restoration from Git. |
| Rol | Obligatorio | Descripción |
|---|---|---|
| DevOps Engineer | Obligatorio | Standardizes GitOps for the organization: defines repository strategy and branching model for GitOps repos, creates templates for standardized deployments, implements GitOps compliance (audit trail, change approval). Trains teams on GitOps practices. |
| Infrastructure Engineer | Obligatorio | Standardizes infrastructure-as-code through GitOps: defines repository structure and module strategy, creates infrastructure scaffolding tools, implements policy compliance in infrastructure PR review. Designs infrastructure change management process. |
| Platform Engineer | Obligatorio | Standardizes GitOps at platform level: defines platform team's GitOps workflow for infrastructure changes, creates golden path templates, designs policy-as-code enforcement via OPA/Kyverno integrated into GitOps. Ensures platform self-healing through GitOps reconciliation. |
| Site Reliability Engineer (SRE) | Obligatorio | Defines GitOps strategy for SRE: standardizes deployment safety through GitOps gates (SLO check, chaos test, security scan), designs change management through Git. Creates GitOps runbook automation for common incident response actions. |
| Rol | Obligatorio | Descripción |
|---|---|---|
| DevOps Engineer | Shapes enterprise GitOps strategy: designs multi-cluster GitOps with ArgoCD for fleet management, defines governance for GitOps across organizational boundaries. Influences industry practices through GitOps maturity model and best practices. | |
| Infrastructure Engineer | Shapes enterprise infrastructure GitOps: designs unified infrastructure management through Git for multi-cloud, defines governance for infrastructure changes. Influences infrastructure-as-code ecosystem development: Crossplane, Terraform, Pulumi integration with GitOps. | |
| Platform Engineer | Shapes enterprise platform strategy through GitOps: designs platform-of-platforms architecture with GitOps at core, defines standards for cross-team infrastructure management. Influences GitOps ecosystem: contributions to ArgoCD, Flux, Crossplane for platform engineering use cases. | |
| Site Reliability Engineer (SRE) | Shapes enterprise deployment safety through GitOps: designs organization-wide change management policy through GitOps, defines compliance requirements for regulated industries. Influences GitOps for SRE development: progressive delivery, SLO-driven deployment, automated remediation. |