Continental Innovates with Rancher and Kubernetes
Measuring costs in Kubernetes environments is complex. Applications and their resource needs are often dynamic. Teams share resources without transparent prices attached to workloads, while organizations are often running resources on disparate machine types and even multiple cloud providers. We look at best practices and different approaches for implementing cost monitoring in your organization, including Kubecost.
Many companies still struggle to find a way to abstract the complexity of Kubernetes away from developers. This often results in custom-tailored platforms that limit the potential of Kubernetes and add a maintainence burden. Combining DevSpace, Rancher and loft gives developers direct access to Kubernetes while making the interaction with it as easy as possible by running just a single command.
Inventx’ financial and insurance customers are adopting microservices and moving to cloud-native through a full-stack DevOps platform based on Rancher.
Learn about the integration of Citrix ADC as an Istio ingress gateway and sidecar proxy in Istio service mesh deployed on Rancher.
Learn about the components of a disaster recovery scenario and how to implement them safely in a Kubernetes environment.
Learn how to deploy open source Ingress controller Ambassador on K3s.
Deploy a PHP application on Kubernetes with custom OPcache and PHP-FPM configurations to improve performance. You’ll use Rancher to deploy a PHP application using custom environment variables to dynamically configure OPcache and PHP-FPM.
Manage a Rancher cluster deployment using GitLab for CI/CD, Terraform for Infrastructure as Code and the Rancher2 provider.
See how to scale application delivery on Kubernetes clusters provisioned with Rancher with Microsoft Azure Arc enabled Kubernetes GitOps policy enablement.
Citrix Ingress Controller is an emerging enterprise-grade ingress controller for load balancing microservices in the Kubernetes environment. In this article, we will discuss different deployment modes for Citrix Ingress Controller and deploy it via the Rancher catalog.
Optoro, the world’s leading returns optimization platform, has pioneered a reverse logistics model to keep returned goods out of landfills. With Rancher and Kubernetes, Optoro is driving greater scale, efficiency and sustainability.
Use Rancher to deploy Kubernetes clusters on Microsoft Azure, with Terraform or from the GUI
DIMOCO is an international mobile payments innovator. See how why Rancher is central to their infrastructure transformation around Kubernetes and how they have cut development time by 80 percent.
A common challenge in deploying Kubernetes is gaining the necessary visibility into the cluster environment to effectively monitor and troubleshoot networking and security issues. Discover best practices for better cluster visibility to avoid downtime troubleshooting.
The Folding@home project allows you to donate unused compute resources to support research for COVID-19. Join the fight! We’ve published the app in the Rancher catalog so you can easily donate unused compute resources from your Kubernetes clusters in Rancher.
Fleet is new open source project from the team at Rancher focused on managing fleets of Kubernetes clusters. Ever since Rancher 1.0, Rancher has provided a central control plane for managing multiple clusters. As pioneers of Kubernetes multi-cluster management, we have seen firsthand how users have consistently increased the number of clusters under management. We are already seeing interest from users who want to manage tens of thousands or even millions of clusters in the near future.
Rancher 2.4 includes under-the-hood changes that pave the way to supporting up to 1 million clusters. See what these scale improvements mean for the future of Kubernetes on the edge and in fleet management.
Learn how to deploy a completely cloud-native infrastructure stack that consists of Google Kubernetes Engine, Rancher, Longhorn distributed block storage and a YugabyteDB distributed SQL database.
Kubernetes Pod Security Policies are critical for Kubernetes security. See how to harden your Kubernetes security posture using a Pod Security Policy in your Rancher environment and tools from Sysdig.
Kubernetes Pod Security Policies are critical for Kubernetes security. See how to harden your Kubernetes security posture using a Pod Security Policy in your Rancher environment.
Security is one of the most talked-about topics for Kubernetes users. Google “Kubernetes security” and you’ll find a huge number of articles, blogs and more. The reason is simple: you need to align your container and Kubernetes security with your organization’s existing security profile.
Kubernetes has some strong security best practices for your cluster—authentication and authorization, encryption in secrets and objects in the etcd database—to name a few. However, you need to be aware of other risks, such as privilege escalation and secrets obtained.
The k3s project was started by Darren Shepherd, Chief Architect at Rancher 7 months ago and has already become one of the most popular Kubernetes options on the CNCF Landscape by number of GitHub stars.
To put this into context, k3s is more popular than OpenShift by IBM/Red Hat and only Rancher Kubernetes itself is more popular than k3s. Now stars are indicative of interest and popularity only and that should be noted.
Support for relational databases is a growing focus for Kubernetes users, and the release of Windows Server 2019 is expanding options for .NET applications and SQL Server. SQL Server workloads, however, often rely on Active Directory and Windows Auth, and storage arrays, which will not be supported by SQL Server containers on Windows Server 2019. Fortunately, a new Rancher Labs partner, Windocks, offers new options for SQL Server on Kubernetes and Rancher.
K3s and Traefik partner to speed up cloud native applications deployment.
Today we announced releases v2.1.6 and v2.0.11 to address two security vulnerabilities recently discovered in Rancher. The first vulnerability allows users in the Default project of a cluster to escalate privileges to that of a cluster admin through a service account. The second vulnerability allows members to have continued access to create, update, read, and delete namespaces in a project after they have been removed from it. You can view the official CVEs here CVE-2018-20321 and here CVE-2019-6287.