How to setup Autoscaling on Kubernetes / Amazon EKS: Cluster Autoscaler & Horizontal Pod Autoscaler

แชร์
ฝัง
  • เผยแพร่เมื่อ 14 ต.ค. 2024

ความคิดเห็น • 14

  • @samahome
    @samahome ปีที่แล้ว

    Wonderful workshop(s) & excellent explanations with all your sessions on "all things about containers", specifically with "EKS". Always love the way you conduct these workshops in a "very joyous mood & with illustrations".

  • @SV-tc8cu
    @SV-tc8cu 4 ปีที่แล้ว +3

    unfortunately it is out of sync with the site contnet as service accont has been added. This does however gets mentioned in the video. Anyway, thank you for the fantastice series!

  • @joepinto5066
    @joepinto5066 3 ปีที่แล้ว +3

    perfect, can you please send us a link to get the yaml to autoscalling, please.

  • @OpenEmoto
    @OpenEmoto 3 ปีที่แล้ว +1

    You saved my day!

  • @icurtispe
    @icurtispe 4 ปีที่แล้ว +2

    A good advise would be how to save money, maybe stopping the cluster, since this workshop take some days to complete.

    • @SV-tc8cu
      @SV-tc8cu 4 ปีที่แล้ว

      Look in the clean up section

  • @justinogala1729
    @justinogala1729 ปีที่แล้ว

    Thanks. It's educative.

  • @brandonclodius1210
    @brandonclodius1210 ปีที่แล้ว

    Can someone explain why the hpa command reports values over 100%, I didn't quite understand that.

  • @giovannygalindo4726
    @giovannygalindo4726 ปีที่แล้ว

    I accidentally close my TERMINAL where the LOOP was working and is still going on, what can I do????? how can I recover that terminal and how to stop it???

  • @zongzaili9701
    @zongzaili9701 2 ปีที่แล้ว

    great job

  • @Gandolfof
    @Gandolfof 3 ปีที่แล้ว +3

    Thanks a lot! But it could be even better if you would use declarative yaml files instead of running kubectl commands.

  • @madrag
    @madrag 3 ปีที่แล้ว

    Could anyone share how to connect to kube-ops-view with ClusterIP and kubectl proxy option in Cloud9 ?

    • @brandonclodius1210
      @brandonclodius1210 ปีที่แล้ว

      I ran kubectl proxy and then accessed from the following address.
      localhost:8001/api/v1/namespaces/default/services/kube-ops-view/proxy/#