the installation of SAP Data Intelligence 3.3 consists of the following steps: Installing VMware virtual machines in the vsphere cluster as dedicated nodes for the RKE 2 cluster Creating the configuration this document. Create the virtual machines for the RKE 2 cluster with SUSE Linux Enterprise Server 15 SP4 as operating system in the vSphere environment. Make sure these virtual machines are sized according above in this guide. Make sure that uuid creation for disks is enabled in the settings for the virtual machines. 7 SAP Data Intelligence 3 on Rancher Kubernetes Engine 2 using VMware vSAN and vSphere

paper also explains how to protect the above Kubernetes workloads with Dell EMC PowerProtect Data Manager. Dell Technologies Solutions PowerFlex Engineering Validated Copyright ....................... 26 Rancher Kubernetes Cluster Data Protection using PowerProtect Data Manager ................. 29 Conclusion............................................................... Dell EMC PowerProtect Data Manager enables users to protect, manage, and recover data in on-premises, virtualized, or cloud deployments. The PowerProtect Data Manager platform provides centralized

CN2 is a networking platform that provides dynamic end-to-end virtual networking and security for cloud-native containerized and virtual machine (VM) workloads, across multi-cluster compute and storage provisioning events such as a new workload being instantiated, network provisioning events such as a new virtual network being created, routing updates from internal and external sources, and unexpected network containerized workloads on the worker nodes in a cluster. Kubernetes control plane node This is the virtual or physical machine that hosts the Kubernetes control plane, formerly known as a master node. Server

load balancing, resource monitoring and isolation, and more. For years, Google has used a cluster manager called Borg to run thousands of jobs, supporting thousands of applications, running on multiple basic concepts and Kubernetes terminology: Cluster A cluster is a set of machines (physical or virtual) on which your applications are managed and run. For Kubernetes, all machines are managed as a cluster set of clusters, depending on the topology used). Node A logical machine unit (physical or virtual), which is part of a larger cluster on which you can run your applications. Pod A co-located

require that users download and install virtual machines and base image templates before performing the cluster upgrade. A cluster upgrade replaces the virtual machines and must be performed on the management hyperconverged infrastructure solution from SUSE. With Rancher and Harvester, operators can manage their virtual machine workloads alongside their container clusters, all within a single platform. 3.1.2.2 3.1.7.4 Anthos Anthos supports deployment within a vSphere environment or on bare metal or virtual machines. Anthos also can manage non GKE or Anthos clusters previously deployed on these infrastructure

Desktop / POS SLE Server SLES for SAP Applications SLES for HPC SLE Micro SLE Extensions SUSE Manager SUSE Linux Enterprise Compliance Security Availability Management The most adaptable Linux operating Infrastructure Software Revenue ($M), 2022-2025 Aaron’s Anecdote In my prior life as a product manager for an MSP I expected to generate a dollar of services and consulting revenue for every ten dollars IDC SUSE – Market Facts Copyright © SUSE 2021 6 Target Market Finance Information Technology Media and Entertainment Healthcare Government / Defense Retail Telecom Manufacturing & Automotive

Node Security Configuration 1.1 Master Node Configuration Files 1.2 API Server 1.3 Controller Manager 1.4 Scheduler 2 Etcd Node Configuration 2 Etcd Node Configuration Files 3 Control Plane Configuration configuration is passed in as arguments at container run time. 1.1.3 Ensure that the controller manager pod specification file permissions are set to 644 or more restrictive (Scored) Result: Not Applicable the controller manager. All configuration is passed in as arguments at container run time. CIS Benchmark Rancher Self-Assessment Guide - v2.4 6 1.1.4 Ensure that the controller manager pod specification

Node Security Configuration 1.1 Master Node Configuration Files 1.2 API Server 1.3 Controller Manager 1.4 Scheduler 2 Etcd Node Configuration 2 Etcd Node Configuration Files 3 Control Plane Configuration configuration is passed in as arguments at container run time. 1.1.3 Ensure that the controller manager pod specification file permissions are set to 644 or more restrictive (Scored) Result: Not Applicable controller manager. All configuration is passed in as arguments at container run time. CIS 1.5 Benchmark - Self-Assessment Guide - Rancher v2.5 6 1.1.4 Ensure that the controller manager pod specification

(Automated) 1.1.3 Ensure that the controller manager pod specification file permissions are set to 644 or more restrictive (Automated) 1.1.4 Ensure that the controller manager pod specification file ownership is (Automated) 1.1.17 Ensure that the controller-manager.conf file permissions are set to 644 or more restrictive (Automated) 1.1.18 Ensure that the controller-manager.conf file ownership is set to root:root (Automated) Ensure that the API Server only makes use of Strong Cryptographic Ciphers (Automated) 1.3 Controller Manager 1.3.1 Ensure that the --terminated-pod-gc-threshold argument is set as appropriate (Automated) 1

Result: Pass 1.3 - Controller Manager 1.3.1 - Ensure that the --terminated-pod-gc-threshold argument is set as appropriate (Scored) Audit docker inspect kube-controller-manager | jq -e '.[0].Args[] | m that the --profiling argument is set to false (Scored) Audit docker inspect kube-controller-manager | jq -e '.[0].Args[] | match("--profiling=false").string' Returned Value: --profiling=false Result: --use-service-account-credentials argument is set to true (Scored) Audit docker inspect kube-controller-manager | jq -e '.[0].Args[] | match("--use-service-account-credentials=true").string' Returned Value: