Deploying Kubernetes was the straightforward part of building a cloud-native platform at a bank, according to Marcy Paramonova and Stéphane Cusin. In a KubeCon & CloudNativeCon Europe talk reported by InfoQ, they described the harder work: establishing shared knowledge, collaboration and clear ownership.
Cusin said open source was initially met with questions about support and accountability in their banking environment. Rather than argue for it in theory, the team ran real workloads. Trust grew through the platform’s day-to-day operation.
The first version of their Kubernetes platform was delivered and adopted, but operating it was difficult. Responsibilities were unclear, and teams used the platform without contributing much to it. The team responded by building a community of practice and trying different ways for teams to work together. Paramonova said many improvements came from bottom-up feedback, including an annual ideas competition in which winning proposals were implemented.
In a follow-up interview, Cusin said the first platform exposed many Kubernetes capabilities and allowed extensive customization, which led teams to develop different deployment patterns. In the current version, Kubernetes is an implementation detail rather than the product itself. The platform instead offers preset deployment patterns, standardized Helm charts and shared capabilities to make software delivery more consistent across teams.
Paramonova said Kubernetes also gave teams a shared language, though it did not eliminate organizational silos overnight. Both speakers emphasized that trust came from reliable operation, transparency about what was not yet ready and clear responsibility when problems arose.