December 19, 2018 | Written by: Douglas Paris-White
Categorized: Compute Services | Events
Share this post:
The Cloud Native Computing Foundation’s flagship conference gathered adopters and technologists from leading open source and cloud-native communities in Seattle, WA from December 10-13, 2018.
IBM Cloud kicked off its week on Monday with an Istio hands-on lab where a packed house learned how Kubernetes and Istio make it easy to bind apps to Watson, Blockchain, and IoT. More than 200 participants left with certification badges to prove their proficiency.
Following the Istio workshop, at the IBM Cloud Garage ArcadeCon, 120 attendees got to munch on local eats from the Pike Place Market, play an ‘80s-themed set of arcade games and music, and learn how the IBM Cloud Garage is helping enterprises adopt cloud-native development.
IBM Cloud booth
The IBM Cloud booth was constantly full of visitors. Twenty-eight in-booth sessions covered topics that included leveraging Istio incrementally across the enterprise, bridging serverless computing into Kubernetes with Knative, and a partnership with Sysdig that brings end-to-end cloud monitoring of cloud-native apps.
One highlight was IBM Distinguished Engineer Dan Berg’s talk on The Weather Company’s migration to the IBM Cloud. The Weather Company currently leverages Kubernetes to ensure that, during inclement and extreme weather, consumer services remain reliably available.
Booth visitors also got a virtual tour of the IBM Cloud Garage and were invited to trade-in steps recorded in the CloudCoins app for IBM Cloud swag.
IBM Fellow and CTO Jason McGee discussed the unification of containers, apps, and functions. Driven by Kubernetes, Istio, and the emergence of Knative into a single combined container platform, the silos brought on by traditional development in the cloud are breaking down as these project’s paths converge. Microservices dilemmas around security, scale, and operations are no longer left unsolved.
Interviews on cloud-native dev and Kubernetes
IBM Cloud Kubernetes Service and IBM Cloud Garage subject matter experts joined hosts of The Cube to talk about the primary goal of many conference attendees: automating DevOps so that teams using Kubernetes can spend as much time as possible on creating and improving customer-facing business apps.
Assess your team’s cloud-native dev readiness
- Chris Rosen (Senior Product Manager, IBM Cloud Kubernetes Service) talks about the expanded Kubernetes ecosystem as the big story of the conference. Chris mentions security as the biggest request he hears from public and private cloud customers alike and covers the programmability of virtual private clouds as a recent addition to the security toolset for enterprises working on cloud-native app development within hybrid cloud deployments.
- IBM Distinguished Engineer Daniel Berg teams with his counterpart from LogDNA, Norman Hsieh, to discuss the partnership to bring real-time observability to Kubernetes deployments at scale, dramatically relieving ops pressure on cloud-native DevOps pipelines.
- IBM Fellow and IBM Cloud CTO Jason McGee talks about the extensibility of the Kubernetes core stack (containerd, Kubernetes, Prometheus, Istio, Knative) in allowing different approaches to solving core problems to coexist in the open source community and/or to compete as long as needed for one to earn recognition as superior. At the same time, McGee reminds us that DevOps teams, always wanting to keep focus on rapidly creating and iterating their apps, gain the ability to easily consume the forms of compute that best fit their purposes. And they can easily consume, too, the AI and other advanced services that IBM Cloud makes available via API endpoints and keeps available as high-scale deployments within the IBM Cloud Kubernetes Service itself.
- Roland Barcia, IBM Distinguished Engineer and CTO for Microservices, explains why the hard part of doing cloud-native app development is not writing the app but instead performing the operations that scale and maintain it. To get used to it, he suggests finding some part of an existing app to move into containers, allowing the team to setup an effective DevOps pipeline. With that done, the team is usually ready to begin the work of innovating the user experience and getting the efficiencies related to automation.