The New Stack Podcast

In this interview with Jennifer Tejada, CEO of PagerDuty, recorded live at PagerDuty Summit 2017, she discusses the new and emerging challenges in streamlining operations, in introducing automation and achieving integration. Team members must play new and yet-to-be-defined roles in improving IT to better deliver value to the customer. Tejada speaks with Scott Fulton about her own customer success stories and also about the extent human beings need to be involved in driving the commitment to DevOps.

Watch on YouTube: https://youtu.be/Y2VZguLJVuI

Kubernetes now faces an evolutionary hurdle that only Docker before it has faced so soon in its life cycle: the problem of multiple concurrent versions. Version 1.7 is upon us today, even though other versions are still in active use. At the rate Kubernetes is evolving now, over a dozen viable versions could be deployed over the standard life cycle of organizations’ IT projects — some three to four years’ time.

“We try to make every new Kubernetes release as stable as possible,” said Caleb Miles, who leads the Kubernetes Project Management SIG. “We have a long code freeze and stabilization period to shake out any of the rough edges before a new version of Kubernetes lands.”

Learn more about how the Project Management SIG maintains consistency and concurrency without introducing obsolescence, in this special edition of The New Stack Makers podcast.

Kubernetes now faces an evolutionary hurdle that only Docker before it has faced so soon in its life cycle: the problem of multiple concurrent versions. Version 1.7 is upon us today, even though other versions are still in active use. At the rate Kubernetes is evolving now, over a dozen viable versions could be deployed over the standard life cycle of organizations’ IT projects — some three to four years’ time.

“We try to make every new Kubernetes release as stable as possible,” said Caleb Miles, who leads the Kubernetes Project Management SIG. “We have a long code freeze and stabilization period to shake out any of the rough edges before a new version of Kubernetes lands.”

Learn more about how the Project Management SIG maintains consistency and concurrency without introducing obsolescence, in this special edition of The New Stack Makers podcast.

Kubernetes now faces an evolutionary hurdle that only Docker before it has faced so soon in its life cycle: the problem of multiple concurrent versions. Version 1.7 is upon us today, even though other versions are still in active use. At the rate Kubernetes is evolving now, over a dozen viable versions could be deployed over the standard life cycle of organizations’ IT projects — some three to four years’ time.

“We try to make every new Kubernetes release as stable as possible,” said Caleb Miles, who leads the Kubernetes Project Management SIG. “We have a long code freeze and stabilization period to shake out any of the rough edges before a new version of Kubernetes lands.”

Learn more about how the Project Management SIG maintains consistency and concurrency without introducing obsolescence, in this special edition of The New Stack Makers podcast.

In the young history of container orchestration, one of the most successful practitioners of merging the microservices mindset with enterprises’ development and deployment pipelines, has been the Berlin-based director of engineering for CI/CD platform provider Codeship, Laura Frank.

The more businesses Frank has come into contact with as a “Docker Captain,” the more she has come to understand the cultural issues facing developers in organizations today, and the extent to which platforms like Kubernetes may stop short of catalyzing revolutionary changes in and of themselves. Hear more about “Captain” Frank’s experiences with businesses that are trying to navigate these new and still-uncharted waters, in this edition of The New Stack Makers.

In the young history of container orchestration, one of the most successful practitioners of merging the microservices mindset with enterprises’ development and deployment pipelines, has been the Berlin-based director of engineering for CI/CD platform provider Codeship, Laura Frank.

The more businesses Frank has come into contact with as a “Docker Captain,” the more she has come to understand the cultural issues facing developers in organizations today, and the extent to which platforms like Kubernetes may stop short of catalyzing revolutionary changes in and of themselves. Hear more about “Captain” Frank’s experiences with businesses that are trying to navigate these new and still-uncharted waters, in this edition of The New Stack Makers.

In the young history of container orchestration, one of the most successful practitioners of merging the microservices mindset with enterprises’ development and deployment pipelines, has been the Berlin-based director of engineering for CI/CD platform provider Codeship, Laura Frank.

The more businesses Frank has come into contact with as a “Docker Captain,” the more she has come to understand the cultural issues facing developers in organizations today, and the extent to which platforms like Kubernetes may stop short of catalyzing revolutionary changes in and of themselves. Hear more about “Captain” Frank’s experiences with businesses that are trying to navigate these new and still-uncharted waters, in this edition of The New Stack Makers.

One of the people without whom Kubernetes would not exist, and perhaps the whole notion of orchestration would never have come to fruition, does not believe Kubernetes is truly at the center of the emerging ecosystem. Yes, we call it a “Kubernetes Ecosystem,” but Google’s Tim Hockin explained that he sees the platform as a hub for a greater kind of ecosystem to come.

“Part of what Kubernetes really set out to do at the beginning,” said Hockin, “was to provide the hub of ecosystems, plural. There’s the network ecosystem, the storage ecosystem and the security ecosystem.”

Listen now to 'Kubernetes 1.7 and Extensibility,' part of The New Stack Makers podcast, and learn how the platform’s new extensibility model could enable integration with security policy, using whatever policy model you happen to have on hand.

One of the people without whom Kubernetes would not exist, and perhaps the whole notion of orchestration would never have come to fruition, does not believe Kubernetes is truly at the center of the emerging ecosystem. Yes, we call it a “Kubernetes Ecosystem,” but Google’s Tim Hockin explained that he sees the platform as a hub for a greater kind of ecosystem to come.

“Part of what Kubernetes really set out to do at the beginning,” said Hockin, “was to provide the hub of ecosystems, plural. There’s the network ecosystem, the storage ecosystem and the security ecosystem.”

Listen now to 'Kubernetes 1.7 and Extensibility,' part of The New Stack Makers podcast, and learn how the platform’s new extensibility model could enable integration with security policy, using whatever policy model you happen to have on hand.

One of the people without whom Kubernetes would not exist, and perhaps the whole notion of orchestration would never have come to fruition, does not believe Kubernetes is truly at the center of the emerging ecosystem. Yes, we call it a “Kubernetes Ecosystem,” but Google’s Tim Hockin explained that he sees the platform as a hub for a greater kind of ecosystem to come.

“Part of what Kubernetes really set out to do at the beginning,” said Hockin, “was to provide the hub of ecosystems, plural. There’s the network ecosystem, the storage ecosystem and the security ecosystem.”

Listen now to 'Kubernetes 1.7 and Extensibility,' part of The New Stack Makers podcast, and learn how the platform’s new extensibility model could enable integration with security policy, using whatever policy model you happen to have on hand.