Kubernetes Reviews and Ratings

Use Cases and Deployment Scope

Kubernetes is widely used in the organization as the main workload for all microservices and applications, including infrastructure and dev/sec/ops deployments throughout the stack. Our Kubernetes software uses all of the orchestration's capabilities. As a tool for Kubernetes we use VMWare Tanzu.

Likelihood to Recommend

The Orchestrator is very well suited for fast-paced organizations where deployments are a must. It's also well-suited for organizations with multiple teams that want to use multiple Kubernetes clusters according to their needs. The scenario where it's less appropriate is with organizations that usually do not require containerized applications.

Use Cases and Deployment Scope

Kubernetes allows to create a unified compute and scheduling substrate across many potentially disparate providers and vendors. Even more importantly, this substrate can then be used to provide developers an abstracted platform to use. That, of course, requires layers of automations and services, but that's where the unified approach of using standardized Kubernetes-based APIs and concepts pays off. Everything else is just side effects and depends on how well you execute.

Likelihood to Recommend

Here's the thing - Kubernetes is a carrier grade platform. It is most definitely not for everyone. If you only need to manage a dozen computing nodes (or a couple dozen, for that matter), for a relatively small number of workloads, if your usage patterns are relatively static - it is very likely you do not *need* Kubernetes. Its complexity costs - in learning, in maintenance, in overhead. Simpler tools like docker-compose, Hashicorp Nomad or Amazon ECS might fit your use case more efficiently.

However, at certain scale of things - nodes, workloads, services, number of developer teams, Kubernetes starts to become a viable platform that can enable efficiencies of said scale, both operationally and conceptually.

Use Cases and Deployment Scope

We use Kubernetes to deploy our microservices on different servers automatically. The addressed business problems are deployment and lifecycle management of our microservices as well as checking the current state and command line output for troubleshooting if necessary. It's a very central software in our organization because it saves much time and helps to keep an stable environment

Likelihood to Recommend

We use Kubernetes in different scenarios in our company. These ones are the ones which are very well suited in my experience:

Microservices: We use microservices in our automation team and deploy them with Kubernetes. This works like a charm with Kubernetes as it is designed to manage multiple services. Also it's easy to deploy all the services on different namespaces and thus having validation, reference and production environments without having lots of maintaining work for these namespaces. Kubernetes helps to keep the system reliable and healthy and keeps old containers live when a new one fails to instantiate - this way it's not risky another to do system upgrades. Also keeping an overview of the complete system and it's state is pretty easy in this scenario. We also use k8s in cloud-native applications:

The same advantages as listed above apply to this scenario: It helps to focus on the applications itself because k8s supports the complete lifecycle management and supports scalability and reliability of the system. Kubernetes is in my experience not appropriate for small and non-containerized applications. Especially for small ones it's much easier to rely on docker because starting with Kubernetes and initially setting it up takes much more time and it would be overpowered for a small application. Also using K8s for non-containerized application could add a lot of workload as the application first needs to be adapted to fit in the requirements of k8s.

Use Cases and Deployment Scope

We use Kubernetes in a big bare metal cluster, and we are here at the Red Hat summit to talk about a migration directly to OpenShift to create an hybrid infrastructure that can help us to achieve a more resilient services for our clients, actually we got a lot of problem with the limits of k8s, especially with the calico service middleware, when our transactions are with high demand calico gets crazy and reset connections, for example, also we got and issue with the middleware limits, we are running 160 pods for worker, and we got 6 mega hardware workers, that we cant use it fully hardware for the middleware limits, thats the reason we are leaving k8s and working in a migration to OpenShift en AWS

Likelihood to Recommend

i think that Kubernetes is well suited in multiple deploys schemas where you don't need full access to the hypervisor, for other instances is better to use a virtualization schema, I think that today Kubernetes its a little bit green to move all traditional infrastructure, but for infrastructure oriented to microservices is better than swarm, because you can find better resources online and better support of the community, also works great within the limits

Use Cases and Deployment Scope

