Cluster API and GitOps: the key to Kubernetes lifecycle management

Поделиться
HTML-код
  • Опубликовано: 6 окт 2024

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

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

    Thank you!! Was very helpful to understand CAPI

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

    Awesome overview, great job!

  • @SaadMalik
    @SaadMalik Год назад +4

    Really well done. Thank you!

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

    good job mate

  • @willemm9356
    @willemm9356 Год назад +2

    Why don't you just mount the kubeconfig secret from the management cluster directly into the autoscaler? You just need to run the autoscaler in the same namespace as the cluster objects.
    And you can use a similar way to get the kubeconfig secret into argocd, although it does need a bit of converting so you need a controller to do that. I think there's even a kyverno policy for it.

  • @vitusyu9583
    @vitusyu9583 6 месяцев назад

    Could I know the name of the software you used in your video? The one with the ‘k9s’ logo on the top right corner.

  • @mzs114
    @mzs114 10 месяцев назад

    How does this compare to Gardener?