Sign in Subscribe
8 min read gitlab-ci-cd

Gitlab CI/CD - Architecture

GitLab CI/CD relies on a Coordinator-Runner model. The GitLab server manages the pipeline state, while isolated Runners pick up jobs and execute the heavy lifting. We’ll map out how these components communicate securely to execute your code.
Gitlab CI/CD - Architecture
Reader: GitLab Architecture

Reader Mode

-- / --

Introduction

Published by:

WassupAI

You might also like...

21
Dec
Gitlab CI/CD - Kubernetes Integration

Gitlab CI/CD - Kubernetes Integration

Embrace GitOps. Connect your cluster via the GitLab Agent to manage deployments securely. Synchronize your manifest files directly with the cluster state for seamless, pull-based updates.
7 min read
21
Dec
Gitlab CI/CD - Terraform / OpenTofu Integration

Gitlab CI/CD - Terraform / OpenTofu Integration

Infrastructure as Code meets CI/CD. Manage your Terraform state within GitLab. We’ll generate plans in Merge Requests and apply infrastructure updates automatically when code is merged.
7 min read
21
Dec
Gitlab CI/CD - Compliance Pipelines

Gitlab CI/CD - Compliance Pipelines

Enforce governance. Define mandatory scans or steps that run in every project's pipeline regardless of developer configuration. Ensure regulatory requirements are met without relying on individual teams.
7 min read
21
Dec
Gitlab CI/CD - Secure Authentication (OIDC)

Gitlab CI/CD - Secure Authentication (OIDC)

Stop managing long-lived keys. Use OpenID Connect (OIDC) to authenticate securely with cloud providers like AWS and GCP. Exchange temporary ID tokens for access, eliminating the risk of static credential leaks.
8 min read
21
Dec
Gitlab CI/CD - Gitlab Secure Features

Gitlab CI/CD - Gitlab Secure Features

Shift security left. Integrate SAST, DAST, and Dependency Scanning directly into your pipeline. Automatically detect code vulnerabilities and leaked secrets before your changes ever hit production.
7 min read

Member discussion