OpenShift for operations

Поділитися
Вставка
  • Опубліковано 25 сер 2024

КОМЕНТАРІ • 9

  • @kidfrom87
    @kidfrom87 7 років тому +1

    This is pure gold. Thank you so much for that.
    After a couple months working with OpenShift on top of OpenStack I gotta say it really is amazing to learn the ins and outs.

  • @pdoshi2
    @pdoshi2 7 років тому

    Very good presentation. Great to understand what is going on under-the-hood.

  • @dewaynebranch776
    @dewaynebranch776 2 роки тому +1

    awesome, any new updates

    • @rvalug
      @rvalug 2 роки тому +1

      I'm actually over at Google Cloud these days. :)

  • @calvinlocklear2166
    @calvinlocklear2166 7 років тому

    Great stuff, Jamie!!!

  • @nafasm
    @nafasm 5 років тому

    Thanks
    Jamie Duncan

  • @chauhanvivek27
    @chauhanvivek27 6 років тому +1

    Hi all
    I have question , I know openshift use the kubernetes to make application up .
    But where docker Comes in picture in openshift.
    Why the docker is still required when we have kubernetes.
    What exactly use of docker in openshift?

    • @juninhoalmaraz
      @juninhoalmaraz 6 років тому +2

      I'm not a specialist, but, as far as I know Kubernetes doesn't work without a container runtime and the most common is Docker. There are another container runtimes such as rkt. More or less Kubernetes is sliced in:
      Kubernetes Infrastructure:
      - OS (CoreOS, RedHat);
      - docker , rkt, etc (runtime engine);
      - etcd (implementation - all data stored in etcd cluster - all the other components are stateless except for etcd)
      - flannel, flee (network)
      - Kubernetes Controller: API server, Scheduler, Replication controller, Kubernetes node (old minion)
      Cheers.
      Jose

    • @simianpiate
      @simianpiate 6 років тому

      José Roberto Almaráz da Cunha Júnior Late response but yes, this is exactly right. The Container Engine, in this instance, is what runs the container on the host. Kubernetes itself is just the orchestrations software that takes care of scheduling and controlling the containers running at the Engine layer.