vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* [14 January 2021](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-relnotesopenshift-jan1421)



* Cluster autoscaler



* [12 January 2021](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-relnotesopenshift-jan1221)



* Ingress resources
* Kubernetes benchmarks
* Removal of data center support



* [6 January 2021](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-relnotesopenshift-jan0621)



* Master versions





* [December 2020](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-relnotesopenshift-dec20)



* [21 December 2020](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-relnotesopenshift-dec2120)



* Gateway firewalls and Calico policies
* Worker node versions



* [18 December 2020](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-relnotesopenshift-dec1820)



* CLI change log
* IBM Cloud Object Storage plug-in



* [17 December 2020](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-relnotesopenshift-dec1720)



* Audit documentation
* Back up and restore



* [15 December 2020](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-relnotesopenshift-dec1520)



* Cluster autoscaler
Upgrade to the newer TLS version, or as a workaround you can change the security level to 0 for OpenSSL, by appending @SECLEVEL=0 to your cipher list in the kube-system/ibm-k8s-controller-config ConfigMap. For example: ssl-ciphers: HIGH:!aNULL:!MD5:!CAMELLIA:!AESCCM:!ECDH+CHACHA20@SECLEVEL=0







 Version 1.5.1 



 1.5.1_5160_iks, released 5 July 2023 