I deploy & manage telco workloads on top of Kubernetes. These are called CNFs (Containerized network functions) which are legacy telco applications converted into K8s objects & connected via a networking & storage solution of your choice, managed by K8s. Just like every other industry, Telcos are no exception converting all their legacy applications sitting on proprietary hardware & boxes to COTS hardware & software architectures adapted toward cloud technologies. Kubernetes helps us to manage the CNFs efficiently & gives a better uptime as compared to VM-based architecture. I see the scope of flexibility & easy scaling in K8s as compared to any other technology.

Likelihood to Recommend

<b><i><u>K8s should be avoided</u></i></b> - If your application works well without being converted into microservices-based architecture &amp; 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 &amp; 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.

<b><i><u> Kubernetes is a good choice</u></i></b> - 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.

Use Cases and Deployment Scope

We have multiple Kubernetes clusters that deploy mainly web-based applications. Containers/Kubernetes. Helm has become a widely used platform for deploying applications and many applications offer this as their preferred standard deployment.

Likelihood to Recommend

Kubernetes is well-suited for deploying stateless, web-based applications. We have had mixed results with deploying databases on Kubernetes, and suspect it has a lot to do with the characteristics of the underlying storage provider. Lastly, Kubernetes is not well-suited for non-HTTP workloads and those sensitive to certain IPs, e.g. SMTP gateways.

Use Cases and Deployment Scope

Currently we are using Kubernetes in our project to orchestrate the containers. We are using it for our banking client where some point of time user transection get increased while they try to use banking applications. whenever load get increase Kubernetes spin new pods in the cluster using replicaset to handle the load of user transections.

Likelihood to Recommend

Kubernetes really required where we expected user load fluctuate. Kubernetes handles it very well by spin new pods of same application when load get high and terminate pods when load get reduce. it do all these thing without any manual intervention. We just need to define the HPA to perform it. we can easily run it on clouds.

Use Cases and Deployment Scope

On the foundation, Kubernetes manages containers such as docker containers or from other technology and it helps you manage containerization applications that are made of hundreds of containers in different environments such as physical machines, virtual machines or cloud machines, or even hybrid deployment environments. As in my specific scenario, we install a Kubernetes cluster on CentOS 8 with one master node and two worker nodes for orchestration of our existing applications containers.

Likelihood to Recommend

Along with all the best features and support by k8s, the automatic container scheduling to worker nodes and also self-healing containers which is what I like the most. On the other side, when I was installing the k8s cluster on CentOS 8, it was quite difficult for me, but never mind it is working as we expected and it is a one-time effort. Especially, in my case, there are more than 7 application containers required to run and communicate with each other, so for us, Kubernetes is an optimal solution.

Use Cases and Deployment Scope

We have moved almost all the stateless services to Kubernetes so managing the umpty number of services can be so easy. Kubernetes helps us in scaling the services up or down based on business needs. It helps us in upgrading the bunch of clusters with zero to minimal downtime based on the applications. We also moved stateful database services (mostly NoSQL) to Kubernetes to manage a single place and to keep the cost down.

Likelihood to Recommend

Kubernetes as such makes our life easy in terms of deploying, orchestrating, and managing stateless and stateful services/pods from a single place along with security. We use k9s which makes it easier to manage Kubernetes because of the simple but effective GUI it provides. When it comes to database/stateful services we need to be more cautious when it comes to managing storage. Also, unless tested properly Kubernetes needs some more tweaking when it comes to hosting RDBMS databases.

Use Cases and Deployment Scope

I am working in a company that is currently working on moving everything to the cloud. We want to leverage as many as cloud managed services as we can. Kubernetes came to our sight when we thinking of containerizing our on-premises servers for fast and easy deployment to cloud. We are still experimenting with Kubernetes but based on what we've got now, it works perfectly for our department.

Likelihood to Recommend

If your company is 1) looking into moving to cloud, 2) thinking of designing a CI/CD pipeline, and 3) comfortable with taking the time and effort to deploy clusters, then Kubernetes is definitely worth the resources. It will bring much more benefits with almost no tradeoffs. But for small size companies who have few servers, Kubernetes might not be the best choice.