DevOps & Release Engineering Topics
CI/CD pipeline design, build automation, deployment strategies, release management, artifact repositories, version control integration, and continuous delivery practices. Covers infrastructure automation for delivery workflows, release gates and approvals, multi-service orchestration, rollback strategies, and GitOps approaches. Distinct from Cloud & Infrastructure by focusing specifically on delivery automation and release processes rather than infrastructure platforms.
Automation Scripting for Operations
Writing scripts and tooling to automate operational and delivery tasks: shell and Python scripting, glue automation, toil reduction, and operational efficiency. Covers automating repetitive infrastructure and deployment work and building internal tooling that raises operational leverage. The concern is task-level automation and scripting, distinct from full pipeline or infrastructure-as-code frameworks.
Release Management and Change Control
Planning and governing releases: release cadence and trains, versioning of releases, approval gates, coordinated multi-service releases, and change-management workflows. Covers documenting and controlling changes, adapting release process to delivery needs, and managing the human sign-off around shipping. The concern is the process and governance of releasing, not the deployment mechanics themselves.
Patching and Upgrade Management at Scale
Keeping fleets of systems current: OS and software patching, coordinated fleet updates, version upgrades, and system migrations. Covers planning and rolling out upgrades across many machines, managing change through migrations, and balancing currency against stability. Focuses on maintaining and evolving existing running systems rather than shipping application releases.
Pipeline Security and Compliance
Securing the software delivery pipeline and enforcing compliance within it: supply-chain security, secrets management in CI/CD, security and compliance gates, and automated patch and vulnerability management in the delivery flow. Covers shifting security left into pipelines and preventing insecure or non-compliant changes from shipping. Concerned with securing the delivery path itself, not general application or infrastructure security.
Infrastructure as Code and GitOps
Defining and managing infrastructure and delivery state declaratively: provisioning as code (Terraform, CloudFormation, Pulumi, Ansible, Puppet), configuration management, idempotency, drift detection and remediation, and version control for infrastructure definitions, extended by GitOps where git is the source of truth for deployment and infrastructure state. Covers keeping environments consistent, treating config as a first-class versioned artifact, pull-based deployment and continuous reconciliation toward the committed state (ArgoCD, Flux, and similar controllers), Kubernetes manifest and configuration delivery via git, secrets handling for IaC and GitOps pipelines, policy-as-code guardrails (OPA, Sentinel), Terraform state management and locking, and auditable change through version control: branching strategy, pull request review, commit conventions, and code review policy for infrastructure code. Distinct from the CI/CD pipeline design topic, which owns generic pipeline structure and platform-scale release orchestration (build, test, artifact publishing, runner mechanics) and the architectural choice between push-based CI/CD and pull-based GitOps, even when the payload is infrastructure code. Distinct from the safe deployment and rollback strategies topic, which owns deployment-strategy mechanics: canary and blue-green traffic shifting, automated rollback triggered by metrics or SLOs, feature-flag progressive delivery, Kubernetes rollout mechanics (maxSurge, maxUnavailable, health-check gating), and database or schema migration safety as it gates a release, even when the delivery mechanism is GitOps. Distinct from the automation and scripting topic, which owns operational-scripting disciplines (retry and backoff logic, CLI tool design, generic file, checksum, or diff utilities) when the task is not specifically about declarative infrastructure or configuration state. This topic keeps the GitOps reconciliation loop itself, drift detection and remediation, and IaC state and module lifecycle management regardless of which adjacent discipline a question also touches.