Copyright © SUSE 2021 SUSE Rancher MSP Use Cases & Enablement APRIL 2022 Managed Services Providers Copyright © SUSE 2021 Agenda Acquired Rancher in 2020 1. Company Snapshot • Powering Innovation Benefits of SUSE Rancher for MSPs • Program Benefits for MSPs • Success Stories 2. SUSE Rancher Use Cases • SUSE Rancher Service Models • SUSE Rancher Solution Stacks • Other Service Examples 3. Enterprises have been trained by the hyperscalers to adopt cloud-native approaches for nearly every use case Inhibitor: Legacy App Compatibility Low hanging fruit continue to be picked off, meaning transformations

..............................................................................48 4.5.1 Ingress Use cases ............................................................................................ and selectors are inherently two sides of the same coin. You can use labels to classify resources and use selectors to find them and use them for certain actions. Replication Controller Replication enable certain number of pods for scaling, or ensure that at least one pod. It is a best practice to use replication controllers to define pod lifecycles, rather than to create pods directly. Replica Sets

specifically disclaims implied warranties of merchantability or fitness for a particular purpose. Use, copying, and distribution of any software described in this publication requires an applicable software isolated applications. Customers who want to boost their productivity and reduce the time to value, can use containers with the departments that are focused on software development. Kubernetes orchestration to deploy a Kubernetes cluster using SUSE Rancher Kubernetes Engine on a PowerFlex cluster and the use of the PowerFlex CSI 1.4 driver to provision persistent storage for Kubernetes managing containerized

dedicated nodes for the RKE 2 cluster Creating the configuration of the vsphere CPI/CSI drivers for the use with RKE 2 Installing RKE 2 Kubernetes cluster on the dedicated nodes Deploying SAP Data Intelligence SUSE Linux Enterprise Server 15 SP3. Only the AMD64/Intel 64 architecture is applicable for our use case. 2.1.1 Hardware Sizing Correct hardware sizing is very important for setting up SAP Data Intelligence Production systems Minimal hardware requirements for an SAP Data Intelligence 3 deployment for production use: At least seven nodes are needed for the Kubernetes cluster. Minimum sizing of the nodes needs to

Deterministic Random Bit Generators 6/24/2015 [SP 800-131A r2] NIST SP 800-131A Rev. 2, Transitioning the Use of Cryptographic Algorithms and Key Lengths 3/21/2019 [SP 800-133 r2] NIST SP 800-133 Rev. 2 Electromagnetic Interference (EMI) and Electromagnetic Compatibility (EMC) requirements for business use as defined by 47 Code of Federal Regulations, Part 15, Subpart B. FIPS 140-2 Security Policy The module is a software library providing a C-language application program interface (API) for use by other processes that require cryptographic functionality. All operations of the module occur via

is the subject of this technical documentation consists of (or is intended for use with) Juniper Networks software. Use of such software is subject to the terms and conditions of the End User License distributions. • Manage CN2 using familiar, industry-standard tools and practices. • Optionally, use the CN2 Web UI to configure and monitor your network. • Leverage the skill set of your existing DevOps up and running. • Combine with Juniper Networks fabric devices and fabric management solutions or use your own fabric or third-party cloud networks. Terminology Table 1: Terminology Term Meaning Kubernetes

flagship product, Rancher. Rancher remains available as an open source project that anyone can use, and as the commercially supported SUSE Rancher. With the additional resources and extended leadership Platforms Copyright © SUSE 2022 5 2 Capabilities Summary 2.1 Overview In this analysis, we use “Harvey balls” to illustrate how each vendor compares to the others by category: • The full ball GUI or via command-line directives that use a YAML configuration file. Clusters can run on vSphere, Amazon, Microsoft Azure or GCP nodes if operators choose to use the bring your own host feature (BYOH)

encryption providers are appropriately configured (Automated) 1.2.35 Ensure that the API Server only makes use of Strong Cryptographic Ciphers (Automated) 1.3 Controller Manager 1.3.1 Ensure that the --termi (Automated) 1.3.2 Ensure that the --profiling argument is set to false (Automated) 1.3.3 Ensure that the --use-service-account-credentials argument is set to true (Automated) 1.3.4 Ensure that the --service-ac RotateKubeletServerCertificate argument is set to true (Automated) 4.2.13 Ensure that the Kubelet only makes use of Strong Cryptographic Ciphers (Automated) 5.1 RBAC and Service Accounts 5.1.1 Ensure that the cluster-admin

1” profile and exhibit one or more of the following characteristics: are intended for use in environments or use cases where security is paramount act as a defense in depth measure may negatively impact restrictive pod security policy (PSP) as the default and create role bindings for system level services to use the less restrictive default PSP. Rationale To address the following controls, a restrictive default resourceNames: - default-psp resources: - podsecuritypolicies verbs: - use --- apiVersion: rbac.authorization.k8s.io/v1 kind: RoleBinding metadata: name: de

Kubernetes site. 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 default-psp resources: - podsecuritypolicies verbs: Hardening Guide v2.3.5 8 - use --- apiVersion: rbac.authorization.k8s.io/v1 kind: RoleBinding metadata: name: de resourceNames: - default-psp resources: - podsecuritypolicies verbs: - use Hardening Guide v2.3.5 9 --- apiVersion: rbac.authorization.k8s.io/v1 kind: RoleBinding