We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
Our road to a k8s/GKE based Closed Build Environment A small journey to an autoscaling build env ba…
Join this talk as we explore our journey to a scalable, secure, and maintainable Closed Build Environment using Kubernetes, GKE, and ArgoCD.
- Kubernetes allows for scalability and flexibility in their infrastructure.
- Jenkins is a super powerful tool, but it has security concerns.
- ArgoCD is a great open source tool for defining and applying infrastructure as code.
- Using Helm charts allows for version control and updates.
- Kubernetes allows for networking, as well as other services such as LoadBalancer and Ingress.
- Jenkins masters can be autoscaled, which makes it more cost-effective.
- There is a manual versioning system in use.
- Monitoring is an essential part of maintaining the system, with tools such as Prometheus and Grafana.
- A seed shop or monstrous \$2000 dedicated to architecture hardware was not enough for demand.
- Jenkins plugins pave the way for automation, emphasize the use of OpenID Provider.
- Kubernetes uses TCS tool for persistent storage and SAE for scaling.
- The need for less curation leads to the automation.