ISL wanted to modernize its development cycle with containers and OpenShift — but adopting a platform without the right know-how is a guaranteed failure. We enabled their development and operations teams to own the technology, closed the DevOps gap, and compressed deployment times from 4–5 days to just hours.
ISL made the right call betting on containers and OpenShift. The real challenge wasn't the technology — it was getting people to truly own it.
The real adoption challenge
ISL acquired OpenShift on VMware Cloud on AWS (VMC) to speed up its development cycle and scale elastically. But a powerful platform without teams trained to run it is just expensive technical debt. The real challenge wasn't installing the tool — it was getting development and operations to own it, in an institutional environment with established processes and natural resistance to change.
Speed vs. control silos
Dev wanted speed. Ops wanted control. Without a shared DevOps methodology, every deployment was a negotiation. Applications reached production after 4 to 5 days of manual coordination, ad-hoc reviews, and people-to-people dependencies — not system-to-system.
Modernization on faith, not data
Without observability, no one knew if the process was working well or simply hadn't blown up yet. There were no lifecycle metrics, no dashboards, no evidence to justify the investment. Modernization was faith — not data.
We designed a gradual adoption program that started where the teams were — not where we wanted them to be.
We designed an enablement program calibrated to ISL's real context — not generic training. Hands-on workshops in Git, Containers, Jenkins, and OpenShift for dev and ops teams, learning directly on the production platform. We installed OpenShift v4 in parallel so knowledge was anchored in practice from day one.
We implemented CI/CD pipelines with Jenkins and GitLab, connected directly to OpenShift. Each team learned to deploy autonomously — from development to production — without intermediaries or maintenance windows. The result: real self-service, with the process supervised by the platform, not by people.
We integrated ElasticSearch, Fluentd, and Kibana to give end-to-end visibility into the new process. For the first time, teams could see lifecycle metrics, detect bottlenecks, and prove the value of modernization with data. Observability wasn't an add-on — it was the argument for continued investment.
Government · Chile
Deployments taking 4 to 5 days, dependent on people and informal processes. Two teams working in parallel with no shared methodology. No process visibility or evidence of efficiency.
DevOps enablement program for dev and ops. OpenShift v4 installation and CI/CD pipelines with Jenkins and GitLab. Full observability stack with ElasticSearch and Kibana.
Deployments in hours, not days. Teams that self-serve on OpenShift without manual coordination. Real-time metrics to prove and sustain the modernization investment.
"The project was executed integrating the development, architecture, and operations teams, collecting questions that arose throughout the process. The Andes team responded with clarity and in plain language, successfully managing the change."
— Marco Mendoza, Instituto de Seguridad Laboral
The full ecosystem implemented to enable and automate ISL's container platform.
Technology without enablement transforms nothing. Let's talk about how we move your team from resistance to mastery — with measurable results from the very first stage.
Schedule a meeting →