Agronod built a self-service OpenShift platform for its development teams, then successfully migrated it to Kubernetes with an incremental plan that avoided disruption to production workloads.

The challenge

Agronod set out to give its development teams a reliable, self-service container platform, choosing OpenShift as the foundation but lacking in-house platform engineering experience. Later, as its platform strategy evolved, Agronod needed to migrate to Kubernetes — a delicate undertaking since the platform was by then carrying production workloads and depended on several OpenShift-specific capabilities.

The solution

Stakater's consultants worked directly with Agronod's eineers to design and build the OpenShift platform into production. For the later Kubernetes migration, Stakater helped assess which OpenShift-specific capabilities needed replacing, chose the replacements, and planned an incremental migration path that let teams move over without a single disruptive cutover.

Customer quote

“Stakater helped Agronod first build our OpenShift platform and later migrate off it onto Kubernetes — two very different projects, both handled well. Their consultants were technically excellent and, just as importantly, clear communicators who worked as part of our team rather than alongside it. The migration touched a lot of moving parts, and Stakater’s experience with both platforms meant we avoided pitfalls we would otherwise have discovered the hard way. We would recommend them to any organisation building or evolving a Kubernetes platform.”

Chstian Backman, Chief Technology Officer, Agronod

Delivery details

Agronod set out to give its development teams a reliable, self-service container platform. It chose OpenShift as the foundation and engaged Stakater to help design and build it. Stakater’s consultants brought platform engineering experience Agronod did not have in-house at the time, working directly with its engineers to get the platform into production.

Later, as Agronod’s platform strategy evolved, the decision was made to move to Kubernetes. This was a more delicate piece of work: the platform was by then carrying production workloads, and a number of capabilities Agronod’s teams depended on were OpenShift-specific. Stakater helped assess what would need to be replaced, chose the replacements, and planned a migration path that let teams move over incrementally rather than in a single cutover.

The result is a Kubernetes platform that meets Agronod’s needs, with the migration completed without significant disruption to its teams. What stood out across both engagements was the combination of genuine technical depth and clear communication — Stakater explained trade-offs in terms Agronod’s stakeholders could act on, and left its own engineers better equipped to run the platform themselves.

Why Stakater

• Deep experience across both OpenShift and Kubernetes, avoiding pitfalls in the transition
• Consultants who worked as part of the team, not alongside it
• Incremental migration planning that avoided disruption to production workloads
• Clear communication that left in-house engineers equipped to run the platform themselves