Это видео недоступно.
Сожалеем об этом.

Single-node Kubernetes Clusters Using K3s with Benefits of GitOps • Lasse Højgaard • GOTO 2021

Поделиться
HTML-код
  • Опубликовано: 31 июл 2024
  • This presentation was recorded at GOTO Copenhagen 2021. #GOTOcon #GOTOcph
    gotocph.com
    Lasse Højgaard - Cloud Architect & Software Pilot at Trifork
    ORIGINAL TALK TITLE
    Lowering the Barriers to Entry for Kubernetes
    ABSTRACT
    The Kubernetes eco-system is quickly becoming the de facto way to run applications. The toolbox is chock-full of tools that can be hard to let go off once you’ve tried them.
    Large-scale Kubernetes deployments in the cloud or on-premises can be a daunting task to set up. Sometimes you can’t justify the cost of a managed Kubernetes cluster because the project is still in its infancy? What if you don’t need a highly-available multi-node cluster? Should you go back to running Docker containers on a simple VM?
    In this talk we will look at how single-node Kubernetes clusters using K3s can be a way to lower the barrier of entry for Kubernetes, while still getting the benefits of GitOps, rolling deployments, and mature monitoring solutions. We’ll also discuss next steps if you outgrow your single-node cluster [...]
    TIMECODES
    00:00 Intro
    02:20 Agenda
    03:01 Act 1: Docker-compose up & echo done
    11:14 Act 2: Trouble in paradise
    14:57 Act 3: Is there something better & can we afford it?
    23:25 Demo
    41:10 Problems to solve
    41:33 Where to go from here?
    42:59 Outro
    Download slides and read the full abstract here:
    gotocph.com/2021/sessions/200...
    RECOMMENDED BOOKS
    Thomas Vitale • Cloud Native Spring in Action • amzn.to/3355Zy0
    Brendan Burns, Joe Beda & Kelsey Hightower • Kubernetes: Up and Running • amzn.to/31OAhB9
    Burns, Villalba, Strebel & Evenson • Kubernetes Best Practices • amzn.to/3gBXRsr
    Sam Newman • Monolith to Microservices • amzn.to/2Nml96E
    Sam Newman • Building Microservices • amzn.to/3dMPbOs
    Ronnie Mitra & Irakli Nadareishvili • Microservices: Up and Running• amzn.to/3c4HmmL
    Mitra, Nadareishvili, McLarty & Amundsen • Microservice Architecture • amzn.to/3fVNAb0
    Chris Richardson • Microservices Patterns • amzn.to/2SOnQ7h
    Adam Bellemare • Building Event-Driven Microservices • amzn.to/3yoa7TZ
    Dave Farley • Continuous Delivery Pipelines • amzn.to/3hjiE51
    / gotocon
    / goto-
    / gotoconferences
    #CloudNative #Cloud #Kubernetes #k8s #k3s #DevOps #ContinuousDelivery #CD #Testing #GitOps #Microservices #APIs #APIGateway #Observability #Testing #Docker #DockerCompose #CNCF #Flux #Helm #Kustomize #curl #SealedSecrets
    Looking for a unique learning experience?
    Attend the next GOTO conference near you! Get your ticket at gotopia.tech
    Sign up for updates and specials at gotopia.tech/newsletter
    SUBSCRIBE TO OUR CHANNEL - new videos posted almost daily.
    ruclips.net/user/GotoConf...

Комментарии • 26

  • @yehudamakarov
    @yehudamakarov Год назад +3

    Great talk. A real engineer here with that brutal problem solving attitude, superb. 😊

  • @JonasKongslund
    @JonasKongslund 2 года назад +5

    Great talk. I want to emphasize that any attempt to introduce a platform comes with an added cost of maintaining that platform. When the platform, and the solutions on top of it, have to be hosted on-premises, it is crucial to keep this cost in mind since a team may not have the luxury of delegating maintenance to someone else.

  • @theritesh973
    @theritesh973 2 года назад +1

    Informative.Thanks for this talk.

  • @dilmurodyangiboev1296
    @dilmurodyangiboev1296 11 месяцев назад +1

    Great insights! Thank you!)

  • @kauffmann101
    @kauffmann101 2 года назад +1

    why not use podman ?

  • @mza9738
    @mza9738 2 года назад +2

    The repo is not public

  • @AndersKeisHansen
    @AndersKeisHansen 2 года назад +3

    Great video, thx :)

  • @undefined_cat
    @undefined_cat Год назад +1

    Why not just use Docker swarm?

  • @anjumwaheed7264
    @anjumwaheed7264 2 года назад +2

    1 all

  • @suikast420
    @suikast420 2 года назад +1

    Great talk. I am thinking about replace Kafka with NATS. Furthermore I see the HUMIO it is a good replacement ( memory consumption and bootup time for example ) for elasticsearch ?

    • @JonasKongslund
      @JonasKongslund 2 года назад +3

      Humio is a great choice for logs. You may also want to take a look at Loki from Grafana Labs.

    • @suikast420
      @suikast420 2 года назад +1

      @@JonasKongslund I have it on my list ;-)

    • @q1joe
      @q1joe 2 года назад

      I wouldn’t consider NATS and Kafka the same, one is MQ and more is event source / write ahead log.

    • @prdoyle
      @prdoyle 2 года назад

      Sorry, what does this have to do with the video?

  • @fringefringe7282
    @fringefringe7282 2 года назад +40

    Sad story about what happened to IT industry. We can't afford anything, we have to do it immediately in 'fire mode', it has to work somehow, go, tik tok, tik tok, why is it taking so long, tik tok... Everything is one giant MVP nowadays. Unfortunately its trendy to solve obvious problems on production, instead of anticipating them. Culture of non-thinking. Culture of empirically head-bumping everything.

  • @MarkRuvald
    @MarkRuvald Год назад +1

    This doesn't really make sense; replace docker compose with Kubernetes - complicating everything. It isn't even highly available!

    • @tehseensajjad1003
      @tehseensajjad1003 Год назад +1

      As he said at the start, HA isnt the target here,
      i would trade docker-compose/swarm with a lightweight kubernetes any day. Just think about configuring all the stuff that base-kubernetes comes with in a docker-compose deployment

  • @AtulVinayakS
    @AtulVinayakS 2 года назад +5

    Single-node and cluster?

    • @ankursharma5043
      @ankursharma5043 2 года назад

      Haha

    • @lhxperimental
      @lhxperimental 2 года назад +2

      A special case of clusters where number of nodes is 1. Still make sense because. It's very easy to scale up by adding nodes when need arises. It not ha while it is single node. That's all

  • @ArielRichtman0
    @ArielRichtman0 2 года назад +2

    Hard pass but thanks

    • @prdoyle
      @prdoyle 2 года назад +3

      Obviously not an appropriate production deployment for most systems, but that's not the interesting part. The interesting part to me is seeing the progress in "scaling down" k8s so it's not this enterprise-only juggernaut anymore. Running k8s in this (obviously not ideal) setup should smooth the transition to a proper scalable, fault-tolerant setup down the road; compared with the more straightforward approach of building automation scripts around his manual steps, which would create more and more team-owned complexity and technical debt, and move their solution AWAY from best practices rather than toward them.

  • @Jahzwolf1955
    @Jahzwolf1955 2 года назад +1

    🤬