PodCTL - Enterprise Kubernetes

SEASON 2 - EPISODE 4

ABOUT THE SHOW:
In this show, we discuss the frequency of Kubernetes releases, as well as the differences between upstream project releases and vendor-created distributions (or cloud services). We also discuss why all variations of Kubernetes are not running the same version, and why this might create challenges for companies using Kubernetes.
SHOW LINKS:

• Kubernetes Homepage
• CNCF Homepage
• Business stories of companies using Kubernetes

FEEDBACK?
Email: PodCTL at gmail dot com
Twitter: @PodCTL
Web: http://podctl.com

SEASON 2 - EPISODE 2

ABOUT THE SHOW:
In this show, we look at the why technologists and business leaders are choosing to use Kubernetes to help solve new business challenges. We highlight the various types of use-cases that can be enabled by the core technologies within Kubernetes.
SHOW LINKS:

• Kubernetes Homepage
• CNCF Homepage
• Business stories of companies using Kubernetes

FEEDBACK?
Email: PodCTL at gmail dot com
Twitter: @PodCTL
Web: http://podctl.com

Show: 23
Show Overview: Brian and Tyler talk with Christian Posta (@christianposta, Chief Architect, Cloud Application Development at Red Hat) about the evolution of SOA and Microservices, Envoy Proxy and Istio Service Mesh, emerging application patterns, and how Kubernetes and Istio are the future of microservices.
Show Notes:

• Istio Homepage
• Envoy Proxy
• Introduction to Modern Load-Balancing and Proxying
• Microservices: From NetFlix OSS to Istio
• Microservic’ing Like a Unicorn
• Christian’s Blog (lots of Microservices stuff)

Topic 1 - Welcome to the show. Give us a little bit of your background as a developer and history of working with various development frameworks/languages/concepts.

Topic 2 - Let’s start with some basics - as a development paradigm, why are we now seeing technologies like Istio and Envoy? The premise of service mesh “reliably connecting services across the network” sounds eerily similar to what we heard about ESB technology. Can you say some words about why this service mesh concept idea is different? Or is it?

Topic 3 - So we’re seeing a need to decouple the application code from the routing-level logic and control. Walk us through the types of things that Istio and Envoy are providing for applications? What are the performance implications of the service mesh? How is this related to API management?

Topic 4 - Architecturally, where are you seeing some of the advantages of Istio / Envoy vs. either previous approaches, or some other service-mesh like projects in the market? (e.g. linkerd, Netflix OSS projects)

Topic 5 - What are some specific problem examples that people run into that should make them think “maybe I need Istio”?

Topic 6 - Where is Istio in its maturity to run in production?
Feedback?

• Email: PodCTL at gmail dot com
• Twitter: @PodCTL
• Web: http://podctl.com

Show: 57

Show Overview: Brian and Tyler talk about a significant security bug in Kubernetes, the recently announced Kubernetes 1.13 release, and the upcoming KubeCon event in Seattle.

Show Notes: 

• Kubernetes Privilege Escalation Flaw  - https://www.redhat.com/en/blog/kubernetes-privilege-escalation-flaw-innovation-still-needs-it-security-expertise
• Kubernetes 1.13 Release Announcement - https://kubernetes.io/blog/2018/12/03/kubernetes-1-13-release-announcement/
• What’s new in Kubernetes 1.13 - https://coreos.com/blog/whats-new-kubernetes-113
• OpenShift Commons Gathering Seattle (preview)- https://blog.openshift.com/openshift-commons-gathering-preview-your-personal-prelude-to-kubecon-seattle/

Kubernetes 1.13 Features

• Kubeadm is now GA
• CSI (Container Storage Interface) is now GA
• Core-DNS is now GA, replacing kube-dns (as default)
• Alpha - support for device monitoring plugins
• Stable - Kubelet Device Plugin Registration
• Stable - Topology Aware Volume Scheduling
• Beta - APIServer DryRun
• Beta - Kubectl Diff
• Beta - Raw Block Device with Persistent Volume

Feedback?

Email: PodCTL at gmail dot com
Twitter: @PodCTL
Web: http://podctl.com

Show: 8
Show Overview: Brian and Tyler talk with Jeremy Eder (@jeremyeder, Senior Principal Software Engineer at Red Hat) about the Kubernetes Resource Management Working Group, scaling Kubernetes environments, extending Kubernetes for high-performance workloads (HPC, HFT, Animation, GPUs, etc.), testing at scale and how companies can get involved.
Show Notes:

• KubeCon 2017 (Austin) Schedule
• OpenShift Commons Gathering (Austin, Dec.5th)
• Kubernetes Resource Management Working Group
• Contact the Resource Management Working Group
• Deploying 1000 Nodes of Kubernetes/OpenShift (Part I)
• Deploying 2048 Nodes of Kubernetes/OpenShift (Part II)

Topic 1 - Welcome to the show. You recently introduced the Resource Management Working Group within Kubernetes. Tell us a little bit about the group.
Topic 2 - The group’s prioritized list of features for increasing workload coverage on Kubernetes enumerated in the charter of the Resource Management Working group includes (below). Let’s talk about some of the types of use-cases you’re hearing that drive these priorities.

• Support for performance sensitive workloads (exclusive cores, cpu pinning strategies, NUMA)
• Integrating new hardware devices (GPUs, FPGAs, Infiniband, etc.)
• Improving resource isolation (local storage, hugepages, caches, etc.)
• Improving Quality of Service (performance SLOs)
• Performance benchmarking
• APIs and extensions related to the features mentioned above

Topic 3 - This is a broad list of areas to focus on. How do you determine what things should be kernel-level focus, Kubernetes-level focus, or application-level focus?
Topic 4 - How do you go about testing these areas? Are there lab environments available? How will you publish methodologies and results?
Topic 5 - As you talk to different companies, do you feel like they are holding back on deploying higher-performance applications on Kubernetes now, or they are looking for more optimizations?
Feedback?

• Email: PodCTL at gmail dot com
• Twitter: @PodCTL
• Web: http://podctl.com