Due to its vast array of capabilities and applications, it can be challenging to pinpoint the exact essence of what Kubernetes does. Today we are asking questions about orchestration and runtimes and trying to see if we can agree on whether Kubernetes primarily does one or the other, or even something else. Kubernetes may rather be described as a platform for instance! In order to answer these questions, we look at what constitutes an orchestrator, thinking about management, workflow, and security across a network of machines. We also get into the nitty-gritty of runtimes and how Kubernetes can fit into this model too. The short answer to our initial question is that defining a platform, orchestrator or a runtime depends on your perspective and tasks and Kubernetes can fulfill any one of these buckets. We also look at other platforms, either past or present that might be compared to Kubernetes in certain areas and see what this might tell us about the definitions. Ultimately, we come away with the message that the exact way you slice what Kubernetes does, is not all-important. Rigid definitions might not serve us so well and rather our focus should be on an evolving understanding of these terms and the broadening horizon of what Kubernetes can achieve. For a really interesting meditation on how far we can take the Kube, be sure to join us today!

Follow us: https://twitter.com/thepodlets

Website: https://thepodlets.io

Feeback:

info@thepodlets.io

https://www.notion.so/thepodlets/The-Podlets-Guest-Central-9cec18726e924863b559ef278cf695c9

Hosts:

https://twitter.com/mauilion 

https://twitter.com/joshrosso 

https://twitter.com/embano1 

https://twitter.com/opowero

Key Points From This Episode:
What defines an orchestrator? Different kinds of management, workflow, and security.
Considerations in a big company that go into licensing, security and desktop content.
Can we actually call Kubernetes and orchestrator or a runtime?
How managing things at scale increases the need for orchestration.
An argument for Kubernetes being considered an orchestrator and a runtime.
Understanding runtimes as part of the execution environment and not the entire environment.
How platforms, orchestration, and runtimes change positions according to perspective.
Remembering the 'container orchestration wars' between Mezos, Swarm, Nomad, and Kubernetes.
The effect of containerization and faster release cycles on the application of updates.
Instances that Kubernetes might not be used for orchestration currently.
The increasingly lower levels at which you can view orchestration and containers.
The great job that Kubetenes is able to do in the orchestration and automation layer.
How Kubernetes removes the need to reinvent everything over and over again.
Breaking down rigid definitions and allowing some space for movement.

Quotes:

“Obviously, orchestrator is a very big word, it means lots of things but as we’ve already described, it’s hard to fully encapsulate what orchestration means at a lower level.” — @mauilion [0:16:30]

“I wonder if there is any guidance or experiences we have with determining when you might need an orchestrator.” — @joshrosso [0:28:32]

“Sometimes there is an elemental over-automation some people don’t want all of these automation happening in the background.” — @opowero [0:29:19]

Links Mentioned in Today’s Episode:

Apache Airflow — https://airflow.apache.org/

SSCM — https://www.lynda.com/Microsoft-365-tutorials/SSCM-Office-Deployment-Tool/5030992/2805770-4.html

Ansible — https://www.ansible.com/

Docker — https://www.docker.com/

Joe Beda — https://www.vmware.com/latam/company/leadership/joe-beda.html

Jazz Improvisation over Orchestration — https://blog.heptio.com/core-kubernetes-jazz-improv-over-orchestration-a7903ea92ca?gi=5c729e924f6c

containerd — https://containerd.io/

AWS — https://aws.amazon.com/

Fleet — https://coreos.com/fleet/docs/latest/launching-containers-fleet.html

Puppet — https://puppet.com/

HashiCorp Nomad — https://nomadproject.io/

Mesos — http://mesos.apache.org/

Swarm — https://docs.docker.com/get-started/swarm-deploy/

Red Hat — https://www.redhat.com/en

Zalando — https://zalando.com/