* Resolves [CVE-2023-32731](https://nvd.nist.gov/vuln/detail/CVE-2023-32731)







 1.5.1_5074_iks, released 6 June 2023 



* Updates golang version to 1.20.4.
* [CVE-2023-29491](https://nvd.nist.gov/vuln/detail/CVE-2023-29491)
* [CVE-2023-2650](https://nvd.nist.gov/vuln/detail/CVE-2023-2650)







 1.5.1_4168_iks, released 23 May 2023 



* [CVE-2023-28319](https://nvd.nist.gov/vuln/detail/CVE-2023-28319)
* [CVE-2023-28320](https://nvd.nist.gov/vuln/detail/CVE-2023-28320)
* [CVE-2023-28321](https://nvd.nist.gov/vuln/detail/CVE-2023-28321)
* [CVE-2023-28322](https://nvd.nist.gov/vuln/detail/CVE-2023-28322)







 1.5.1_4113_iks, released 4 May 2023 



* Image update.
* [Change log for patch update 1.0.9_44, released 22 June 2023](https://cloud.ibm.com/docs/containers?topic=containers-ca_changelog10944_ca)



* [Version 1.0.8](https://cloud.ibm.com/docs/containers?topic=containers-ca_changelog0108_ca_addon)



* [Change log for patch update 1.0.8_56, released 6 July 2023](https://cloud.ibm.com/docs/containers?topic=containers-ca_changelog10856_ca)
* [Change log for patch update 1.0.8_1078, released 15 May 2023](https://cloud.ibm.com/docs/containers?topic=containers-ca_changelog1081078_ca)
* [Change log for patch update 1.0.8_1016, released 5 April 2023](https://cloud.ibm.com/docs/containers?topic=containers-ca_changelog1081016_ca)
* [Change log for patch update 1.0.8_987, released 29 March 2023](https://cloud.ibm.com/docs/containers?topic=containers-ca_changelog108987_ca)
* [Change log for patch update 1.0.8_968, released 9 March 2023](https://cloud.ibm.com/docs/containers?topic=containers-ca_changelog108968_ca)



* [Version 1.0.7](https://cloud.ibm.com/docs/containers?topic=containers-ca_changelog0107_ca_addon)



* [Change log for patch update 1.0.7_57, released 6 July 2023](https://cloud.ibm.com/docs/containers?topic=containers-ca_changelog10757_ca)
Maximum HSM Storage Space (Bytes): 2097152
Space In Use (Bytes): 1468005
Free Space Left (Bytes): 629147
Command Result : 0 (Success)

The output states The HSM is NOT in FIPS 140-2 approved operation mode, confirming the device is not running FIPS.
2. Review your policies before enabling FIPS mode with the hsm showpolicies command.

[jdoe1] lunash:>hsm showpolicies

HSM Label: jpmonge
Serial : 534071
Firmware: 6.10.9

[OUTPUT OMITTED]

The following policies are set due to current configuration of this HSM and cannot be altered directly by the user.

Description Value
=========== =====

PIN-based authentication True

The following policies describe the current configuration of this HSM and may be changed by the HSM Administrator.

Changing policies marked "destructive" will zeroize (erase completely) the entire HSM.

Description Value Code Destructive
=========== ===== ==== ===========
Allow masking On 6 Yes
Allow cloning On 7 Yes
Allow non-FIPS algorithms On 12 Yes
SO can reset partition PIN On 15 Yes
Allow network replication On 16 No
Allow Remote Authentication On 20 Yes
Force user PIN change after set/reset Off 21 No
Allow offboard storage On 22 Yes
Allow Acceleration On 29 Yes

Command Result : 0 (Success)

This output shows that policy 12 (Allow non-FIPS algorithms) is set to On, meaning that algorithms non-compliant with FIPS are currently allowed for operations in the HSM.
3. Login as an HSM SO/Administrator using the password you specified during [initialization](https://cloud.ibm.com/docs/citrix-netscaler-vpx?topic=citrix-netscaler-vpx-initialize-ibm-hardware-security-module-hsm-).

[jdoe1] lunash:>hsm login
mount -t nfs -o nfsvers=3 fsf-wdc0403a-fz.service.softlayer.com:/IBM02SEV1414935_66/data01 /mnt

Example for enterprise volumes.

 mount -t nfs -o nfsvers=3 nfshou0201d-fz.service.softlayer.com:/IBM01SEV1414935_2 /mnt

The mount point information can be obtained from the File Storage for Classic Details page in the UI, with an API call - SoftLayer_Network_Storage::getNetworkMountAddress(), or by looking at the ibm_storage_file resource in Terraform.
3. Verify that the mount was successful by using the disk file system command.

 df -h
Filesystem Size Used Avail Use% Mounted on
/dev/xvda2 25G 1.4G 22G 6% /
/tmpfs 1.9G 0 1.9G 0% /dev/shm
/dev/xvda1 97M 51M 42M 55%
4. Go to the mount point, and read/write files.

 touch /mnt/test
 ls -la /mnt
total 12
drwxr-xr-x 2 nobody nobody 4096 Sep 8 15:52 .
dr-xr-xr-x. 22 root root 4096 Sep 8 14:30 ..
-rw-r--r-- 1 nobody nobody 0 Sep 8 15:52 test

The files that are created by root have ownership of nobody:nobody. To display ownership correctly, idmapd.conf needs to be updated with the correct domain settings. For more information, see the [Implementing no_root_squash for NFS (optional)](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-mountingLinuxnorootsquash) section.
5. Mount the remote share on start.
ibmcloud ce sub cron update -n cron-sub -d cron-app --data '{"mydata":"hello world again"}' -s '0 0 * * '

Run the ibmcloud ce sub cron get -n cron-sub command to find information about your subscription.

Example output

In this output, you can see that the schedule and data are updated.

Getting cron event subscription 'cron-sub'...
OK

Name: cron-sub
ID: abcdefgh-abcd-abcd-abcd-1a2b3c4d5e6f
Project Name: myproject
Project ID: 01234567-abcd-abcd-abcd-abcdabcd1111
Age: 5m7s
Created: 2021-03-14T13:21:13-05:00

Destination: App:cron-app
Schedule: 0 0 * * 
Data: {"mydata":"hello world again"}
Ready: true

Events:
Type Reason Age Source Messages
Normal FinalizerUpdate 65s pingsource-controller Updated "cron-sub" finalizers





 Step 6: Clean up for cron subscription tutorial 

Ready to delete your cron subscription and your app? You can use the [ibmcloud ce app delete](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-application-delete) and the [ibmcloud ce sub cron delete](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-subscription-cron-delete) commands.

To remove your subscription,

ibmcloud ce sub cron delete --name cron-sub

To remove your application,

ibmcloud ce app delete --name cron-app

Looking for more code examples? Check out the [Samples for IBM Cloud Code Engine GitHub repo](https://github.com/IBM/CodeEngine).
HSM Admin login attempts left: 3 before HSM zeroization!
RPV Initialized: No
Audit Role Initialized: No
Remote Login Initialized: No
Manually Zeroized: No
[OUTPUT OMITTED]
Show more

The output should show Logged In in the HSM Admin login status. Otherwise, most operations and commands listed in the following sections will fail because they require administrator access.
3. List any existing partitions:

[jpmongehsm2] lunash:>partition list
Storage (bytes)
----------------------------
Partition Name Objects 	Total Used Free
===================================
534071016 partition1 0 207559 0 207559 	534071020 partition2 3 207559 3464 204095
534071027 partition3 0 207559 0 207559
534071021 partition4 2 207559 1652 205907
534071030 partition5 10 207559 9400 198159

Command Result : 0 (Success)

This output shows five existing partitions.
4. Create a new partition:

The password defined in this step is used later to associate and create objects in the Citrix VPX HSM client process. Keep track of this password for future reference. Also, be sure to use the cloning domain defined during the initialization process.

[jpmongehsm2] lunash:>partition create -partition partition6

On completion, you will have this number of partitions: 6

-label: Not provided; using name for label.

Please enter a password for the partition:
> 

Please re-enter password to confirm:
> 

Please enter a cloning domain to use when creating this partition:
> 

Please re-enter cloning domain to confirm:
>
For more information, see the [iscsiadm(8) man page](https://linux.die.net/man/8/iscsiadm). In this step, discover the device by using the Target IP address that was obtained from the IBM Cloud® console.



1. Run the discovery against the iSCSI array.

iscsiadm -m discovery -t sendtargets -p <ip-value-from-IBM-Cloud-console>

If the IP information and access details are displayed, then the discovery is successful.
2. Configure automatic login.

sudo iscsiadm -m node --op=update -n node.conn[0].startup -v automatic
sudo iscsiadm -m node --op=update -n node.startup -v automatic
3. Enable the necessary services.

systemctl enable open-iscsi
systemctl enable iscsid
4. Restart the iscsid service.

systemctl restart iscsid.service
5. Log in to the iSCSI array.

sudo iscsiadm -m node --loginall=automatic







 Step 6: Verifying configuration 



1. Validate that the iSCSI session is established.

iscsiadm -m session -o show
2. Validate that multiple paths exist.

multipath -ll

This command reports the paths. If it is configured correctly, then each volume has a single group, with a number of paths equal to the number of iSCSI sessions. It's possible to attach Block Storage for Classic with only a single path, but it is important that connections are established on both paths to ensure no disruption of service.

$ sudo multipath -ll
mpathb (360014051f65c6cb11b74541b703ce1d4) dm-1 LIO-ORG,TCMU device
size=1.0G features='0' hwhandler='0' wp=rw
|-+- policy='service-time 0' prio=1 status=active
Understanding the vSRX default configuration 

IBM Cloud® Juniper vSRX devices come with following default configuration:



* SSH and Ping are permitted on both vSRX public and private gateway IP addresses
* Juniper Web Management (J-Web) UI access is permitted on HTTPS port 8443 for both public and private gateway IP addresses
* An address-set SERVICE is predefined for IBM service networks
* Two security zones: SL-PRIVATE and SL-PUBLIC are predefined.
* Access from the zone SL-PRIVATE to all services is provided by IBM and address-set SERVICE is permitted
* All other network accesses are denied



Two redundancy groups are configured. The following table illustrates these redundancy groups:



Table 1. Redundancy groups

 Redundancy group Redundancy group function 

 redundancy-group 0 Redundancy group for control plane 
 redundancy-group 1 Redundancy group for data plane 



Priority in the redundancy group decides which vSRX node is active. By default, node 0 is active for both control plane and data plane.



 Default Configuration of a sample 1G Standalone SR-IOV Public and Private vSRX Gateway 

The following code samples are examples from the latest code release.

 Last commit: 2020-04-28 00:32:27 UTC by root
version 18.4R1-S1.3;
system {
login {
class security {
permissions [ security-control view-configuration ];
}
user admin {
uid 2000;
class super-user;
authentication {
encrypted-password "$6$5gPuIk9u$JPzyjh5zVz0tf4P3.POWv4UWGDfowbzirGmnpiBUW0tDWLf1ZfvP.YwN88Mc8.cyOIvgDMrksbCYsmZxf4f3p."; SECRET-DATA
}
}
}
root-authentication {
For more information about Ubuntu specifics, see [iSCSI Initiator Configuration](https://help.ubuntu.com/lts/serverguide/iscsi-initiator.html) and [DM-Multipath](https://help.ubuntu.com/lts/serverguide/multipath-setting-up-dm-multipath.html).



1. Install the iSCSI and multipath utilities to your host.



* RHEL and CentOS



yum install iscsi-initiator-utils device-mapper-multipath



* Ubuntu and Debian



sudo apt-get update
sudo apt-get install multipath-tools
2. Create or edit your multipath configuration file if it is needed.



* RHEL 6 and CENTOS 6



* Edit /etc/multipath.conf with the following minimum configuration.



defaults {
user_friendly_names no
max_fds max
flush_on_last_del yes
queue_without_daemon no
dev_loss_tmo infinity
fast_io_fail_tmo 5
}
 All data in the following section must be specific to your system.
blacklist {
wwid "SAdaptec"
devnode "^hd[a-z]"
devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]"
devnode "^cciss."
}
devices {
device {
vendor "NETAPP"
product "LUN"
path_grouping_policy group_by_prio
features "3 queue_if_no_path pg_init_retries 50"
prio "alua"
path_checker tur
failback immediate
path_selector "round-robin 0"
hardware_handler "1 alua"
rr_weight uniform
rr_min_io 128
}
}
Show more
0 0 DROP all -- eth1 * 192.0.2.0/24 0.0.0.0/0 / DDOS: Drop private source IPs /
0 0 DROP all -- eth1 * 0.0.0.0/8 0.0.0.0/0 / DDOS: Drop private source IPs /
0 0 DROP all -- eth1 * 240.0.0.0/5 0.0.0.0/0 / DDOS: Drop private source IPs /
0 0 DROP all -- eth1 * 10.0.0.0/8 0.0.0.0/0 / DDOS: Drop private source IPs /
0 0 DROP all -- eth1 * 192.168.0.0/16 0.0.0.0/0 / DDOS: Drop private source IPs /
0 0 ACCEPT all -- vethlocal * 127.0.0.0/8 0.0.0.0/0 / DDOS: Accept local LB traffic /
0 0 DROP all -- !lo * 127.0.0.0/8 0.0.0.0/0 / DDOS: Drop private source IPs /

 How to fix it 

To resolve this issue, [create a private load balancer](https://cloud.ibm.com/docs/containers?topic=containers-cs_network_planning) to allow this traffic with the private source IP addresses. If that does not resolve the problem, or for some reason, you can't create a private load balancer, then create a daemonset that removes the rules that are causing the issue.
-hls_time 6 Attempt to target each output video fragment length to 6 seconds. <br>Accumulates frames for at least 6 seconds of video, and then <br>stops to break off a video fragment when it encounters the next keyframe. 
 -hls_playlist_type vod Prepares the output .m3u8 playlist file for Video on Demand (VOD). 
 test-video.m3u8 Name the output playlist/manifest file to test-video.m3u8. <br>As a result, test-video0.ts, test-video1.ts, test-video2.ts, ..., and similar, <br>will be the video fragment's names by default. 



Note, for the - options, unless a stream is specified, the "best" one for its category is chosen.

Such as:



* -c:a chooses the audio stream with the most channels.
* -c:v chooses the video stream with the highest resolution.
* -c:a:0 chooses audio stream 0.
* -c:v:0 chooses video stream 0.



In this example, only one audio stream and one video stream make up the example test-video.mp4. And so, the difference would not be a concern moving forward.

Afterward, you can expect to see a number of .ts files. Additionally, you can expect to see a .m3u8 file that looks something like the following:

cat test-video.m3u8
EXTM3U
EXT-X-VERSION:3
EXT-X-TARGETDURATION:7
EXT-X-MEDIA-SEQUENCE:0
EXT-X-PLAYLIST-TYPE:VOD
EXTINF:6.039000,
test-video0.ts
EXTINF:6.039000,
test-video1.ts
EXTINF:6.039000,
test-video2.ts
EXTINF:6.039000,
test-video3.ts
EXTINF:6.039000,
test-video4.ts
EXTINF:6.039000,
* [Change log for worker node fix pack 4.4.33_1533_openshift, released 15 February 2021](https://cloud.ibm.com/docs/openshift?topic=openshift-changelog_archive4433_1533)
* [Change log for worker node fix pack 4.4.31_1532_openshift, released 1 February 2021](https://cloud.ibm.com/docs/openshift?topic=openshift-changelog_archive4431_1532)
* [Change log for master fix pack 4.4.31_1531_openshift, released 19 January 2021](https://cloud.ibm.com/docs/openshift?topic=openshift-changelog_archive4431_1531)
* [Change log for worker node fix pack 4.4.31_1530_openshift, released 18 January 2021](https://cloud.ibm.com/docs/openshift?topic=openshift-changelog_archive4431_1530)
* [Change log for master fix pack 4.4.31_1529_openshift, released 6 January 2021](https://cloud.ibm.com/docs/openshift?topic=openshift-changelog_archive4431_1529)
* [Change log for worker node fix pack 4.4.31_1528_openshift, released 21 December 2020](https://cloud.ibm.com/docs/openshift?topic=openshift-changelog_archive4431_1528)
* [Change log for master fix pack 4.4.29_1527_openshift, released 14 December 2020](https://cloud.ibm.com/docs/openshift?topic=openshift-changelog_archive4429_1527)
* [Change log for worker node fix pack 4.4.31_1526_openshift, released 7 December 2020](https://cloud.ibm.com/docs/openshift?topic=openshift-changelog_archive4431_1526)
When you run this command to redeploy the ALB to an edge worker node, the ALB also updates to the latest version. If you do not want to update the ALB to the latest version, include the --version option and specify the version listed under Build in the output from the previous step.

ibmcloud ks ingress alb update -c <cluster_name_or_ID> --alb <ALB_ID> [--version <build_version>]

Example output

Updating ALB pods for private-crc81nk5l10gfhdql4i3qg-alb1 to version '1.1.1_1949_iks' in cluster c81nk5l10gfhdql4i3qg...
OK
9. Verify that ALB pods are scheduled onto edge nodes and are not scheduled onto compute nodes.



1. Confirm that all ALB pods are deployed to edge nodes. Each public and private ALB that is enabled in your cluster has two pods.

kubectl describe nodes -l dedicated=edge | grep alb

Example output

kube-system private-crdf253b6025d64944ab99ed63bb4567b6-alb1-d5dd478db-27pv4 0 (0%) 0 (0%) 0 (0%) 0 (0%)
kube-system private-crdf253b6025d64944ab99ed63bb4567b6-alb1-d5dd478db-7p9q6 0 (0%) 0 (0%) 0 (0%) 0 (0%)
kube-system public-crdf253b6025d64944ab99ed63bb4567b6-alb1-5ff8cdff89-s77z6 0 (0%) 0 (0%) 0 (0%) 0 (0%)
Formula to calculate the available memory 

AvailableMemory = [HostMemory - HostOverheadMemory - HostVsanOverheadMemory - (HostVsanOverheadMemoryDiskPercentage * HostVsanCapacityDiskSize)] * (HostCount - vSphereHAHostTolerance) - MgmtOverheadMemory

The following table lists the variables that are used in the previous formula.



Table 4. Description of variables in formula 2

 Variable Description Unit vSAN example NFS example 

 AvailableMemory The number of GB of memory available for workloads and services in the environment GB 693 860 
 HostCount The number of hosts in the default cluster Hosts 6 6 
 HostMemory The number of raw GB of memory available in each host in the default cluster GB 192 192 
 HostVsanCapacityDiskSize The number of GB of a capacity of each vSAN capacity SSD disk on this host GB 960, 1,946, or 3,891 0 
 HostOverheadMemory The number of GB of memory that is reserved by the ESXi server as overhead GB 4.6 4.6 
 MgmtOverheadMemory<br><br>[4] The number of GB of memory reserved by the Cyber Recovery management components (Cyber Recovery, PSC, AD/DNS, Edges) GB 77 77 
 vSphereHAHostTolerance<br><br>[5] The number of hosts to tolerate in the vSphere HA configuration Hosts 1 1 
 HostVsanOverheadMemoryDiskPercentage The number of GB of memory reserved by vSAN management (represented as percentage of one of the capacity vSAN disks) % 2.75% 2.75% 
 HostVsanOverheadMemory The number of GB of memory reserved by vSAN management regardless of disk size GB 7 0 











 Procedure to order services for Cyber Recovery instances 

For Cyber Recovery instances, a recommended service is Caveonix RiskForesight, which manages cyberrisk and compliance risk. You can have many other options, such as Zerto, Entrust CloudControl, and Red Hat OpenShift for VMware Solutions.
Capacity (GB) 20
LUN Id 0
Endurance Tier READHEAVY_TIER
Endurance Tier Per IOPS 2
Datacenter dal12
Target IP 161.26.110.17
Snapshot Size (GB) 5
Snapshot Used (Bytes) 3325952
 of Active Transactions 0
Replicant Count 0

The output shows the hostname of the storage device, the LUN ID, and the Target IP:

IBM02SEL1575811-3 lun id: 0 Target IP: 161.26.110.17
IBM02SEL1575811-4 lun id: 1 Target IP: 161.26.110.43
3. You can further confirm this information by using the following command iscsiadm -m session -P 3.

 iscsiadm -m session -P 3
iSCSI Transport Class version 2.0-870
version 6.2.0.874-7
Target: iqn.1992-08.com.netapp:stfdal1201 (non-flash)
Current Portal: 161.26.110.17:3260,1027 match this target iscsi IP to the block storage device
Persistent Portal: 161.26.110.17:3260,1027

Interface:

Iface Name: default
Iface Transport: tcp
Iface Initiatorname: iqn.2018-08.com.ibm:ibm02su1575811-i117305979
Iface IPaddress: 10.74.10.67
Iface HWaddress: <empty>
Iface Netdev: <empty>
SID: 1
iSCSI Connection State: LOGGED IN
iSCSI Session State: LOGGED_IN
Internal iscsid Session State: NO CHANGE

Timeouts:

Recovery Timeout: 5
Target Reset Timeout: 30
LUN Reset Timeout: 30
Abort Timeout: 15

CHAP:

username: IBM02SU1575811-I117305979
password: 
username_in: <empty>
password_in:
MgmtOverheadCores<br><br>[2] The number of cores reserved by the vCenter Server management components (vCenter Server, PSC, AD/DNS, Edges) Cores 5 5 
 vSphereHAHostTolerance<br><br>[3] The number of hosts to tolerate in the vSphere HA configuration Hosts 1 1 
 HostVsanOverheadCorePercentage The percentage of a host's cores used by vSAN % 10 0 







 Formula to calculate the available memory 

AvailableMemory = [HostMemory - HostOverheadMemory - HostVsanOverheadMemory - (HostVsanOverheadMemoryDiskPercentage * HostVsanCapacityDiskSize)] * (HostCount - vSphereHAHostTolerance) - MgmtOverheadMemory

The following table lists the variables that are used in the previous formula.



Table 4. Description of variables in formula 2

 Variable Description Unit vSAN example NFS example 

 AvailableMemory The number of GB of memory available for workloads and services in the environment GB 693 860 
 HostCount The number of hosts in the default cluster Hosts 6 6 
 HostMemory The number of raw GB of memory available in each host in the default cluster GB 192 192 
 HostVsanCapacityDiskSize The number of GB of a capacity of each vSAN capacity SSD disk on this host GB 960, 1,946, or 3,891 0 
 HostOverheadMemory The number of GB of memory that is reserved by the ESXi server as overhead GB 4.6 4.6 
 MgmtOverheadMemory<br><br>[4] The number of GB of memory reserved by the vCenter Server management components (vCenter Server, PSC, AD/DNS, Edges) GB 77 77 
 vSphereHAHostTolerance<br><br>[5] The number of hosts to tolerate in the vSphere HA configuration Hosts 1 1 
 HostVsanOverheadMemoryDiskPercentage The number of GB of memory reserved by vSAN management (represented as percentage of one of the capacity vSAN disks) % 2.75% 2.75%