|
Show: 62
Show Overview: Brian talks with Fabian von Feilitzsch (@fabianismus, Sr. Software Engineer at RedHat) and Shawn Hurley (@shawn_hurIey, Sr. Software Engineer at Red Hat) about Ansible Operators, how they work with Ansible Playbook, on-platform and off-platform usage, and examples to help people learn the new Kubernetes technology.
Show Notes: Topic 1 - There are multiple types of operators: Go, Ansible, Helm. What are the basic things that the Ansible Operator does - in the context of the Operator Framework? Topic 2 - A couple months ago we saw you in a video called “What is a Service Mesh?”. It was intended to be a “let’s make this simple” and you realize that a Service Mesh could be a lot of things - L4-L7 routing, Proxy, Encryption, Authentication, Application patterns. Is a Service Mesh solving a new problem, or is it pulling together lots of things that have existed at L4-L7 and application stacks in the past? Topic 3 - “Service Mesh” has become a pretty crowded and fragmented market over the last couple years. HashiCorp Consul has been around since 2014 (was originally “Service Discovery”) and now there’s Linkerd, Istio, Envoy and a bunch of variations. As you talk to people in the market, how are they evaluating the options out there? Topic 4 - Consul has evolved from Service Discovery to Service Mesh, and seems to have come from more of an authentication and security perspective (some others tends to be more routing-centric). Are there use-cases when one Service Mesh is a better fit than others, or should we expect that all/most of them will more or less converged on features over the next 12-24 months? Topic 5 - Can you give us some examples of how companies are using Service Meshes today (parts or all of the capabilities) and what teams are usually driving the adoption (infra/ops, security, app-dev, etc.)? Feedback?
Email: PodCTL at gmail dot com Twitter: @PodCTL Web: http://podctl.com |