Kubernetes is an open-source container cluster manager.
N/A
Red Hat OpenShift on IBM Cloud
Score 8.0 out of 10
N/A
Red Hat OpenShift on IBM Cloud is a comprehensive service that offers fully managed OpenShift clusters, on IBM Cloud platform. It is directly integrated into the same Kubernetes service that maintains 25 billion on-demand forecasts daily at The Weather Company.
For one of our banking clients, I have explored and played around the Kubernetes platform on IBM Cloud. In the process to deploy the application, I had to create the deployment artifacts, which was quite cumbersome. But then for one of the automotive clients I was asked to …
Red hat Openshift had a better user interface by far. Amazon EKS's was so basic it was essentially useless. We had to use a separate tool called lens to get basic stuff done. Lens was buggy and didn't work as well though, even for basic functionality like updating a K8s secret.
Red Hat OpenShift on IBM Cloud is a container application platform based on Kubernetes, that leverages our ability to start very quickly any containerized application developed with different languages, plus CI/CD, monitoring and logging and security.
1. The pricing is better than the other competitors. 2. We are already using other services being offered by IBM, so it makes better sense to utilize the IBM cloud red hat open shift. 3. Support is also valuable. 4. security is good. 5. constant updates on clusters. 6. cloud …
Red Hat OpenShift on IBM Cloud is best when it comes to security capabilities and hybrid scenarios. With Red Hat OpenShift on IBM Cloud we could provision new environments very quickly and in cost effective way. Customers could also use the cloud credits that they might have …
We are using IBM Cloud App ID as a simple method to get an OIDC provider for our applications, that are running within the OpenShift cluster. Also, IBM Cloud Object Storage is used within the workload to store data via an s3 compliant way. The IBM Cloud Container Registry is an …
K8s should be avoided - If your application works well without being converted into microservices-based architecture & fits correctly in a VM, needs less scaling, have a fixed traffic pattern then it is better to keep away from Kubernetes. Otherwise, the operational challenges & technical expertise will add a lot to the OPEX. Also, if you're the one who thinks that containers consume fewer resources as compared to VMs then this is not true. As soon as you convert your application to a microservice-based architecture, a lot of components will add up, shooting your resource consumption even higher than VMs so, please beware. Kubernetes is a good choice - When the application needs quick scaling, is already in microservice-based architecture, has no fixed traffic pattern, most of the employees already have desired skills.
RedHat OpenShift is not only suited for IBM Cloud but can run in ANY cloud. We installed in Azure Cloud, for example. It can also run on Linux servers or a Power 9 machine. It is built for multi-cloud or on-prem environments. IBM support provides such excellent guidance in the installation and configuration that no other product on the market can beat it.
Local development, Kubernetes does tend to be a bit complicated and unnecessary in environments where all development is done locally.
The need for add-ons, Helm is almost required when running Kubernetes. This brings a whole new tool to manage and learn before a developer can really start to use Kubernetes effectively.
Finicy configmap schemes. Kubernetes configmaps often have environment breaking hangups. The fail safes surrounding configmaps are sadly lacking.
The Kubernetes is going to be highly likely renewed as the technologies that will be placed on top of it are long term as of planning. There shouldn't be any last minute changes in the adoption and I do not anticipate sudden change of the core underlying technology. It is just that the slow process of technology adoption that makes it hard to switch to something else.
It is an eminently usable platform. However, its popularity is overshadowed by its complexity. To properly leverage the capabilities and possibilities of Kubernetes as a platform, you need to have excellent understanding of your use case, even better understanding of whether you even need Kubernetes, and if yes - be ready to invest in good engineering support for the platform itself
Most of the required features for any orchestration tool or framework, which is provided by Kubernetes. After understanding all modules and features of the K8S, it is the best fit for us as compared with others out there.
We evaluated a number of potential solutions and ultimately chose Red Hat OpenShift because it was compatible with our existing technology. Time and costs savings have been realized throughout the company since we implemented Red Hat OpenShift, and the IT department has been freed up to focus on activities that are more valuable.
