Installing SAP Data Intelligence 3.3 11 6 Maintenance tasks 17 7 Legal notice 20 8 GNU Free Documentation License 21 3 SAP Data Intelligence 3 on Rancher Kubernetes Engine 2 using VMware vSAN and vSphere generic SAP Data Intelligence 3 deployment: At least 7 nodes are needed for the Kubernetes cluster. Minimum sizing of the nodes needs to be as shown below: Server Role Count RAM CPU Disk space Management 3 deployment for production use: At least seven nodes are needed for the Kubernetes cluster. Minimum sizing of the nodes needs to be as shown below: Server Role Count RAM CPU Disk space Management

Kubernetes distribution from the cloud to core and at the edge. Each distribution requires the bare minimum of host configuration, usually no more than a supported version of Docker. For edge deployments upgrade replaces the virtual machines and must be performed on the management cluster first. The documentation lists multiple pages of prerequisites and post-upgrade re-registration tasks, which may make the possibility to run Single Node OpenShift (SNO) clusters. However, the SNO needs are high: the minimum hardware to run SNO is 8 vCPU cores, 32 GB of RAM and 120GB of storage, making it less than ideal

feedback on the solution and the solution documentation. Contact the Dell Technologies Solutions team by email or provide your comments by completing our documentation survey. Author: Sanjay Puttaswamy Vinod Kumaresan. Contributors from SUSE Team: Gerson Guevara Note: For links to additional documentation for this solution, see Dell Technologies Solutions Info Hub for PowerFlex. This white paper consistency and simplicity over time. You can scale the system while linearly scaling performance from a minimum of four nodes to thousands of nodes, on-demand and without any disruption. And with its self-healing

the resource (for example, storing strong keys, etc). 1.3 Kubernetes Functionalities At bare minimum, any container orchestration platform needs the ability to run and schedule containers. But to period of time, and in some cases, cannot be taken down at all. Rolling updates ensure that a minimum number of instances are always available, while instances are taken out of the pool for updates master as separate components so that they can be scaled easily (there are templates and detailed documentation for Kubernetes here). For Logstash and Kibana, we will use the images and templates developed

the --basic-auth-file argument is not set (Automated) Result: pass Remediation: Follow the documentation and configure alternate mechanisms for authentication. Then, edit the API server pod specification the --token-auth-file parameter is not set (Automated) Result: pass Remediation: Follow the documentation and configure alternate mechanisms for authentication. Then, edit the API server pod specification arguments are set as appropriate (Automated) Result: pass Remediation: Follow the Kubernetes documentation and set up the TLS connection between the apiserver and kubelets. Then, edit API server pod specification

random bit generator for creation of the seed for asymmetric key generation. The module requests a minimum number of 128 bits of entropy from its Operational Environment per each call. The output data

that the --basic-auth-file argument is not set (Scored) Result: PASS Remediation: Follow the documentation and configure alternate mechanisms for authentication. Then, edit the API server pod specification that the --token-auth-file parameter is not set (Scored) Result: PASS Remediation: Follow the documentation and configure alternate mechanisms for authentication. Then, edit the API server pod specification arguments are set as appropriate (Scored) Result: PASS Remediation: Follow the Kubernetes documentation and set up the TLS connection between the apiserver and kubelets. Then, edit API server pod specification

that the --basic-auth-file argument is not set (Scored) Result: PASS Remediation: Follow the documentation and configure alternate mechanisms for authentication. Then, edit the API server pod specification that the --token-auth-file parameter is not set (Scored) Result: PASS Remediation: Follow the documentation and configure alternate mechanisms for authentication. Then, edit the API server pod specification arguments are set as appropriate (Scored) Result: PASS Remediation: Follow the Kubernetes documentation and set up the TLS connection between the apiserver and kubelets. Then, edit API server pod specification

END USER LICENSE AGREEMENT The Juniper Networks product that is the subject of this technical documentation consists of (or is intended for use with) Juniper Networks software. Use of such software is supported OSes and kernels (see the CN2 Tested Integrations matrix at https://www.juniper.net/documentation/us/en/software/cn-cloud-native/ cn2-tested-integrations/cn-cloud-native-tested-integrations/c informational purposes. For more information about creating an RKE2 cluster, see the official Rancher documentation: https:// docs.rke2.io/install/quickstart. Before you start, make sure you've brought up the

all traffic in that namespace. Save the following yaml as default-allow-all.yaml. Additional documentation about network policies can be found on the Kubernetes site. Hardening Guide v2.3.5 5 This NetworkPolicy Install documentation is provided with additional details about the configuration items. # If you intend to deploy Kubernetes in an air-gapped environment, # please consult the documentation on how