What is the context in DevOps?

In the DevOps context, it can mean several things, but mainly:

1. Organizational context: culture, processes, team structure, and business goals that influence the adoption of DevOps practices.
2. Technical context: infrastructure, technology stack, application architecture, and existing tools used in the workflow.
3. Task or activity context: specific requirements, constraints, and dependencies related to a particular task (e.g., deploying a new service, configuring a CI/CD pipeline).

Example of using context in a CI/CD pipeline:

# .gitlab-ci.yml
stages:
  - build
  - test
  - deploy_staging
  - deploy_production

variables:
  # Organizational context: project name, application version
  PROJECT_NAME: "my-web-app"
  APP_VERSION: "1.0.${CI_PIPELINE_IID}" # CI_PIPELINE_IID from the technical context of GitLab CI

build:
  stage: build
  script:
    # Technical context: using Docker to build the image
    - docker build -t $PROJECT_NAME:$APP_VERSION .
  tags:
    - docker_builder # Task context: build requires a specific environment

test:
  stage: test
  script:
    # Task context: running unit tests
    - docker run $PROJECT_NAME:$APP_VERSION npm test

deploy_staging:
  stage: deploy_staging
  script:
    # Task context: deploying to a staging environment
    - kubectl apply -f kubernetes/staging.yaml # Technical context: using Kubernetes
  variables:
    # Organizational context: variables for accessing staging
    KUBECONFIG: /path/to/staging/kubeconfig

deploy_production:
  stage: deploy_production
  script:
    # Task context: deploying to production environment
    - kubectl apply -f kubernetes/production.yaml
  when: manual # Organizational context: manual approval for production
  only:
    - main # Organizational context: deploy only from the main branch

Understanding the context is critically important for making the right decisions when choosing tools, processes, and strategies in DevOps, as well as for effective collaboration between teams.