Isovalent Reviews

My main use case for Isovalent is using Cilium policies together with good visibility on the internal AKS traffic. For example, I use CDM policies and visibility for internal traffic in a scenario where Grafana Loki components are using different configurations inside the Grafana Loki deployment.

The best features Isovalent offers include excellent experience for traffic observability and a lot of nice features related to security hardening for Kubernetes deployment.

Unfortunately, I do not have any use case for those security hardening features for Kubernetes because this was only my testing and I have not implemented that on a production scale.

Isovalent has positively impacted my organization by increasing efficiency. The increase I noticed is the efficiency of the support teams. Isovalent helped my support teams be more efficient by decreasing time consumption related to troubleshooting for network-related issues.

I experienced some Hubble problems which were related to the huge internal traffic, which was somehow causing Hubble to hang and required a restart of Hubble. That is something that could be improved.

I have been using Isovalent for around four years.

Isovalent is stable. In my experience, Isovalent is stable and there has been nothing problematic as far as I am aware.

I have not seen any performance issues related to Isovalent products, so I am guessing it is good regarding scalability.

I do not remember right now about the customer support but have not had many support cases open for Isovalent products.

I did not previously use a different solution.

I think the return on investment question is not the best for me because if the metric includes decreased time of support related to network issues for the deployed applications, then fewer employees are needed from the support team. This is the biggest return on investment.

My experience with pricing, setup cost, and licensing is that it was not a big issue to configure.

I have not evaluated other options before choosing Isovalent.

The advice I would give to others looking into using Isovalent is that the biggest advantage from my perspective is that you can easily track what communicates with what, and this will give you a much better overview of what needs to be allowed in a secured and hardened environment.

My main use case for Isovalent is CNI for Azure Kubernetes. I deployed a multi-tenant Kubernetes environment based on Isovalent as CNI for the City of Amsterdam. Using Isovalent helped us resolve issues that were not previously allowed.

Isovalent has positively impacted my organization by helping improve the security and visibility. The use of Hubble really helped with the visibility of the environment and gave us insights for observability, which in turn helped with security. I observed fewer security incidents as a specific metric.

The best features Isovalent offers are based on eBPF. The specific features I find most valuable include the visibility using Hubble and the network policies. When using Isovalent within Hubble, the standout features are the insights provided and its integration with other observability tools that we are using.

I am happy with the features of Isovalent as they are now. Even small improvements are not needed as I am satisfied with it.

I have been using Isovalent for around three years.

I was running a Kubernetes cluster, and the main challenge that Isovalent helped my team with was the separation of all traffic between applications.

My advice to others looking into using Isovalent is to explore the different labs that are available on Isovalent to gain hands-on experience with it and to think very carefully about deploying it. I would rate this product a 9 out of 10.

My main use case for Isovalent is to practice eBPF and Cilium. I use eBPF for my learning, and I use Cilium to manage networking in Kubernetes, providing a specific example of how I integrate eBPF and Cilium with Isovalent in my day-to-day work.

The best features Isovalent offers in my experience include Isovalent Labs. I find its labs, PDFs, and documents to be valuable and interesting features.

Isovalent has impacted my organization positively as we are currently moving to Kubernetes and trying to add Cilium to manage networking. Since adding Cilium and managing Kubernetes with Isovalent, I have noticed specific outcomes including a lot of network rules, good visibility when we use Hubble, and the addition of mTLS support in Cilium.

I think Isovalent can be improved by adding more labs. I chose a rating of nine out of ten because I believe it would be better to add more labs and also be able to manage user profiles and change emails.

My advice to others looking into using Isovalent is to learn the ecosystem before applying it. I do have something else to add about how I use Isovalent, but I will not go into details. I would rate this product nine out of ten.