Concepts in CI/CD & Automation, page 8
Argo AnalysisTemplates: Reusable Health Checks for Deployments
An AnalysisTemplate is a reusable recipe for judging a deployment's health. During a canary rollout, Argo uses it to query metrics like error rates to decide whether to promote or roll back the new version.
Platform Engineering: Paving the Road for Developers
Platform engineering builds a paved road for developers, offering a standardized, self-service path to ship code. It's used to reduce developer cognitive load and enforce standards. The footgun is building a platform so rigid that nobody wants to use it.
Internal Developer Platform: Your Org's 'Easy Button'
An Internal Developer Platform (IDP) is your company's internal 'PaaS,' offering a self-service 'easy button' for common developer tasks. It lets teams ship faster by abstracting away infrastructure complexity.
Golden Paths: The Paved Road for Developers
A golden path is the company-supported 'paved road' for building and shipping software, offering pre-configured tools. It reduces developer cognitive load and enforces standards for CI/CD and security.
Software Catalog: Your Org's Engineering Map
A software catalog is a searchable map of your software ecosystem, tracking ownership and metadata for every service, library, and pipeline. It helps growing orgs discover services and find owners.
Team Topologies: Organizing for a Fast Flow of Value
Team Topologies is an organizational design framework for accelerating value. As teams scale or adopt new tech, complexity often slows them down. This model structures teams to maintain a fast flow of delivery and innovation.
Platform API: The Contract for Your Developer Platform
The Platform API is the central contract for your internal developer platform, abstracting complex tooling into simple, self-service actions. It's what a developer portal or CLI calls to provision a database or scaffold a new service without knowing the…
Crossplane: The Kubernetes Control Plane for Infrastructure
Crossplane turns your Kubernetes cluster into a universal control plane for all your cloud infrastructure, not just containers. Use it to let developers provision cloud resources like databases using familiar kubectl commands.
Score: Define Your Workload Once, Run Anywhere
Score is a universal remote for your workload configs, letting you define what your app needs once in a score.yaml file. It translates this spec into files for Docker Compose or Kubernetes, preventing config drift.
Visual Regression Testing: Catching Unintended UI Changes
Visual regression testing is a 'spot the difference' game for your UI, comparing screenshots to a baseline to catch visual bugs. It's used in CI/CD to prevent CSS regressions and layout breaks that unit tests miss.
Docker Image Tagging: A Strategy for Reliable Deployments
Think of Docker tags as pointers, not permanent labels. Multiple tags like v1.2.3 and production can point to the same image SHA, enabling reliable CI/CD and rollbacks. The footgun is relying on mutable tags like latest in production.
Hotfix Deployment: Emergency Production Patches
A hotfix is a surgical strike on a production bug, using a dedicated branch to isolate the emergency fix. It's used for critical security flaws or severe defects that can't wait. The footgun: forgetting to merge the fix back into main, causing the bug to.
Configuration Hydration: From Template to Manifest
Configuration hydration turns templates like Helm charts into final Kubernetes manifests. This lets you see the exact YAML diff in a PR, not just a variable change. The footgun is that this adds a build step which, if broken, blocks all deployments.
Argo CD: Git as the Source of Truth for Kubernetes
Argo CD makes your Git repo the single source of truth for your Kubernetes cluster's state. It constantly monitors your cluster and compares it to your desired state in Git, flagging any differences.
Developer Portals: A Self-Service Hub for APIs
A developer portal is a self-service hub for APIs, bundling docs and access controls so developers can discover and use APIs without platform team help. They're used externally for third-party developers or internally for infrastructure automation.
Software Scaffolding: Building Projects from Templates
Scaffolding is like a prefabricated house foundation; it automates creating a standardized project structure from a template. Use it to bootstrap new services with consistent CI/CD, security, and observability from day one.
Linting: Your Automated Code Style Guide
A linter is an automated style guide for your code, catching stylistic errors like inconsistent indentation or naming. It runs in your editor or CI pipeline to enforce team conventions, keeping style debates out of code reviews.
Artifact Signing: Proving Your Code is Your Code
Artifact signing is a notary's seal for software, proving who built it and that it hasn't been tampered with. It's used in CI/CD to sign container images and binaries before publishing.
Secret Sprawl: When Credentials Multiply Unchecked
Secret sprawl is when credentials like API keys multiply without control, getting lost in code, config files, and CI/CD pipelines. It's common in automated cloud systems where non-human identities proliferate.
.jpeg&w=1600&q=75)
Compliance as Code: Automate Your Audits
Compliance as Code prevents last-minute audit scrambles by treating security rules as software. It automates checks in your CI/CD pipeline, turning manual spreadsheet work into a continuous, code-driven process.
We are hiring for this. Every open role lists the topics its interview covers, so you can prepare for the real thing rather than guessing.
See open roles