The New Stack Podcast

What is the context for Kubernetes if the data center is Mount Olympus? This is the first question for Alcide co-founder and CTO Gadi Naor in this episode of The New Stack Makers podcast, included in our latest ebook, "Kubernetes Deployment & Security Patterns." Naor made an analogy between the mythic Mount Olympus, home of the Gods, and the modern data center.

The comparison brings into play a concept about how the overall organization views infrastructure. The Olympus Naor describes as the data center now has the powers of Kubernetes. With the energy and force of such a power, how today’s organizations value and protect their core assets becomes a matter of first order.

The first value must be defined by how organizations treat security in Kubernetes. Security is not best used as an add-on, Naor says. It must be native to the deployment. A second consideration is zero-trust, which is best embodied in a security-first approach. There must be considerations of clusters and how microservices make transactions across the interconnected Kubernetes architecture.

What is the context for Kubernetes if the data center is Mount Olympus? This is the first question for Alcide co-founder and CTO Gadi Naor in this episode of The New Stack Makers podcast, included in our latest ebook, "Kubernetes Deployment & Security Patterns." Naor made an analogy between the mythic Mount Olympus, home of the Gods, and the modern data center.

The comparison brings into play a concept about how the overall organization views infrastructure. The Olympus Naor describes as the data center now has the powers of Kubernetes. With the energy and force of such a power, how today’s organizations value and protect their core assets becomes a matter of first order.

The first value must be defined by how organizations treat security in Kubernetes. Security is not best used as an add-on, Naor says. It must be native to the deployment. A second consideration is zero-trust, which is best embodied in a security-first approach. There must be considerations of clusters and how microservices make transactions across the interconnected Kubernetes architecture.

What is the context for Kubernetes if the data center is Mount Olympus? This is the first question for Alcide co-founder and CTO Gadi Naor in this episode of The New Stack Makers podcast, included in our latest ebook, "Kubernetes Deployment & Security Patterns." Naor made an analogy between the mythic Mount Olympus, home of the Gods, and the modern data center.

The comparison brings into play a concept about how the overall organization views infrastructure. The Olympus Naor describes as the data center now has the powers of Kubernetes. With the energy and force of such a power, how today’s organizations value and protect their core assets becomes a matter of first order.

The first value must be defined by how organizations treat security in Kubernetes. Security is not best used as an add-on, Naor says. It must be native to the deployment. A second consideration is zero-trust, which is best embodied in a security-first approach. There must be considerations of clusters and how microservices make transactions across the interconnected Kubernetes architecture.

What is the context for Kubernetes if the data center is Mount Olympus? This is the first question for Alcide co-founder and CTO Gadi Naor in this episode of The New Stack Makers podcast, included in our latest ebook, "Kubernetes Deployment & Security Patterns." Naor made an analogy between the mythic Mount Olympus, home of the Gods, and the modern data center.

The comparison brings into play a concept about how the overall organization views infrastructure. The Olympus Naor describes as the data center now has the powers of Kubernetes. With the energy and force of such a power, how today’s organizations value and protect their core assets becomes a matter of first order.

The first value must be defined by how organizations treat security in Kubernetes. Security is not best used as an add-on, Naor says. It must be native to the deployment. A second consideration is zero-trust, which is best embodied in a security-first approach. There must be considerations of clusters and how microservices make transactions across the interconnected Kubernetes architecture.

One of the most touted virtues of cloud-native application deployment is that it aims to free the software developer from having to worry about the state of their infrastructure. Cloud-native security is a service provided on behalf of the maintainer of the cloud-native development space who, in more and more enterprises, is someone in development. So how can cloud-native architectures be easier to use while also placing more responsibility on developers for delivering secure applications?

The New Stack correspondent Scott Fulton and Twistlock CTO John Morello discuss why cloud-native is the future of application development and what makes it inherently more secure.

“One of the characteristics of containers is that they’re very predictable, or they should be,” Morello said. “This allows you to do security in a more predictable, automated way.”

One of the most touted virtues of cloud-native application deployment is that it aims to free the software developer from having to worry about the state of their infrastructure. Cloud-native security is a service provided on behalf of the maintainer of the cloud-native development space who, in more and more enterprises, is someone in development. So how can cloud-native architectures be easier to use while also placing more responsibility on developers for delivering secure applications?

The New Stack correspondent Scott Fulton and Twistlock CTO John Morello discuss why cloud-native is the future of application development and what makes it inherently more secure.

“One of the characteristics of containers is that they’re very predictable, or they should be,” Morello said. “This allows you to do security in a more predictable, automated way.”

One of the most touted virtues of cloud-native application deployment is that it aims to free the software developer from having to worry about the state of their infrastructure. Cloud-native security is a service provided on behalf of the maintainer of the cloud-native development space who, in more and more enterprises, is someone in development. So how can cloud-native architectures be easier to use while also placing more responsibility on developers for delivering secure applications?

The New Stack correspondent Scott Fulton and Twistlock CTO John Morello discuss why cloud-native is the future of application development and what makes it inherently more secure.

“One of the characteristics of containers is that they’re very predictable, or they should be,” Morello said. “This allows you to do security in a more predictable, automated way.”

One of the most touted virtues of cloud-native application deployment is that it aims to free the software developer from having to worry about the state of their infrastructure. Cloud-native security is a service provided on behalf of the maintainer of the cloud-native development space who, in more and more enterprises, is someone in development. So how can cloud-native architectures be easier to use while also placing more responsibility on developers for delivering secure applications?

The New Stack correspondent Scott Fulton and Twistlock CTO John Morello discuss why cloud-native is the future of application development and what makes it inherently more secure.

“One of the characteristics of containers is that they’re very predictable, or they should be,” Morello said. “This allows you to do security in a more predictable, automated way.”

The goal for the Kubernetes community in 2018 is to make Kubernetes rock solid. Over the past year, the community has focused on building out the Kubernetes core. Networking, security and storage are all examples of Kubernetes projects that have matured quite a bit in the past year. For the new year, we shouldn’t necessarily expect major changes or even Kubernetes 2.0. Instead, it's a year to focus on the basics, providing a base on which different distribution providers can build out their unique offerings.

In this context, The New Stack Founder and Editor-in-Chief Alex Williams discusses existing and emerging deployment patterns with Ihor Dvoretskyi, Developer Advocate at the Cloud Native Computing Foundation in this podcast included in our latest ebook, “Kubernetes Deployment & Security Patterns.”

The goal for the Kubernetes community in 2018 is to make Kubernetes rock solid. Over the past year, the community has focused on building out the Kubernetes core. Networking, security and storage are all examples of Kubernetes projects that have matured quite a bit in the past year. For the new year, we shouldn’t necessarily expect major changes or even Kubernetes 2.0. Instead, it's a year to focus on the basics, providing a base on which different distribution providers can build out their unique offerings.

In this context, The New Stack Founder and Editor-in-Chief Alex Williams discusses existing and emerging deployment patterns with Ihor Dvoretskyi, Developer Advocate at the Cloud Native Computing Foundation in this podcast included in our latest ebook, “Kubernetes Deployment & Security Patterns.”