⎈ Kubecon San Diego Recap, ArgoCD, Autoscaling, CNCF year in recap & + ⎈


⎈ Kubecon San Diego recap, ArgoCD, Autoscaling, CNCF year in recap⎈


We are happy to be back from San Diego and organize the last CNCF event of 2019! Come join us and get news about KubeCon or share your experience if you went. Learn about the latest news in CNCF, Kubernetes 1.16 & 1.17, Istio 1.3 and 1.4, Helm 3. As usual, we are trying to get great speakers from around the world and will be happy to have users speaking at our Meetup too.
If you want to share your story, submit your CFP here: https://www.papercall.io/cncf-waterloo

18:00 - 18:15 Registration
18:15 - 18:45 Kubecon Recap, CNCF, Kubernetes, Helm, Istio year in recap! by CNCF Ambassador
18:45 - 19:30 Designing a complete CI-CD pipeline using Argo Events, Workflow and CD projects by Julian Mazzitelli by CTO BioBox
19:30 - 20.15 Autoscaling in reality: Lessons learned from adaptively scaling Kubernetes, by Andy Kwiatkowski @Shopify

🙏 Big thanks to Shopify for hosting us.

Designing a complete CI-CD pipeline using Argo Events, Workflow and CD projects
CTO BioBox - “bioinformatics as a service” on cloud-native technologies
Twitter: @thejmazz

Are you looking to get more flexibility out of your CICD platform? Interested how GitOps fits into the mix? Learn how Argo CD, Workflows, and Events can be combined to craft custom CICD flows. All while staying Kubernetes native, enabling you to leverage existing observability tooling.

Autoscaling in reality: Lessons learned from adaptively scaling Kubernetes
Andy Kwiatkowski Senior Production Engineer, Shopify

Cloud providers often come with a checkbox to enable a simple CPU-based autoscaler. However, if your application runs complex deployments on thousands of servers across multiple regions and has to wrestle the occasional celebrity flash sale, you might need to go further to react quicker, allow for more complex scaling rules, and create extra fail-safes to prevent capacity shortages.

Andy Kwiatkowski dives into what it took for Shopify to create its own autoscaler, from writing traffic-smoothing algorithms to dealing with regional evacuations and to handling noise from a system continuously deployed 50 times a day. He details creating a more useful utilization signal and share battle-tested ideas for creating a highly fault-tolerant tool you can trust to scale your entire infrastructure.