Kubernetes Sucks for Developers, Right? No. (Ep 21)
We are joined by Ellen Körbes for this episode, where we focus on Kubernetes and its tooling. Ellen has a position at Tilt where she works in developer relations. Before Tilt, she was doing closely related kinds of work at Garden, a similar company! Both companies are directly related to working with Kubernetes and Ellen is here to talk to us about why Kubernetes does not have to be the difficult thing that it is made out to be. According to her, this mostly comes down to tooling. Ellen believes that with the right set of tools at your disposal it is not actually necessary to completely understand all of Kubernetes or even be familiar with a lot of its functions. You do not have to start from the bottom every time you start a new project and developers who are new to Kubernetes need not becomes experts in it in order to take advantage of its benefits.
The major goal for Ellen and Tilt is to get developers code up, running and live in as quick a time as possible. When the system is standing in the way this process can take much longer, whereas, with Tilt, Ellen believes the process should be around two seconds! Ellen comments on who should be using Kubernetes and who it would most benefit. We also discuss where Kubernetes should be run, either locally or externally, for best results and Tilt's part in the process of unit testing and feedback. We finish off peering into the future of Kubernetes, so make sure to join us for this highly informative and empowering chat!
Follow us: https://twitter.com/thepodlets
Ellen Körbes https://twitter.com/ellenkorbes
Key Points From This Episode:
Ellen's work at Tilt and the jumping-off point for today's discussion.
The projects and companies that Ellen and Tilt work with, that she is allowed to mention!
Who Ellen is referring to when she says 'developers' in this context.
Tilt's goal of getting all developers' code up and running in the two seconds range.
Who should be using Kubernetes? Is it necessary in development if it is used in production?
Operating and deploying Kubernetes — who is it that does this?
Where developers seem to be running Kubernetes; considerations around space and speed.
Possible security concerns using Tilt; avoiding damage through Kubernetes options.
Allowing greater possibilities for developers through useful shortcuts.
VS Code extensions and IDE integrations that are possible with Kubernetes at present.
Where to start with Kubernetes and getting a handle on the tooling like Tilt.
Using unit testing for feedback and Tilt's part in this process.
The future of Kubernetes tooling and looking across possible developments in the space.
“You're not meant to edit Kubernetes YAML by hand.” — @ellenkorbes [0:07:43]
“I think from the point of view of a developer, you should try and stay away from Kubernetes for as long as you can.” — @ellenkorbes [0:11:50]
“I've heard from many companies that the main reason they decided to use Kubernetes in development is that they wanted to mimic production as closely as possible.” — @ellenkorbes [0:13:21]
Links Mentioned in Today’s Episode:
Ellen Körbes — http://ellenkorbes.com/
Ellen Körbes on Twitter — https://twitter.com/ellenkorbes?lang=en
Tilt — https://tilt.dev/
Garden — https://garden.io/
Cluster API — https://cluster-api.sigs.k8s.io/
Lyft — https://www.lyft.com/
KubeCon — https://events19.linuxfoundation.org/events/kubecon-cloudnativecon-europe-2019/
Unu Motors — https://unumotors.com/en
Mindspace — https://www.mindspace.me/
Docker — https://www.docker.com/
Netflix — https://www.netflix.com/
GCP — https://cloud.google.com/
Azure — https://azure.mi
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...
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.