logo
Dates

Author


Conferences

Tags

Sort by:  

Authors: Michael McCune, Bridget Kromhout
2022-10-27

tldr - powered by Generative AI

Update on cloud provider migration and graduation to GA
  • AWS and GCP have tested cloud native migration
  • Azure still needs to be tested
  • V1 API update and graduation coming up
  • No blockers identified
  • Beta testing can begin with at least two implementations
  • Circular dependency issue needs to be fixed for GA
Authors: Niko Smeds
2022-05-20

tldr - powered by Generative AI

Lessons learned from deploying workloads on a new cloud provider
  • Use infrastructure as code and version control from early on in the project
  • Expect to iterate and plan around limitations
  • Don't blindly copy solutions from previous providers, look for possible improvements
  • Load test applications to discover issues before customers do
  • Be aware of quotas when scaling up nodes
Authors: Steve Wong, Nicholas Turner
2022-05-19

tldr - powered by Generative AI

Updates on cloud provider implementations for Kubernetes
  • Kubernetes runs on multiple clouds
  • Cloud provider implementations give community updates
  • Updates on recent releases and support for dual stack
  • AWS load balancer controller recommended over built-in service controller
  • CSI migration offered as add-ons in EKS and COPs
  • Testing and migration plans for cloud provider features
Authors: Jeremy Olmsted-Thompson, Laura Lorenz, Paul Morie
2022-05-19

tldr - powered by Generative AI

The presentation is about showcasing the AWS cloud map MCS controller for Kubernetes and its interaction with the about API and MCS API.
  • The AWS cloud map MCS controller for Kubernetes is showcased in the presentation.
  • The controller is built on top of AWS cloud map and interacts with the about API and MCS API.
  • The presentation demonstrates the creation of service exports and imports between two EKS clusters.
  • The AWS cloud map services created for the namespace are also shown.
  • The audience is encouraged to join the bi-weekly meetings of the Sig multi-cluster to provide input and bring up new ideas.
Authors: Mauricio Salatino
2021-10-15

tldr - powered by Generative AI

The presentation discusses the importance of cloud strategy and multi-cloud approach in building a self-service conference platform. It also highlights the use of Tekton and Helm for automating the creation and packaging of artifacts, and KNative for making developers' lives easier.
  • Industries that are heavily regulated require running cloud providers that comply with regulations and allowing customers to run the platform in their on-prem cloud services
  • Clear definitions and a multi-cloud strategy are important in building platforms
  • Tekton and Helm can automate the creation and packaging of artifacts
  • KNative can make developers' lives easier by providing advanced traffic management and eventing capabilities
  • KNative Serving allows for easy creation of Canadian services and header-based routing
  • KNative Eventing provides producers and consumers of events to Kubernetes
Authors: Anusha Iyer, Alex Meijer
2021-10-13

tldr - powered by Generative AI

Tips and tricks for cloud agnostic paradigm using Terraform and Kubernetes
  • Utilizing Terraform in a cloud agnostic paradigm by building modules for each cloud provider
  • Gluing together modules with a common module that has essential code
  • Understanding the importance of resources and limits for the scheduler
  • Being cautious when pulling in elements from the rich world of free source software and understanding the configuration and dials
  • Sharing an anecdote about the importance of watching the dials when introducing a modsec waff into the ingress controllers
Authors: Steve Wong, Nicholas Turner, Walter Fender
2021-10-13

Cloud Provider code allows Kubernetes to run on top of different platforms. Originally, support for all variations was built directly into a K8s release. This brought bloat - a running cluster used only a subset of the code within the release. Also, any cloud specific bug fix or enhancement demanded a new full K8s release as a carrier. This will be a status report on removing the cloud provider code from the main Kubernetes repository. Significant early milestones were recently achieved: the API Server no longer needs the cloud provider library; SSHTunnels have been deleted. For each in-tree cloud provider, we will report on efforts, accomplishments, and roadmap for getting "out-of-tree". We’ll also discuss the plans to handle the speed bumps that are left - including interesting topics like multi-repo e2e testing and removing the cluster directory.