Webinar: Kubernetes and Networks: Why is This So Dang Hard?

Sdílet
Vložit
  • čas přidán 9. 09. 2020
  • Tim Hockin presents a webinar where he looks at different models for integrating Kubernetes into your network in both single-cluster and multi-cluster environments. He looks at IPs, gateway configurations, and how to navigate security boundaries, describing pros and cons of each solution, so that developers can make the best choice for their particular environment.
    Presenter:
    Tim Hockin, Principal Software Engineer @Google
  • Věda a technologie

Komentáře • 9

  • @jjarechiga
    @jjarechiga Před 3 lety +2

    Great talk!
    The audio quality degrades after the 35 minute mark in the Q&A then it gets good again.

  • @tomknud
    @tomknud Před 10 měsíci

    Neat rundown of the options in Pod Internetworking, thanks.

  • @1018hb
    @1018hb Před 3 lety

    I want to pods running on independent host with static ip and want to communicate with pods running in Kubernetes cluster. Only way to communicate is using static ip. How can I do that? I tried to use weavenet, but it works fine between two independent hosts, I can join multiple hosts to weavenet but how can I make it work with Kubernetes cluster.

  • @alveedev
    @alveedev Před 13 dny

    k8s great

  • @DudeSkinnyTall
    @DudeSkinnyTall Před 3 lety +5

    The audio clips all the time, the talk is great though

  • @francisantony12
    @francisantony12 Před 2 lety +1

    25:40 : I think the VIP is assigned to the node. ( Same NIC with multiple IPs ) If this is true, VIP should not be shown as a box outside the cluster.

    • @es3t
      @es3t Před rokem +1

      Can be if the same IP exists on multiple nodes than literally it's on the nodes NICs a you said but doesn't mean that the VIP is used by all of them. It floats. So in those circumstances floating value of that NIC which is the IP itself can be and should be outside the box because it moves whenever it needs.

  • @pengdu7751
    @pengdu7751 Před 2 lety

    cluster CIDR range doesn't have to be "taken" from the network range right? so Cluster:10.0.0.0/16 has nothing to do with Network:10.0.0.0/8?

    • @es3t
      @es3t Před rokem

      That's just for model