Should Developers Be Allowed Anywhere Near Kubernetes? – InApps Technology is an article under the topic Software Development Many of you are most interested in today !! Today, let’s InApps.net learn Should Developers Be Allowed Anywhere Near Kubernetes? – InApps Technology in today’s post !
Read more about Should Developers Be Allowed Anywhere Near Kubernetes? – InApps Technology at Wikipedia
You can find content about Should Developers Be Allowed Anywhere Near Kubernetes? – InApps Technology from the Wikipedia website
Listen to all TNS podcasts on Simplecast.
Do developers need to interact with the Kubernetes open source container orchestration engine at all? That was one of the many intriguing questions we got from the audience during our second pancake podcast, held Thursday, at the Cloud Native Computing Foundation’s Kubecon 2017. We caught it all here on this latest edition of InApps Technology Analysts podcast.
Sponsored by Alcide and Chef, this panel discussion set out to explore the “Evolving Patterns in Kubernetes.” Leading the discussion, moderated by TNS founder Alex Williams, were the following panelists:
As application development appears to be slowly reconfiguring around microservice-based architectures, questions from the audience naturally centered on how to adopt this new paradigm within existing enterprise IT management. While working together to form an application, each of the microservices must be unit-tested individually, to ensure the whole system will operate, noted Jeyakeerthi, who was with Twitter when that company delved into microservices. He noted that isolation testing must be done across three dimensions: security, failure and performance.
Security, naturally, was a big area of concern. Service meshes proved to be popular at this year’s event, and one of the reasons for this was that they provide a greater level of observability, Naor noted. You still need to dig into the microservices once a breach happens, he noted. When something goes wrong, developers want to ssh into their microservices, the way they have always done, von Buelow added, noting that this, in itself, is a bad security practice (as is having an ssh client in a container at all).
Kubernetes has the reputation of being difficult to manage. The question of whether system administrators should allow access to production K8s instances at all was one also mulled by the panel. After all, Chef’s Habitat provides a fully-automated pipeline that allows devs to package their applications along with their dependencies and deliver them to a Kubernetes environment, Drew noted. (Chef just released a connector to make this transition even more smooth).
In This Edition:
3:25: Some of the themes at KubeCon in context with the idea of evolving patterns and service mesh.
6:55: How Chef Habitat fits into the evolving patterns we are starting to see emerge around an application-oriented development.
16:07: What Habitat does for developers when using Kubernetes.
27:16: Holistically dealing with building infrastructure, service mesh, and policy between microservices.
31:11: Security and observability in a service mesh infrastructure.
35:44: How Kubernetes is going to evolve from a developer perspective as technology shifts.
Let’s create the next big thing together!
Coming together is a beginning. Keeping together is progress. Working together is success.