GitLab CI Pipelines
7 posts in reading order. All series →
Tags, archive, series1 active
Posts 7
-
SonarQube in Kubernetes: deployment and GitLab CI integration
SonarQube HelmRelease with PostgreSQL backend (CloudNativePG), GitLab OAuth, ESO for credentials, sonar-scanner-cli job in GitLab CI, GIT_DEPTH:0 for blame.
-
GitLab Runner in Kubernetes
Helm deployment, Docker-in-Docker with emptyDir for TLS certs, per-job resource limits in runner config, registration token via ESO, S3 cache for fast builds.
-
GitLab CI Docker deploy pipeline: build, push, and rolling update
Full GitLab CI pipeline for containerized apps: Docker build with BuildKit layer caching, push to private registry, kubectl rollout with SHA-pinned image tags, multi-environment promotion, and registry cleanup job.
-
GitLab CI DinD: Docker builds with BuildKit caching
Docker-in-Docker setup with TLS, registry layer caching with mode=max, registry mirror to bypass DockerHub rate limits, multi-arch builds with QEMU, and Trivy scan in the same pipeline.
-
Helm chart testing: lint, unit tests, and ct in CI
helm lint, helm-unittest for template assertions, chart-testing (ct) for changed-chart detection, CI/CD stub values files, and what to actually test in your Helm charts.
-
Trivy + SonarQube: security scanning in a GitLab CI pipeline
Filesystem and live Kubernetes cluster scans with Trivy. SARIF for the repo scan, JSON-to-external-issues conversion for k8s findings, imported into SonarQube.
-
GitLab CI multi-environment pipeline: workflow rules and deploy gates
workflow.rules to suppress duplicate pipelines, stages for dev/test/demo/preprod/prod, per-environment deploy jobs extending a shared .deploy anchor, manual prod gate with user restrictions, Grafana deploy annotations.
No posts match the selected filters.