Kubernetes as a Platform Framework: Journey from IaC Pipelines to K8s APIs - Christina Andonov, AWS

Поділитися
Вставка
  • Опубліковано 29 кві 2024
  • Don't miss out! Join us at our next Flagship Conference: KubeCon + CloudNativeCon North America in Salt Lake City from November 12 - 15, 2024. Connect with our current graduated, incubating, and sandbox projects as the community gathers to further the education and advancement of cloud native computing. Learn more at kubecon.io
    Kubernetes as a Platform Framework: Journey from IaC Pipelines to K8s APIs - Christina Andonov, AWS
    As organizations scale their cloud adoption, they continue to find bottlenecks in their ability to deploy new workloads due to the shear number of resources centralized teams must manage. Developers at these organizations must traverse through multiple workflows-stitching together outputs from multiple pipelines-to deploy their applications. These delays result in new workloads or features taking up to 6-12 months to launch into production. Attempting to remove the bottleneck of centralized teams and empower developers, technical leadership is driving self-service automation initiatives commonly referred to as platform engineering. This presentation covers why platform engineering is trending, why new tools and methodologies are required, real-world customer use-cases, and how to get started. Additionally we’ll demo how to build a modern platform using OSS CNCF tools like Argo, Crossplane, and Gatekeeper.
  • Наука та технологія

КОМЕНТАРІ • 4

  • @spielfuhrer85
    @spielfuhrer85 Місяць тому +2

    Great presentation!

  • @EmanueleDiSaverio
    @EmanueleDiSaverio Місяць тому +1

    "Developers don't have access to Terraform" says who? Why can't developer use Terraform?

    • @NeoDaPlaya
      @NeoDaPlaya Місяць тому +12

      From my experience (most) developer don’t want access to / use Terraform. Which I fully understand

    • @kaurk2058
      @kaurk2058 Місяць тому +5

      She literally explained in the next sentence that they can and how it often looks like + what @neodaplaya said + ensuring standards / conventions across different developer teams