ECI-SRV-05
Containerisation and application platforms
A container platform is only worth something if the development teams adopt it and the operations team can keep it running. We deploy production-ready Kubernetes and OpenShift clusters, with the persistent storage, security and delivery pipelines that make them genuinely usable.
Scope of work
- Deployment of Kubernetes and OpenShift 4.x clusters in production.
- Persistent storage, storage classes and Ceph or ODF integration.
- Networking, ingress, network policies and secure service exposure.
- Security: RBAC, Pod Security, secret management, image registry.
- GitOps delivery pipelines and migration of applications to containers.
Deliverables
- A containerised cluster in production, documented and monitored.
- A working continuous delivery pipeline.
- A good-practice reference and deployment templates.
- Upgrade and cluster backup procedures.
Kubernetes or OpenShift
Both platforms share the same core. The choice is about the operating model and the level of support you need, not about technical capability.
| Criterion | Kubernetes | OpenShift |
|---|---|---|
| Model | Community distribution, assembled component by component | Integrated distribution, Red Hat subscription |
| Operations | Components chosen and maintained by your teams | Console, operators and upgrades provided |
| Support | Community, or a support contract with us | Vendor support included in the subscription |
| Typical fit | Self-sufficient teams, development environments, cost control | Critical applications, compliance requirements, contractual support |
We deploy both and resell neither: should you choose the Red Hat subscription, it is contracted directly with the vendor or its distribution network.
Technologies
- Kubernetes, OpenShift 4.x, OpenShift Virtualization and KubeVirt.
- Helm, ArgoCD, GitLab CI/CD, private image registry.
- Ceph CSI, OpenShift Data Foundation, Prometheus and Grafana.
Engagement terms
Fifteen to forty days depending on the application scope, fixed price or supervised time and materials.
How the engagement runs
Phase 1 — Framing
- Review of the application portfolio and of the platform requirements.
- Choice between Kubernetes and OpenShift, and architecture design.
Phase 2 — Foundation
- Deployment of the cluster, persistent storage and networking.
- Hardening, project governance and image registry.
Phase 3 — Continuous delivery
- Implementation of CI/CD pipelines and GitOps practices.
- Deployment templates and per-team environments.
Phase 4 — Adoption
- Migration of a first reference application.
- Support for the teams and transfer of skills.
What every engagement includes
- A detailed quote, issued after framing
- A named project manager
- Operating documentation delivered
- Transfer of skills to your teams
- Work carried out on site or remotely
- Support after go-live
No work in production without a written rollback plan.
Request a framing session
Or contact us directly:
Let us talk about your situation
Every engagement begins with a framing exercise and a detailed quote.
Book an appointment