Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Kubernetes in the 2nd Decade

Tim Hockin
November 09, 2023

Kubernetes in the 2nd Decade

Tim Hockin

November 09, 2023
Tweet

More Decks by Tim Hockin

Other Decks in Technology

Transcript

  1. Kubernetes in the Second Decade
    KubeCon, Chicago
    November, 2023
    Tim Hockin, Google
    @thockin
    (with help from many people!)

    View full-size slide

  2. “...the next
    trillion core
    hours...”
    Jago Macleod
    @jagosan

    View full-size slide

  3. “AI/ML will increase
    compute resource usage
    and the requirement to
    manage those
    workloads effectively
    and efficiently.”
    Janet Kuo
    @janetkuo

    View full-size slide

  4. “Inference is the new
    web app.”
    Clayton Coleman
    @smarterclayton

    View full-size slide

  5. “The impact of AI/ML
    will be on the same
    scale as the impact of
    the internet itself.”
    Tim Hockin
    @thockin

    View full-size slide

  6. “I hope AI / ML can help
    us to optimize the
    testing, debugging, and
    supportability [of
    Kubernetes].”
    Dawn Chen
    @dchen1107

    View full-size slide

  7. “Multi-cluster is
    unavoidable, and for
    many, it's already the
    reality.”
    Jeremy
    Olmsted-Thompson
    @JeremyOT

    View full-size slide

  8. “Clusters are limiting,
    users need to work at a
    higher level.”
    Jeremy
    Olmsted-Thompson
    @JeremyOT

    View full-size slide

  9. “...maybe not
    clusterless, but less
    cluster.”
    Tim Hockin
    @thockin

    View full-size slide

  10. “We're over-indexing
    [on multi-cluster],
    instead of making
    individual clusters
    reliably run all kinds of
    workloads at once.”
    Wojciech Tyczynski
    @wojtek-t

    View full-size slide

  11. Complexity &
    Reliability

    View full-size slide

  12. “...trying to do
    everything...”
    Antonio Ojea
    @aojea

    View full-size slide

  13. “...trying to solve all
    issues for everyone...”
    Dawn Chen
    @dchen1107

    View full-size slide

  14. “All of us [maintainers]
    underestimate the cost
    [of complexity] for
    users, and I perceive it
    as the biggest existential
    threat.”
    Wojciech Tyczynski
    @wojtek-t

    View full-size slide

  15. “I don't think the Rails
    equivalent for K8s has
    emerged yet ... to solve
    this complexity by
    removing unnecessary
    choices.”
    Michael Taufen
    @mtaufen

    View full-size slide

  16. “The big risk is its
    current complexity.”
    Tim Bannister
    @sftim

    View full-size slide

  17. “We should focus on
    keeping the core small
    and stable.”
    Maciej Szulik
    @soltysh

    View full-size slide

  18. “Avoid gridlock or
    calcification.”
    Jordan Liggitt
    @liggitt

    View full-size slide

  19. “Kubernetes won not
    because it’s the best at
    any specific workload,
    but because it can run
    almost everything
    reasonably well.”
    Clayton Coleman
    @smarterclayton

    View full-size slide

  20. “Kubernetes won not
    because it’s the best at
    any specific workload,
    but because it can run
    almost everything
    reasonably well.”
    Clayton Coleman
    @smarterclayton

    View full-size slide

  21. “We’ve got to say no to
    things today, so we can
    afford to do interesting
    things tomorrow.”
    Tim Hockin
    @thockin

    View full-size slide

  22. “Next generation
    operators are less likely
    to be experts in
    Kubernetes ... reliability
    and security are more
    important than new
    features.”
    Jago Macleod
    @jagosan

    View full-size slide

  23. “Workloads on
    Kubernetes have
    evolved from casual to
    critical, including life
    safety, healthcare, telco,
    and public sector.”
    Jago Macleod
    @jagosan

    View full-size slide

  24. “Keeping (or increasing)
    the [quality] bar in core
    is more important than
    any other feature that
    we may add.”
    Wojciech Tyczynski
    @wojtek-t

    View full-size slide

  25. “Paradox of Choice - too
    many choices actually
    limits our freedom, [we
    need to] help users
    choose or avoid the
    need to choose.”
    Janet Kuo
    @janetkuo

    View full-size slide

  26. “We probably gotta
    shrink the landscape to
    stay sustainable.”
    Davanum Srinivas
    @dims

    View full-size slide

  27. “It's hard to find what to
    plug in to Kubernetes
    and the problem gets
    worse the bigger the
    ecosystem grows.”
    Tim Bannister
    @sftim

    View full-size slide

  28. “The growing CNCF
    landscape indicates a
    lack of standards. This
    creates compatibility
    and operational
    complexities.”
    Dawn Chen
    @dchen1107

    View full-size slide

  29. “The ecosystem has
    flourished, but I see
    fewer learnings and
    patterns being brought
    back to Kubernetes.”
    Michelle Au
    @msau42

    View full-size slide

  30. “...the big tent of
    openstack is a good
    example of how this can
    go wrong.”
    Antonio Ojea
    @aojea

    View full-size slide

  31. “Kubernetes should stay
    unfinished.”
    Tim Bannister
    @sftim

    View full-size slide

  32. “Come to the booth and
    tell me why I am
    wrong!”

    View full-size slide