Kubernetes Reviews

What is our primary use case?

It's a mobile phone application with a website written in Angular 8. It's a strategic microservices solution. There are a lot of containers and resources. The application is written in Java, and we are using Spring Boot, the second version. We are also using the application-gateway of Azure. If you want to do the microservices strategy, you need to split the services to the smaller work. There must be containers in Docker. There are not that many good solutions for Docker. So right now, if you need to use Docker, you choose Kubernetes because they are number one for the container orchestration… more »

What other advice do I have?

Kubernetes is a great product. I am currently also helping a customer with the implementation of AKS because they only have a private cloud, and they want to have a hybrid cloud. I highly recommend to use this feature, and not to install Kubernetes manually or use some third-party tools. The Azure community service is better implemented than AWS community service. They are not good at planning the upgrades for Kubernetes. So, you really need to constantly upgrade the cost. The upgrade is automatic, but Azure changed the integration of load balancing, and I was forced to re-deploy all costs…

What is our primary use case?

We primarily use the solution for deploying containers and scheduling the jobs to the Kubernetes for our server-side deployment.

What other advice do I have?

I would advise new users to take the managed solution. Don't deploy it by yourself. Just take a managed service. It's really worth it. I advise this due to the fact that it's a lot of time and effort. It's not that expensive in terms of overhead. It may be $100 or $200 or something like that monthly. When you pay $3,000, let's say, the $100 doesn't really matter. However, the work that your DevOps will have will be costly. They will initially invest to maintain your unmanaged deployment. On a scale from one to ten, I would rate this solution a ten.

What is our primary use case?

The following is a list of the cases when I prefer Kubernetes for application hosting: * Micro-services infrastructure + possible use of some service meshes, like Istio or Linkerd. * Cost efficiency; we are using Kubernetes in conjunction with AWS Spot Instances or Google Cloud preemptible VMs. * Standards-compliant infrastructures like HIPAA, PCI SOC, DSS, and ISOxxxx. * Highly-available or fault-tolerant infrastructures, due to some sort of self-recovery and self-healing. * Infrastructures with automatically scalable applications.

What is our primary use case?

We primarily use the solution for orchestration. Most of the clients we work with are enjoying the DevOps aspects of Kubernetes. They want to be able to safely and quickly deploy new applications. Others just enjoy the modern way they can deploy containers without being a DevOp company.

What other advice do I have?

I am a consultant, and I am just providing information about how to use this kind of software within specific companies. Kubernetes is evolving now. 1.18 is the latest version, however, we don't have the newest version everywhere. That's the one we choose for new installs when we do them. When it's deployed on the cloud, some of my customers are using public clouds such as Amazon, Google, or Microsoft. There are also some customers that use private clouds here in Switzerland. I work together with them. If people are using modern technologies like containers or developing software by…

What is our primary use case?

We are platinum partners with Oracle and we are preferred partners with Microsoft. I work for an organization which is on both sides of the coin. We are a service integrator organization. We don't have a specific loyalty, we blend in and provide the services. I'm a solutions architect.

What other advice do I have?

I would recommend going through the training to see what the limitations are within Kubernetes. There's not a lot of training, but what training is available should be used so people can understand the difference between Docker and Kubernetes. If somebody has used Docker previously, they can see the difference even though the methods are the same. It's the same madness, but it will help you to better position things like command line interfaces. We had a bit of a struggle when I was trying to implement it in Azure. But if you look at the Oracle implementation, it worked really well so I would…

What is our primary use case?

The use case in this organization is basically to containerize the applications. It covers both the operational and technology side. I work in the train industry here and that is a medium-sized enterprise. I'm a cloud architect and we are customers of Kubernetes.

What other advice do I have?

I like the solution but it depends on the size of your workload. For example, Docker is good for a very small workload or maybe if you are just deploying using Docker, building and deploying your CICD-based tasks. But if you require a more complex solution, using containers or maybe when you have a high traffic workload, even with simple architecture, you might be looking at Kubernetes to optimize the workload. There are other solutions on the market like Serverless, I would use that in preference to Kubernetes which can sometimes be difficult to manage. You can always make use of Serverless…

What other advice do I have?

I would recommend this product. It is very close to being a 100% agnostic solution. It is just a step away from becoming a server-less solution like Fusion, which, although, is designed for running for a short time. I use Kubernetes on the platform layer to deepen a platform. In some cases, when the same solution was developed without Kubernetes, some customers had issues on platforms like AWS, Azure, and Google. I would rate Kubernetes an eight out of ten.