While developing K3s to run at the edge we had to change our assumptions about how to manage these clusters at scale. A key assumption in a data center is that you have stable network connectivity, but this may not be true at the edge. You may have unreliable cellular service or limited time during the day in which you can connect. In these environments, operations such as upgrading Kubernetes or patching an operating system require a different paradigm.

Deep Datta from the JFrog Community Team shares his learnings about Go 1.13 introducing important security features to Go Modules including a checksumdb. He explains how this works and provides information on other tools in GoCenter that keep modules secure include vulnerability scanning and Jfrog Xray.

As DevOps teams deploy Kubernetes in production using Rancher, enterprises must focus on the runtime security and compliance requirements of their cloud-native platforms. Starting with Rancher 2.2, we published self-assessment and hardening guides to outline provisioning a cluster to comply with the CIS Kubernetes benchmark. Identifying gaps and pain points in the process, Rancher engineering added additional features to both Rancher and RKE to simplify the process.

As organizations adopt Kubernetes as the de facto standard for container orchestration, operational challenges remain, particularly as enterprises look beyond their hybrid cloud environments to the Edge.

Learn how to provide consistent Kubernetes cluster operations and bring cloud-like operations on-premises using Rancher. With enhanced vSphere support and self healing node pools, Rancher 2.3 takes the burden of automating infrastructure recovery from cluster admins.

In this presentation, we will talk about the concepts around micro-segmentation, but focusing on the visibility that this approach can bring you in your cluster. Who’s talking to whom, and what are they saying? Should that be allowed or not?

Kubernetes enables a common compute platform across any infrastructure and a consistent set of infrastructure capabilities including improved reliability, enhanced security and increased operational efficiencies. But as organizations adopt Kubernetes, clusters are often deployed with limited access to shared tooling and services, inconsistent security policies and no centralized cluster operations.

Infrastructure-as-Code, a DevOps best practice, is a workflow that involves managing and configuring your environments through source control. This allows teams to move faster and with fewer errors when making changes to production environments. If a mistake does occur, your environment and apps can quickly be reverted back to a previous state. Save time, increase productivity, and reduce the cost of inevitable human error.

In our August Online Meetup, we look at the new Cluster Template feature coming in Rancher 2.3!

We are excited to announce support for Istio with Rancher 2.3 in Preview mode.