Six things to consider related to OpenShift resilience

Photo by Victoriano Izquierdo on Unsplash

1. Container resilience is not enough. You also need cluster resilience

Kubernetes (hence OpenShift) provides a lot of resilience for the container. Once a container dies and is part of a Deployment, StatefulSet, ReplicaSet, etc., Kubernetes will restart it.

2. Share nothing across your cluster

The clusters should be completely independent, without sharing any resource.

3. Consider small, simpler clusters

I have been working with Kubernetes for 4 years. Not as long as my employer (IBM) asked in this job description: https://intellijobs.ai/job/IBMCloud-Native-Infrastructure-Engineer-Architect-bvJJ6yraexfWOk1nMRKP-bvJJ6yraexfWOk1nMRKP.

4. Have a Continuous Delivery process to deploy the resources

Containers bring a new way of developing applications: small components (you can call them microservices), developed, and deployed independently.

  • How to redeploy an application?
  • How to back up the application resources?
  • How to trace back the application deployment?

5. Deploy your application in an Active-Active mode

An OpenShift cluster is just a cluster. It sits somewhere eager to run Kubernetes applications. Regarding resilience, what matters is how these applications are deployed across the clusters.

6. Design your application considering many clusters upfront

OpenShift makes it simple to create a container-based application, then scale it, using many replicas and autoscaling.

Conclusion

OpenShift is an exciting platform, and deploying applications to it is even more exciting.

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store