We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Our road to a k8s/GKE based Closed Build Environment

5
 Cite
 Share
 Download
 Purchase
Logo of FOSDEM VZWFOSDEM VZW
 Kiermayer, Siegfried

Formal Metadata

Title
Our road to a k8s/GKE based Closed Build Environment
Subtitle
A small journey to an autoscaling build env based on Jenkins.
Title of Series
Number of Parts
490
Author
License
CC Attribution 2.0 Belgium:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
My team build a new Closed Build Environment for building Release Packages on Google Cloud Platform(gcp) with Google Kubernetes Engine (GKE). I like to take you on a small journey through a variety of topics we came across (open for change): How we bootstrap and how we use ArgoCD Autoscaling to 100 Build nodes for building Why we are using Prometheus-Operator SRE or how we maintain our stack Product aspect Base Image building & scanning Network setup with Shared VPC Google Cloud Platform IAM Permissions vs. RBAC Specific GKE Features like Workload Identity And others Simple real live example how my team is doing it. Looking forward to inspire and to get feedback from others!