Cloud Native Contrail Networking Installation and Life Cycle Management Guide for Rancher RKE2 Published 2023-09-08 Juniper Networks, Inc. 1133 Innovation Way Sunnyvale, California 94089 USA 408-745-2000 change, modify, transfer, or otherwise revise this publication without notice. Cloud Native Contrail Networking Installation and Life Cycle Management Guide for Rancher RKE2 Copyright © 2023 Juniper Networks agree to the terms and conditions of that EULA. ii Table of Contents 1 Introduction Cloud-Native Contrail Networking Overview | 2 Terminology | 4 CN2 Components | 6 Deployment Models | 11 Single

applications anywhere. The PowerFlex family offers key value propositions for traditional and cloud-native production workloads, deployment flexibility, linear scalability, predictable high performance that span compute and storage infrastructure, from BIOS and firmware to nodes, software, and networking. PowerFlex PowerFlex is the software foundation of the PowerFlex platform. It delivers high exact requirements. PowerFlex rack PowerFlex rack is a fully engineered system, with integrated networking that enables the customers to simplify deployments and accelerate time to value. PowerFlex

late starter. KubeSphere is designed to integrate open-source projects and components in the cloud-native ecosystem into a unified container platform product, ensuring consistent user experience in all Red Hat's commercial software solutions or large enterprises that have very high demands for cloud-native security. OpenShift Functional Architecture 1.3.3 Rancher 15 Rancher products are very lightweight Kubernetes and cloud-native ecological projects. Since its products bring a high learning curve, Rancher is suitable for Kubernetes cluster O&M personnel who have a basic understanding of cloud-native technology

CAGR On-Prem/Other +$1052.7M, 17% CAGR Driver: Shift to Cloud-Native Apps Enterprises have been trained by the hyperscalers to adopt cloud-native approaches for nearly every use case Inhibitor: Legacy increasingly difficult for remaining apps Inhibitor: Time and Effort to re-platform The evolution to cloud-native may require customers to completely re- invent themselves Inhibitor: Scarcity of expertise While

Containers are great……..but Containers are great……..but How about managing many? How do we address: Networking, Security, Scheduling, Automation, etc? 6 Why Kubernetes ? Common compute platform across any Health Checks/HA ✔ Load Balancing ✔ Overlay Networking ✔ Network Security Policies ✔ Backup and Recovery ✔ Autoscaling ✔ Service Discovery ✔ Networking ✔ RBAC & Access Control DEV DATA CENTER CLOUD Health Checks/HA ✔ Load Balancing ✔ Overlay Networking ✔ Network Security Policies ✔ Backup and Recovery ✔ Autoscaling ✔ Service Discovery ✔ Networking ✔ RBAC & Access Control ✔ Common API & Packaging

microservices architecture where you must dynamically manage service endpoints. While Docker allows networking at the host level only (and Docker Swarm works across hosts), Kubernetes makes network management infrastructure and containers supporting their applications. Rancher provides built-in authentication, networking, storage, and load-balancing capabilities as well. 2.2 Native Kubernetes Support in Rancher several features that make it easy to manage the cluster: • Rancher simplifies Kubernetes networking by providing Rancher DNS as a drop-in replacement for SkyDNS. The Kubernetes cluster can then

and do not appear to support PodSecurityPolicies. TKGI uses Antrea (default) or Flannel for networking. Antrea has its own advanced network policy extensions but also supports Kubernetes Network Policies that it is a beta feature exclusively for vSphere with Flannel network plugin and using NSX-T for networking. 3.3.7.4 Anthos GKE (GCP) and GKE on-prem (VMware) support Windows container workloads, but

Hardening Guide v2.3.5 5 This NetworkPolicy is not recommended for production use --- apiVersion: networking.k8s.io/v1 kind: NetworkPolicy metadata: name: default-allow-all spec: podSelector: {}

the Kubernetes site. This NetworkPolicy is not recommended for production use --- apiVersion: networking.k8s.io/v1 kind: NetworkPolicy metadata: name: default-allow-all spec: podSelector: {}