Due to its vast array of capabilities and applications, it can be challenging to pinpoint the exact essence of what Kubernetes does. Today we are asking questions about orchestration and runtimes and trying to see if we can agree on whether Kubernetes primarily does one or the other, or even something else. Kubernetes may rather be described as a platform for instance! In order to answer these questions, we look at what constitutes an orchestrator, thinking about management, workflow, and security across a network of machines. We also get into the nitty-gritty of runtimes and how Kubernetes can fit into this model too. The short answer to our initial question is that defining a platform, orchestrator or a runtime depends on your perspective and tasks and Kubernetes can fulfill any one of these buckets. We also look at other platforms, either past or present that might be compared to Kubernetes in certain areas and see what this might tell us about the definitions. Ultimately, we come away with the message that the exact way you slice what Kubernetes does, is not all-important. Rigid definitions might not serve us so well and rather our focus should be on an evolving understanding of these terms and the broadening horizon of what Kubernetes can achieve. For a really interesting meditation on how far we can take the Kube, be sure to join us today!
Follow us: <a href="https://twitter.com/thepodlets">https://twitter.com/thepodlets</a>
Website: <a href="https://thepodlets.io">https://thepodlets.io</a>
Feeback:
<a href="mailto:info@thepodlets.io">info@thepodlets.io</a>
<a href="https://www.notion.so/thepodlets/The-Podlets-Guest-Central-9cec18726e924863b559ef278cf695c9">https://www.notion.so/thepodlets/The-Podlets-Guest-Central-9cec18726e924863b559ef278cf695c9</a>
Hosts:
<a href="https://twitter.com/mauilion">https://twitter.com/mauilion </a>
<a href="https://twitter.com/joshrosso">https://twitter.com/joshrosso </a>
<a href="https://twitter.com/embano1">https://twitter.com/embano1 </a>
<a href="https://twitter.com/opowero">https://twitter.com/opowero</a>
Key Points From This Episode:
<ul>
<li>What defines an orchestrator? Different kinds of management, workflow, and security.</li>
<li>Considerations in a big company that go into licensing, security and desktop content.</li>
<li>Can we actually call Kubernetes and orchestrator or a runtime?</li>
<li>How managing things at scale increases the need for orchestration.</li>
<li>An argument for Kubernetes being considered an orchestrator and a runtime.</li>
<li>Understanding runtimes as part of the execution environment and not the entire environment.</li>
<li>How platforms, orchestration, and runtimes change positions according to perspective.</li>
<li>Remembering the 'container orchestration wars' between Mezos, Swarm, Nomad, and Kubernetes.</li>
<li>The effect of containerization and faster release cycles on the application of updates.</li>
<li>Instances that Kubernetes might not be used for orchestration currently.</li>
<li>The increasingly lower levels at which you can view orchestration and containers.</li>
<li>The great job that Kubetenes is able to do in the orchestration and automation layer.</li>
<li>How Kubernetes removes the need to reinvent everything over and over again.</li>
<li>Breaking down rigid definitions and allowing some space for movement.</li>
</ul>
Quotes:
&ldquo;Obviously, orchestrator is a very big word, it means lots of things but as we&rsquo;ve already described, it&rsquo;s hard to fully encapsulate what orchestration means at a lower level.&rdquo; &mdash; <a href="https://twitter.com/mauilion">@mauilion</a> [0:16:30]
&ldquo;I wonder if there is any guidance or experiences we have with determining when you might need an orchestrator.&rdquo; &mdash; <a href="https://twitter.com/joshrosso">@joshrosso</a> [0:28:32]
&ldquo;Sometimes there is an elemental over-automation some people don&rsquo;t want all of these automation happening in the background.&rdquo; &mdash; <a href="https://twitter.com/opowero">@opowero</a> [0:29:19]
Links Mentioned in Today&rsquo;s Episode:
Apache Airflow &mdash; <a href="https://airflow.apache.org/">https://airflow.apache.org/</a>
SSCM &mdash; <a href="https://www.lynda.com/Microsoft-365-tutorials/SSCM-Office-Deployment-Tool/5030992/2805770-4.html">https://www.lynda.com/Microsoft-365-tutorials/SSCM-Office-Deployment-Tool/5030992/2805770-4.html</a>
Ansible &mdash; <a href="https://www.ansible.com/">https://www.ansible.com/</a>
Docker &mdash; <a href="https://www.docker.com/">https://www.docker.com/</a>
Joe Beda &mdash; <a href="https://www.vmware.com/latam/company/leadership/joe-beda.html">https://www.vmware.com/latam/company/leadership/joe-beda.html</a>
Jazz Improvisation over Orchestration &mdash; <a href="https://blog.heptio.com/core-kubernetes-jazz-improv-over-orchestration-a7903ea92ca?gi=5c729e924f6c">https://blog.heptio.com/core-kubernetes-jazz-improv-over-orchestration-a7903ea92ca?gi=5c729e924f6c</a>
containerd &mdash; <a href="https://containerd.io/">https://containerd.io/</a>
AWS &mdash; <a href="https://aws.amazon.com/">https://aws.amazon.com/</a>
Fleet &mdash; <a href="https://coreos.com/fleet/docs/latest/launching-containers-fleet.html">https://coreos.com/fleet/docs/latest/launching-containers-fleet.html</a>
Puppet &mdash; <a href="https://puppet.com/">https://puppet.com/</a>
HashiCorp Nomad &mdash; <a href="https://nomadproject.io/">https://nomadproject.io/</a>
Mesos &mdash; <a href="http://mesos.apache.org/">http://mesos.apache.org/</a>
Swarm &mdash; <a href="https://docs.docker.com/get-started/swarm-deploy/">https://docs.docker.com/get-started/swarm-deploy/</a>
Red Hat &mdash; <a href="https://www.redhat.com/en">https://www.redhat.com/en</a>
Zalando &mdash; <a href="https://zalando.com/">https://zalando.com/</a>

