Zero-Config Pipelines with GitLab and Kubernetes on AWS
summary
Explains how to use GitLab AutoDevOps and Convention over Configuration to provide zero‑config CI/CD pipelines by default. Shows how to provision AWS resources and connect Kubernetes with GitLab to run dev, staging and production stacks, and demos an out‑of‑the‑box CI/CD flow using a PHP application.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 2:57GitLab Auto DevOps
- 9:05EKS permissions
- 17:53Production cluster setup
- 25:54Two node groups
- 30:01Kubernetes architecture
- 34:35Helm for Kubernetes
- 41:33GitLab CI/CD
- 50:16GitLab Runner caching
- 59:42Jobs on node groups
- 1:03:14DNS and Ingress
- 1:12:09Project config pipelines
- 1:23:26Pipeline jobs tests
- 1:31:24Summary
related talks
24mReinvent your pipeline with GitLab, Kubernetes, and Amazon EKS
32mEnhance Your Kubernetes CI/CD Pipelines With Open Source
51mGitLab CI/CD Pipelines with Kubernetes
02h 47mPipes on Pipelines
46mFrom Dev to Prod with GitLab CI
55mCI/CD Best Practices with Kubernetes and GitLab
47mGitLab CI and Kubernetes: deploying Applications continuously to Kubernetes
52mFrom 0 to Continuous Deployments with Kubernetes, Helm and GitLab