Continental Innovates with Rancher and Kubernetes
We created the Fleet Project to provide centralized GitOps-style management of a large number of Kubernetes clusters. A key design goal of Fleet is to be able to manage 1 million geographically distributed clusters. In this blog, I will cover Fleet’s architecture, the method we used to test scale and our findings.
As Kubernetes continues to establish itself as the industry standard for container orchestration, finding effective ways to use a declarative model for your applications and tools is critical to success. In this blog, we'll set up a K3s Kubernetes cluster in AWS, then implement secure GitOps using Argo CD and Vault.
The growing popularity of Kubernetes has led to challenges in managing complexity in an environment that is conducive to cluster sprawl. Rancher 2.5 simplifies deployment and management with Rancher Continuous Delivery, a new capability that adopts a GitOps approach toward streamlining the process across any infrastructure—private, public, hybrid or multi-cloud environments—by using a Git repository to store and manage application and configuration information automatically, ensuring consistency in deployments while taking a lot of the load off of the customer.
Rancher 2.5 delivers major new capabilities that simplify and enhance the Kubernetes user experience, whether the user is starting with a single, local cluster or managing many clusters across a hybrid cloud infrastructure. Other new capabilities include: GitOps at scale for edge clusters, full lifecycle management for Amazon EKS clusters and security hardening for public sector applications.
See how to scale application delivery on Kubernetes clusters provisioned with Rancher with Microsoft Azure Arc enabled Kubernetes GitOps policy enablement.
GitOps provides a single source of truth for development and operations of applications in your Kubernetes platform and works to ensure application stability and availability.