Rancher Labs is currently investing in Harvester, as it is an area where improvements are required. I think that in the future, it would be a very powerful tool to compete with giant competitors like VMware, Hyper-V, Proxmox, and other related solutions. The more features it adds, the more the tool's portfolio will be enlarged, making it an appealing product.

I can't migrate to the newer version. The aforementioned area needs to be considered for improvement in the solution.

One area for improvement in Rancher Labs is the development aspect. Unlike some competitors like OpenShift, Rancher Labs may not offer a complete suite of products for development needs, which could benefit from enhancement. Rancher Labs could enhance its offerings by expanding beyond Kubernetes and providing more support for various organizational processes and developer use cases in the future.

The biggest room for improvement in Rancher Labs would be to have a proper upgrading plan. I've seen a few bumps in the past when you upgrade Rancher Labs from one version to a newer version. For example, upgrading from version two dot one to version two dot two was a really big mess, and the whole cloud cluster broke down. That made me very cautious about upgrading Ranger from one version to another. A proper testing environment is an absolute must.

Since it is an open-source solution, one can integrate it with any tool. Also, many tools are integrated with it already. There needs to be an improvement in observability and microservice monitoring tools in Rancher Labs.

In the future, I would like to see Rancher Labs focus on increasing its popularity within the open-source community and on developing new tools for the community. It would be great to see more tools released by the large community of Rancher Labs.

The features like that included in Kubernetes, Q, EKS, and AECS should be included in the Rancher Labs.

We'd like their monitoring tool to be integrated by default. It would be great for a cluster monitoring tool. 

While Rancher Labs provides some level of security, it's not considered very robust. We found it to offer basic security features, which met some of our requirements, but we also relied on other open-source solutions for additional security measures. The main improvement I'd like to see in Rancher Labs is better support for multicloud deployments. This would address a lot of existing issues.

We have found that the auto-secure feature of this solution doesn't always work, and could be improved to be more reliable, particularly when working with business critical applications.

I'd like to see this solution become more stable and have more integrations with other Rancher Labs products, such as Rancher Longhorn.

The solution could improve by adding more features in the dashboard, such as monitoring, scanning, and security. This would be a great benefit.

We're looking for something that is even easier to use. It's a bit complicated. When you're dealing with Kubernetes, it is easier, however, there's still a lot of convoluted types of commands. 

The situation goes pretty deep and when things go South, you spent a lot of time trying to figure things out, and it takes a certain amount of skillsets. To ramp up those skillsets takes time. Unfortunately, we don't have the time to ramp up those skillsets to bring those things in. There are other solutions out there such as HashiCorp, which offers its own version of managing containers. It doesn't use Kubernetes; is a different way of doing it.

The product could use just a little bit more Federation-type capabilities going forward when you're going to the cloud. That's the kind of stuff I can use. You've got different regions within the cloud, and just from that, we that kind of support.

To implement deployments, you can initially start with yaml files instead of relying solely on the Linux command line interface. This approach could be more comfortable for users working with yaml files or similar interfaces using the AWS Management Console. It increases complexity and limited visibility compared to pure CLI commands.

They should improve application visibility along with code visibility.