Rancher 1.6, with Cattle as the orchestrator, is a widely adopted platform among both the open-source and enterprise communities. With the release of Rancher 2.0, we have shifted from a Cattle to Kubernetes-based orchestration platform.

Although more and more companies choose to containerize their applications and to use Kubernetes to orchestrate their containers, they continue to face a common challenge: how to preserve application data even after a container closes. Without the ability to persist data, containers might seem to have limited use in many workloads, especially in stateful applications and database architectures.

One of the most common uses for Kubernetes is to improve development operations, and as part of that, teams need to determine the best way to integrate their CI workflows with Kubernetes. In our August Rancher Meetup, we'll dive into how to build a CI/CD workflow with Rancher 2.0 and Kubernetes. We'll look at best practices for building pipelines with containers, and some of the tools that make it easier.

Since we released Rancher 2.0 last month, we've fielded hundreds of questions about different networking choices on our Rancher Slack Channel and Forums. From overlay networking and SSL to ingress controllers and network security policies, we've seen many users get hung up on Kubernetes networking challenges.

With the latest release of RancherVM, we've added the ability to schedule virtual machines (guests) to specific Kubernetes Nodes (hosts).

Rancher 2.0 was released to general availability this month, and one of the key use cases we developed this platform for was to help organizations build a Container-as-a-Service platform using Kubernetes. In our May online meetup, we dove into the reality of running an enterprise container platform built on Rancher 2.0.

Need to set up and run Kubernetes on different cloud providers, import existing clusters, monitor and check the health of your clusters and deploy your applications in production? This training will introduce you to the steps and concepts needed to do all those tasks with Kubernetes and Rancher 2.0.

We are excited to announce a port of RancherVM to Kubernetes. We've added resource scheduling, a browser-based VNC client, IP address discovery, key-based authentication, and an updated user interface. Learn how RancherVM works: design, usage, scheduling, persistence, and UI.