If you are deploying Kubernetes on-premises in your datacenter, you won’t want to miss this talk and demo. The first thing you’re thinking about might not be networking, but without some knowledge of the networking decisions you’ll need to make, and what the right option is given your environment, you’re likely to get stuck or make the wrong assumptions that may limit your ability to scale or integrate with the rest of the datacenter network.

Rancher is a great way to deploy and manage Kubernetes clusters across a broad range of environments, abstracting away many of the differences between the environments, and using Canal for run-anywhere networking. But what if you want to up your networking game to squeeze the most out of your clusters? In this training session you’ll learn about the various networking options available to you in Rancher, and considerations to take into account in order to select the best option for your environment.

Services in Kubernetes are a commonly misunderstood part of the connectivity stack.

When you have different teams interacting with a Kubernetes cluster you need to think about the security, privacy, and observability challenges associated with multi-tenancy: How to provide each team with access to the specific resources they need, in a way that allows the team to be agile, without risking impacting other teams? In this session, we’ll explore the Kubernetes multi tenancy concepts and design patterns needed for successful enablement of multi-tenancy within your Kubernetes clusters using key capabilities of Calico Enterprise.

Calico is the only cross-platform CNI and networking and network security policy engine available today. It currently powers more than 150,000 known clusters across millions of nodes worldwide. Calico is also unique in supporting multiple dataplanes: Standard Linux, eBPF, and Windows HNS. Many organizations have .NET and Windows workloads that they have or eventually will modernize and deploy to Kubernetes. However, this may be uncharted territory for teams that are using Windows. This session is intended to inform and ease your adoption of Kubernetes on the Windows platform.

A majority of existing workloads are non-Kubernetes, and for the platform teams involved, this creates challenges because the cluster will need to be securely connected to those resources. Calico Enterprise includes several features that enable fine-grained access controls between your microservices and databases, cloud services, APIs, and other applications that may be protected behind a firewall. There are different approaches to managing Kubernetes egress access, depending on your needs and where you want the control point to be

If you are deploying Kubernetes on-premises in your datacenter, this is a talk and demo you won’t want to miss. Networking and security might not be the first things that come to mind, but without some understanding of the networking and security decisions you’ll need to make, and the right options for your environment, you’re likely to get stuck or make the wrong assumptions. These may limit your ability to scale or integrate with the rest of the datacenter network.

Troubleshooting connectivity problems in distributed networks is difficult enough, but doing it in a Kubernetes environment is even more challenging. However, there are tools in Calico that can ease the burden and speed problem resolution. Join this session that discusses the components that makeup Calico and best practices for troubleshooting connectivity problems in your Kubernetes cluster when things go wrong.

Rancher is a great way to deploy and manage Kubernetes clusters across a broad range of environments, abstracting away many of the differences between the environments, and using Canal for run-anywhere networking. But what if you want to up your networking game to squeeze the most out of your clusters? In this training session you’ll learn about the various networking options available to you in Rancher, and considerations to take into account in order to select the best option for your environment.

Managing networking, observability and security in multiple Kubernetes clusters can quickly become a major challenge. Lack of a centralized, unified multi-cluster approach results in dozens of clusters that are deployed and managed independently throughout an organization, with very little uniformity in the way they are secured. This adds complexity for DevOps teams, who must adapt to different cluster environments.