Building a Kubernetes-Based Platform Culture in Banking
Marcy Paramonova and Stéphane Cusin share how banks successfully adopt cloud-native cultural practices.
1Overcoming Initial Skepticism
In a highly regulated banking environment, adopting open source technology initially faced significant resistance regarding support and accountability. Marcy Paramonova and Stéphane Cusin bypassed theoretical debates by running real production workloads. This hands-on approach demonstrated reliability over time, proving that open source could serve as a stable foundation for critical banking infrastructure.
2The Cultural Challenge
Deploying Kubernetes technology proved easier than establishing the necessary organizational culture. Early efforts suffered from blurry responsibilities and a lack of shared knowledge, turning every incident into a chaotic fire drill. The team realized that without rituals, ownership models, and a community of practice, even a technically sound platform cannot survive.
3Open Source as Compass
The team utilized open source projects as a compass to navigate uncertain technological landscapes. By observing transparent governance and production adoption in Kubernetes, they recognized a viable opportunity for their own organization. This strategy allows them to identify and follow industry trends without being forced into rigid, pre-determined paths by external vendors.
4Bottom-Up Innovation
To foster engagement, the organization encourages bottom-up improvements through initiatives like yearly competitions where staff submit ideas for implementation. This deliberate design of team interactions ensures that the culture evolves based on what actually works in practice. By experimenting and keeping successful methods, they built a resilient, collaborative environment for engineers.
5Redefining the Product
The team learned that developers do not seek infrastructure choices, but rather a streamlined way to deliver software. Consequently, they shifted their focus: Kubernetes is now treated as an implementation detail rather than the product itself. The actual product is a standardized, secure, and simple software delivery experience for all internal teams.
6Standardization and Mobility
By providing opinionated deployment patterns and standardized Helm charts, the organization ensures consistency across teams. Engineers moving between departments no longer need to relearn how applications are packaged, monitored, or deployed. This common operating model reduces cognitive load and allows developers to focus entirely on building and shipping their core applications.
7Breaking Down Silos
Kubernetes acted as a catalyst for organizational change by providing a common language for different engineering units. Previously, knowledge was trapped within specific technology stacks or isolated teams. Shared abstractions now enable more natural collaboration, fundamentally changing the nature of technical conversations and expanding the possibilities for what the engineering organization achieves.
8Lessons for Success
Trust in a platform is built through transparency, reliability, and being present when issues arise. The transformation highlights that structure must precede culture, but culture ultimately sustains the platform. For regulated environments, the journey requires a clear compass and a commitment to continuous improvement, ensuring the organization remains agile despite inherent constraints.
Original article: InfoQ — Building a Kubernetes-Based Platform Culture in Banking