Orchestrators and Runtimes

Kubernetes Sucks for Developers, Right? No.

Running Kubernetes on conventional operating systems is time-consuming and labor-intensive. Today’s guests Andrew Rynhard and Timothy Gerla have engineered a product that attempts to provide a solution to this problem.

Kubernetes Operating Systems

Our guests help companies to update their systems and move into more up-to-date setups through the Swift methodology and our conversation focusses on this journey from legacy code to a more manageable solution.  We lay the groundwork for the conversation, defining a few of the key terms and concerns that arise for typical clients and then Shaun and Chris share a bit about their approach to moving things forward.

Application Transformation with Chris Umbel and Shaun Anderson

The question of diving into Kubernetes is something that faces us all in different ways. Whether you are already on the platform, are considering transitioning, or are thinking about what is best for your team moving forward, the possibilities and the learning-curve make it a somewhat difficult question to answer. In this episode, we discuss the topic and ultimately believe that an individual is the only one who can answer that question well. That being said, the capabilities of Kubernetes can be quite persuasive and if you are tempted then it is most definitely worth considering very seriously, at least.

Should I Kubernetes?

If you work in Kubernetes, cloud native, or any other fast-moving ecosystem, you might have found that keeping up to date with new developments can be incredibly challenging. We think this as well, and so we decided to make today’s episode a tribute to that challenge, as well as a space for sharing the best resources and practices we can think of to help manage it.

Keeping up with Cloud Native

Do you know what cloud native apps are? Well, we don’t really either, but today we’re on a mission to find out! This episode is an exciting one, where we bring all of our different understandings of what cloud native apps are to the table. The topic is so interesting and diverse and can be interpreted in a myriad of ways.

Cloud Native Apps

Today we try to dig into what the network actually means. We discover, through our discussion that the network is, in fact, a distributed system. This means that each component of the network has a degree of independence and the complexity of them makes it difficult to understand the true state of the network.

The Network

Our topic in today's great episode is how we think jobs in software engineering have changed since the advent of cloud native computing.

Jobs in Cloud Native

Craig has loads of expertise and shareable experience in the cloud native space and we have a fascinating chat with him, asking about his work, Heptio and of course, Kubernetes! Craig shares some insider perspective on the space, the rise of Kubernetes and how the increase in Kubernetes' popularity can be managed.

The Past, Present and Future of Kubernetes with Craig McLuckie

The Podlets is a weekly show that explores cloud native, one buzzword at a time. Each week experts in the field will discuss and contrast distributed systems concepts, practices, trade-offs, and lessons learned to help you on your cloud native journey. This space moves fast, and we shouldn’t reinvent the wheel. If you are an engineer, operator, or technically minded decision maker, this podcast is for you!

Find us at https://thepodlets.io.

The Podlets is a weekly show that explores cloud native, one buzzword at a time. Each week experts in the field will discuss and contrast distributed systems concepts, practices, trade-offs, and lessons learned to help you on your cloud native journey. This space moves fast, and we shouldn&rsquo;t reinvent the wheel. If you are an engineer, operator, or technically minded decision maker, this podcast is for you!
Find us at <a href="https://thepodlets.io">https://thepodlets.io</a>.

Exploring cloud native, one buzzword at a time!

The Podlets - A Cloud Native Podcast

The Podlets is a weekly show that explores cloud native, one buzzword at a time. Each week experts in the field will discuss and contrast distributed systems concepts, practices, trade-offs, and lessons learned to help you on your cloud native journey. This space moves fast, and we shouldn’t reinvent the wheel. If you are an engineer, operator, or technically minded decision maker, this podcast is for you!

The Podlets is a weekly show that explores cloud native, one buzzword at a time. Each week experts in the field will discuss and contrast distributed systems concepts, practices, trade-offs, and lessons learned to help you on your cloud native journey. This space moves fast, and we shouldn&rsquo;t reinvent the wheel. If you are an engineer, operator, or technically minded decision maker, this podcast is for you!

The Podlets

Social links:

Follow the podcast:

23 clip(s)