vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* Updates the UBI to version 8.7-1085.1679482090.







 Revision 16, released 21 March 2023 



* Resolves the following CVEs: [CVE-2023-23916](https://nvd.nist.gov/vuln/detail/CVE-2023-23916)
* Updates the UBI to version 8.7-1085.
* Updates Go to version 1.19.6.







 Revision 15, released 6 March 2023 



* Resolves the following CVEs: [CVE-2022-4415](https://nvd.nist.gov/vuln/detail/CVE-2022-4415)[CVE-2020-10735](https://nvd.nist.gov/vuln/detail/CVE-2020-10735)[CVE-2021-28861](https://nvd.nist.gov/vuln/detail/CVE-2021-28861)[CVE-2022-45061](https://nvd.nist.gov/vuln/detail/CVE-2022-45061)[CVE-2022-40897](https://nvd.nist.gov/vuln/detail/CVE-2022-40897)[CVE-2022-41723](https://nvd.nist.gov/vuln/detail/CVE-2022-41723)[CVE-2022-41724](https://nvd.nist.gov/vuln/detail/CVE-2022-41724)
* Updates the UBI to version 8.7-1085.
* Updates Go to version 1.19.6.







 Revision 14, released 20 February 2023 



* Resolves the following CVEs: [CVE-2022-47629](https://nvd.nist.gov/vuln/detail/CVE-2022-47629)
* Updates the UBI to version 8.7-1049.1675784874.
U33","omegad12X15||U32","omegad19X16||U35","omegad14X16||U34","omegad18X17||U36","omegad15X18||U37","omegad21X18||U39","omegad17X18||U38","omegad22X19||U42","omegad16X19||U40","omegad20X19||U41","omegad19X20||U43","omegad18X21||U44","omegad23X21||U45","omegad19X22||U46","omegad25X22||U47","omegad24X23||U49","omegad21X23||U48","omegad23X24||U50","omegad25X24||U51","omegad26X25||U54","omegad24X25||U53","omegad22X25||U52","omegad25X26||U55"],"osc":{},"qub":{"0":3,"1":3,"10":3,"11":3,"12":3,"13":3,"14":3,"15":3,"16":3,"17":3,"18":3,"19":3,"2":3,"20":3,"21":3,"22":3,"23":3,"24":3,"25":3,"26":3,"3":3,"4":3,"5":3,"6":3,"7":3,"8":3,
* [Revision 16, released 21 March 2023](https://cloud.ibm.com/docs/satellite?topic=satellite-cl-netapp-ontap-nasnetapp-ontap-nas-22.04-rev-16-change-log)
* [Revision 15, released 6 March 2023](https://cloud.ibm.com/docs/satellite?topic=satellite-cl-netapp-ontap-nasnetapp-ontap-nas-22.04-rev-15-change-log)
* [Revision 14, released 20 February 2023](https://cloud.ibm.com/docs/satellite?topic=satellite-cl-netapp-ontap-nasnetapp-ontap-nas-22.04-rev-14-change-log)



* [Version 21.04](https://cloud.ibm.com/docs/satellite?topic=satellite-cl-netapp-ontap-nas21.04-change-log)



* [Revision 21, released 19 June 2023](https://cloud.ibm.com/docs/satellite?topic=satellite-cl-netapp-ontap-nasnetapp-ontap-nas-21.04-rev-21-change-log)
* [Revision 20, released 21 April 2023](https://cloud.ibm.com/docs/satellite?topic=satellite-cl-netapp-ontap-nasnetapp-ontap-nas-21.04-rev-20-change-log)
* [Revision 19, released 4 April 2023](https://cloud.ibm.com/docs/satellite?topic=satellite-cl-netapp-ontap-nasnetapp-ontap-nas-21.04-rev-19-change-log)
* [Revision 18, released 21 March 2023](https://cloud.ibm.com/docs/satellite?topic=satellite-cl-netapp-ontap-nasnetapp-ontap-nas-21.04-rev-18-change-log)
ibmcloud sl file snapshot-create VOLUME_ID [OPTIONS]

Command options:

-n, --note
: Notes to set on the new snapshot.

Examples:

ibmcloud sl file snapshot-create 12345678 --note snapshotforibmcloud

This command creates a snapshot for volume with ID 12345678 and with addition note as snapshotforibmcloud.





 ibmcloud sl file snapshot-disable 

Disable snapshots on the specified schedule for a given volume:

ibmcloud sl file snapshot-disable VOLUME_ID [OPTIONS]

Command options:

-s, --schedule-type
: Required. Snapshot schedule, options are: HOURLY, DAILY, WEEKLY.

Examples:

ibmcloud sl file snapshot-disable 12345678 -s DAILY

This command disables daily snapshot for volume with ID 12345678.





 ibmcloud sl file snapshot-enable 

Enable snapshots for a volume on the specified schedule:

ibmcloud sl file snapshot-enable VOLUME_ID [OPTIONS]

Command options:

-s, --schedule-type
: Required. Snapshot schedule, options are: HOURLY,DAILY,WEEKLY.

-c, --retention-count
: Required. Number of snapshots to retain.

-m, --minute
: Minute of the hour when snapshots should be taken, integer 0 - 59.

-r, --hour
: Hour of the day when snapshots should be taken, integer 0 - 23.

-d, --day-of-week
: Day of the week when snapshots should be taken, integer 0 - 6. 0 means Sunday, 1 means Monday, 2 means Tuesday, 3 means Wednesday, 4 means Thursday, 5 means Friday, 6 means Saturday.

Examples:

ibmcloud sl file snapshot-enable 12345678 -s WEEKLY -c 5 -m 0 --hour 2 -d 0

This command enables snapshot for volume with ID 12345678.
ibmcloud sl file snapshot-disable 

Disable snapshots on the specified schedule for a given volume:

ibmcloud sl file snapshot-disable VOLUME_ID [OPTIONS]

Command options:

-s, --schedule-type
: Required. Snapshot schedule, options are: HOURLY, DAILY, WEEKLY.

Examples:

ibmcloud sl file snapshot-disable 12345678 -s DAILY

This command disables daily snapshot for volume with ID 12345678.





 ibmcloud sl file snapshot-enable 

Enable snapshots for a volume on the specified schedule:

ibmcloud sl file snapshot-enable VOLUME_ID [OPTIONS]

Command options:

-s, --schedule-type
: Required. Snapshot schedule, options are: HOURLY,DAILY,WEEKLY.

-c, --retention-count
: Required. Number of snapshots to retain.

-m, --minute
: Minute of the hour when snapshots should be taken, integer 0 - 59.

-r, --hour
: Hour of the day when snapshots should be taken, integer 0 - 23.

-d, --day-of-week
: Day of the week when snapshots should be taken, integer 0 - 6. 0 means Sunday, 1 means Monday, 2 means Tuesday, 3 means Wednesday, 4 means Thursday, 5 means Friday, 6 means Saturday.

Examples:

ibmcloud sl file snapshot-enable 12345678 -s WEEKLY -c 5 -m 0 --hour 2 -d 0

This command enables snapshot for volume with ID 12345678. The snapshot is taken weekly on every Sunday at 2:00, and up to 5 snapshots are retained.





 ibmcloud sl file snapshot-delete 

Delete a snapshot on a volume:

ibmcloud sl file snapshot-delete SNAPSHOT_ID

Examples:

ibmcloud sl file snapshot-delete 12345678

This command deletes snapshot with ID 12345678.





 ibmcloud sl file snapshot-list
1.223e-6, // Bandwidth by region Rest Of APAC
0 // Bandwidth by region South America
],
"percentage": [ // The percentage of the bandwidth by regions
null,
null,
null,
null,
null,
null,
null,
null,
null,
null,
null,
null,
null,
0, // Australasia
74.14454067868806, // EMEA
0, // India
0, // Japan
23.374779416239022, // North America
2.480679905072919, // Rest Of APAC
0 // South America
],
"time": [
"1590969600",
"1591142400",
"1591228800",
"1591315200"
],
"xaxis": null,
"yaxis1": [ // TotalHits per day
4,
1,
6,
4
],
"yaxis2": [ // TotalBandwidth per day
6.371999999999999e-6,
4.525e-6,
2.7596e-5,
1.0808e-5
],
"yaxis3": [ // Hits by type 0XX per day
0,
0,
0,
0
],
"yaxis4": [ // Hits by type 200 per day
0,
0,
0,
0
],
"yaxis5": [ // Hits by type 206 per day
0,
0,
0,
0
],
"yaxis6": [ // Hits by type 2XX per day
0,
0,
0,
0
],
kubectl get pods --all-namespaces -o=jsonpath='{range .items[]}{"n"}{.metadata.name}{":t"}{range .spec.volumes[]}{.persistentVolumeClaim.claimName}{" "}{end}{end}' | grep "<pvc_name>"
5. Log in to your pod.

kubectl exec -it <pod_name> bash
6. Show the disk usage statistics and find the server path for your volume that you retrieved earlier.

df -h

Example output

Filesystem Size Used Avail Use% Mounted on
overlay 99G 4.8G 89G 6% /
tmpfs 64M 0 64M 0% /dev
tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup
fsf-dal1001g-fz.adn.networklayer.com:/IBM01SEV1234567_6/data01 40G 0 40G 0% /myvol



Although the size and IOPS of your physical storage changed, these values are not reflected in your PV or PVC. If you describe your PV or PVC, the old size and IOPS continue to display. You have the option to manually update the size and IOPS in your PV by using the kubectl patch pv command. However, this command can't be used to change the size or IOPS in the PVC. To prevent having different sizes and IOPS in your PVC and PV, leave both your PVC and PV as-is.





 Changing the default NFS version 

The version of the File Storage for Classic determines the protocol that is used to communicate with the IBM Cloud File Storage for Classic server. By default, all File Storage for Classic instances are set up with NFS version 4. You can change your existing PV to an older NFS version if your app requires a specific version to properly function.
overlay 99G 4.8G 89G 6% /
tmpfs 64M 0 64M 0% /dev
tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup
fsf-dal1001g-fz.adn.networklayer.com:/IBM01SEV1234567_6/data01 40G 0 40G 0% /myvol



Although the size and IOPS of your physical storage changed, these values are not reflected in your PV or PVC. If you describe your PV or PVC, the old size and IOPS continue to display. You have the option to manually update the size and IOPS in your PV by using the oc patch pv command. However, this command can't be used to change the size or IOPS in the PVC. To prevent having different sizes and IOPS in your PVC and PV, leave both your PVC and PV as-is.





 Changing the default NFS version 

The version of the File Storage for Classic determines the protocol that is used to communicate with the IBM Cloud File Storage for Classic server. By default, all File Storage for Classic instances are set up with NFS version 4. You can change your existing PV to an older NFS version if your app requires a specific version to properly function.

To change the default NFS version, you can either create a new storage class to dynamically provision File Storage for Classic in your cluster, or choose to change an existing PV that is mounted to your pod.

To apply the latest security updates and for a better performance, use the default NFS version and don't change to an older NFS version.



 Creating a customized storage class with a specific NFS version 



1. Create a [customized storage class](https://cloud.ibm.com/docs/openshift?topic=openshift-file_storagenfs_version_class) with the NFS version that you want to provision.
2. Create the storage class in your cluster.

oc apply -f nfsversion_storageclass.yaml
3. Verify that the customized storage class was created.

oc get storageclasses
4.
vx2d-* profiles - Setup Instructions 

See the step by step instructions for setting up the file systems here. The according volume sizes are captured in the table 6. Read the section [Adding Block Storage for VPC](https://cloud.ibm.com/docs/sap?topic=sap-vs-set-up-infrastructurevs-adding-vpc-block-storage) to see how to attach the volumes to the HANA server. Some disks are governed by the Linux Logical Volume Manager LVM or lvm2.

For each profile, consider the specified volume sizes in table 6 and always make sure that the correct disks are given for the respective commands. The Linux command fdisk -l shows which disk is to the volume, for example /dev/vde.



 vx2d-16x224 



1. Create the volume group for LVM.

[root@vx2d-16x224 ] pvcreate /dev/vde
[root@vx2d-16x224 ] vgcreate hana_vg /dev/vde
2. After the volume group is created, three logical volumes are defined on top. These logical volumes reflect the file system size requirements for SAP HANA.

[root@vx2d-16x224 ] lvcreate -L 224G -n hana_shared_lv hana_vg
[root@vx2d-16x224 ] lvcreate -L 224G -n hana_log_lv hana_vg
[root@vx2d-16x224 ] lvcreate -l 100%VG -n hana_data_lv hana_vg
3. Next, add these entries to /etc/fstab

LABEL=HANA_SHARED /hana/shared xfs defaults,inode64 0 0
LABEL=HANA_LOG /hana/log xfs defaults,swalloc,inode64 0 0
LABEL=HANA_DATA /hana/data xfs defaults,largeio,swalloc,inode64 0 0
4.
Flags: 	(no flags)

Data segments:
0: crypt
offset: 16777216 [bytes]
length: (whole device)
cipher: aes-xts-plain64
sector: 512 [bytes]

Keyslots:
0: luks2
Key: 512 bits
Priority: normal
Cipher: aes-xts-plain64
Cipher key: 512 bits
PBKDF: argon2i
Time cost: 4
Memory: 737817
Threads: 2
Salt: c3 c9 89 88 35 3a fb 32 4e 64 a0 5c 58 33 c0 92
af c1 0c 98 78 d8 eb a0 b5 ea 67 4b 00 86 59 63
AF stripes: 4000
AF hash: sha256
Area offset:32768 [bytes]
Area length:258048 [bytes]
Digest ID: 0
1: luks2
Key: 512 bits
Priority: normal
Cipher: aes-xts-plain64
Cipher key: 512 bits
PBKDF: argon2i
Time cost: 4
Memory: 682321
Threads: 2
Salt: ac 17 b7 43 2b 82 e1 68 a9 77 a3 8f ef 3b 42 10
9f 28 60 22 f3 ff 71 c5 03 cf 32 28 1a db e1 96
AF stripes: 4000
AF hash: sha256
Area offset:290816 [bytes]
Area length:258048 [bytes]
Digest ID: 0
Tokens:
Digests:
0: pbkdf2
Hash: sha256
Iterations: 106736
Salt: a4 57 7d 09 e8 cd 56 e7 ad 4c 14 d8 15 b4 38 88
84 63 a8 7d 2a e8 2d d8 46 b6 87 2f 87 fa a9 e0
Digest: 09 aa 56 8f 14 dd c7 76 9a 51 5e 74 b9 1b 95 8a
Space In Use (Bytes): 209715
Free Space Left (Bytes): 1887437

Command Result : 0 (Success)

The command hsm showpolicies should now show that the device is using the FIPS 140-2 mode on policy (code) 12, and reflect the enforcement of FIPS 140-2 algorithms:

[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 Off 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)
* [CVE-2022-3515](https://nvd.nist.gov/vuln/detail/CVE-2022-3515)









 Change log for version 5.0, released 11 October 2022 



* Adds snapshot support for cluster versions 4.9 and later.
* Makes the resource requests and limits of the vpc-block-csi-driver containers configurable. To view the config run kubectl get cm -n kube-system addon-vpc-block-csi-driver-configmap -o yaml
* Adds the following parameters for customizing the driver.



* AttachDetachMinRetryGAP: "3": The initial retry interval for checking Attach/Detach Status. The default is 3 seconds.
* AttachDetachMinRetryAttempt: "3": The number of attempts for AttachDetachMinRetryGAP. The default is 3 retries for 3 seconds retry gap.
* AttachDetachMaxRetryAttempt: "46": Total number of retries for checking Attach/Detach Status. Default is 46 times. For example, 7 minutes (3 secs * 3 times + 6 secs * 6 times + 10 secs * 10 times).
* AttacherWorkerThreads: "15": The number of goroutines for processing VolumeAttachments.
* AttacherKubeAPIBurst: "10": The number of requests to the Kubernetes API server, exceeding the QPS, that can be sent at any given time
* AttacherKubeAPIQPS: "5.0": The number of requests per second sent by a Kubernetes client to the Kubernetes API server.



* Disables the handle-volume-inuse-error option as this is applies to CSI drivers that support offline expansion only.







 Change log for version 5.0.4-beta_1566, released 14 July 2022 



* Updates the storage-secret-sidecar image to v1.1.12.
* Updates Golang to version 1.18.3.
* [CVE-2022-3515](https://nvd.nist.gov/vuln/detail/CVE-2022-3515)









 Change log for version 5.0, released 11 October 2022 



* Adds snapshot support for cluster versions 1.25 and later.
* Makes the resource requests and limits of the vpc-block-csi-driver containers configurable. To view the config run kubectl get cm -n kube-system addon-vpc-block-csi-driver-configmap -o yaml
* Adds the following parameters for customizing the driver.



* AttachDetachMinRetryGAP: "3": The initial retry interval for checking Attach/Detach Status. The default is 3 seconds.
* AttachDetachMinRetryAttempt: "3": The number of attempts for AttachDetachMinRetryGAP. The default is 3 retries for 3 seconds retry gap.
* AttachDetachMaxRetryAttempt: "46": Total number of retries for checking Attach/Detach Status. Default is 46 times. For example, 7 minutes (3 secs * 3 times + 6 secs * 6 times + 10 secs * 10 times).
* AttacherWorkerThreads: "15": The number of goroutines for processing VolumeAttachments.
* AttacherKubeAPIBurst: "10": The number of requests to the Kubernetes API server, exceeding the QPS, that can be sent at any given time
* AttacherKubeAPIQPS: "5.0": The number of requests per second sent by a Kubernetes client to the Kubernetes API server.



* Disables the handle-volume-inuse-error option as this is applies to CSI drivers that support offline expansion only.







 Change log for version 5.0.4-beta_1566, released 14 July 2022 



* Updates the storage-secret-sidecar image to v1.1.12.
* Updates Golang to version 1.18.3.
netapp-ontap-san change log 

Review the version history for the netapp-ontap-san Satellite storage template.



 Version 22.10 



 Revision 6, released 19 June 2023 



* Resolves the following CVEs: [CVE-2022-43552](https://nvd.nist.gov/vuln/detail/CVE-2022-43552)[CVE-2022-3204](https://nvd.nist.gov/vuln/detail/CVE-2022-3204)[CVE-2023-27535](https://nvd.nist.gov/vuln/detail/CVE-2023-27535)[CVE-2022-36227](https://nvd.nist.gov/vuln/detail/CVE-2022-36227)[CVE-2022-35252](https://nvd.nist.gov/vuln/detail/CVE-2022-35252)
* Updates the UBI to version 8.8-860.







 Revision 5, released 21 April 2023 



* Resolves the following CVEs: [CVE-2023-0361](https://nvd.nist.gov/vuln/detail/CVE-2023-0361)
* Updates the UBI to version 8.7-1107.
* Ignore aggregate usage limit if set to 0%







 Revision 4, released 4 April 2023
netapp-ontap-nas change log 

Review the version history for the netapp-ontap-nas Satellite storage template.



 Version 22.10 



 Revision 6, released 19 June 2023 



* Resolves the following CVEs: [CVE-2022-43552](https://nvd.nist.gov/vuln/detail/CVE-2022-43552)[CVE-2022-3204](https://nvd.nist.gov/vuln/detail/CVE-2022-3204)[CVE-2023-27535](https://nvd.nist.gov/vuln/detail/CVE-2023-27535)[CVE-2022-36227](https://nvd.nist.gov/vuln/detail/CVE-2022-36227)[CVE-2022-35252](https://nvd.nist.gov/vuln/detail/CVE-2022-35252)
* Updates the UBI to version 8.8-860.







 Revision 5, released 21 April 2023 



* Resolves the following CVEs: [CVE-2023-0361](https://nvd.nist.gov/vuln/detail/CVE-2023-0361)
* Updates the UBI to version 8.7-1107.
* Ignore aggregate usage limit if set to 0%







 Revision 4, released 4 April 2023
ibmcloud ce project get -n myproject

Example output

Getting project 'myproject'...
OK

Name: myproject
ID: abcdabcd-abcd-abcd-abcd-f1de4aab5d5d
Status: active
Enabled: true
Application Private Visibility Supported: false
Selected: true
Region: us-south
Resource Group: default
Service Binding Service ID: ServiceId-1234abcd-abcd-abcd-1111-1a2b3c4d5e6f
Age: 52d
Created: Tue, 28 Sep 2021 05:12:16 -0500
Updated: Tue, 28 Sep 2021 05:12:19 -0500

Quotas:
Category Used Limit
App revisions 1 60
Apps 1 20
Build runs 1 100
Builds 2 100
Configmaps 2 100
CPU 0 64
Ephemeral storage 0 256G
Instances (active) 0 250
Instances (total) 0 2500
Job runs 0 100
Jobs 0 100
Memory 0 256G
Secrets 6 100
Subscriptions (cron) 0 100
Subscriptions (IBM Cloud Object Storage) 0 100
Subscriptions (Kafka) 0 100
3. Create an application that is only visible to the private endpoint. Use the [ibmcloud ce application create](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-application-create) command with the --visibility=private option. Alternatively, you can use the console to create an app or update an existing app and set the [visibility of your app](https://cloud.ibm.com/docs/codeengine?topic=codeengine-application-workloadsoptionsvisibility).

ibmcloud ce application create -n myapp --visibility=private







 Accessing your app securely with service endpoints 

Before you begin, you must have an [IBM Cloud account](https://cloud.ibm.com/registration).



1.
: Day of the week when snapshots should be taken, integer 0 - 6. 0 means Sunday, 1 means Monday, 2 means Tuesday, 3 means Wednesday, 4 means Thursday, 5 means Friday, 6 means Saturday.

Examples:

ibmcloud sl file snapshot-enable 12345678 -s WEEKLY -c 5 -m 0 --hour 2 -d 0

This command enables snapshot for volume with ID 12345678. The snapshot is taken weekly on every Sunday at 2:00, and up to 5 snapshots are retained.





 ibmcloud sl file snapshot-delete 

Delete a snapshot on a volume:

ibmcloud sl file snapshot-delete SNAPSHOT_ID

Examples:

ibmcloud sl file snapshot-delete 12345678

This command deletes snapshot with ID 12345678.





 ibmcloud sl file snapshot-list 

List file storage snapshots:

ibmcloud sl file snapshot-list VOLUME_ID [OPTIONS]

Command options:

--sortby
: Column to sort by. Options are: id, name, created, size_bytes.

Examples:

ibmcloud sl file snapshot-list 12345678 --sortby id

This command lists all snapshots of volume with ID 12345678 and sorts them by ID.





 ibmcloud sl file snapshot-order 

Order snapshot space for a file storage volume:

ibmcloud sl file snapshot-order VOLUME_ID [OPTIONS]

Command options:

-s, --size
: Required. Size of snapshot space to create in GB.

-t, --tier
: Optional. Endurance Storage Tier (IOPS per GB) of the file volume for which space is ordered. Options are: 0.25, 2, 4, 10.

-i, --iops
: Performance Storage IOPs. Range 100-6000, and in multiples of 100.

-u, --upgrade
: Flag to indicate that the order is an upgrade.

-f, --force
Use the [ibmcloud ce project get](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-project-get) command to verify the output for Application Private Visibility Supported is set to true. If the value is false, [contact IBM support](https://cloud.ibm.com/docs/codeengine?topic=codeengine-get-support) to enable this capability within your existing project.

ibmcloud ce project get -n myproject

Example output

Getting project 'myproject'...
OK

Name: myproject
ID: abcdabcd-abcd-abcd-abcd-f1de4aab5d5d
Status: active
Enabled: true
Application Private Visibility Supported: true
Selected: true
Region: us-south
Resource Group: default
Service Binding Service ID: ServiceId-1234abcd-abcd-abcd-1111-1a2b3c4d5e6f
Age: 52d
Created: Tue, 28 Sep 2021 05:12:16 -0500
Updated: Tue, 28 Sep 2021 05:12:19 -0500

Quotas:
Category Used Limit
App revisions 1 60
Apps 1 20
Build runs 1 100
Builds 2 100
Configmaps 2 100
CPU 0 64
Ephemeral storage 0 256G
Instances (active) 0 250
Instances (total) 0 2500
Job runs 0 100
Jobs 0 100
Memory 0 256G
Secrets 6 100
Subscriptions (cron) 0 100
Subscriptions (IBM Cloud Object Storage) 0 100
Subscriptions (Kafka) 0 100
2. If Application Private Visibility Supported is true, then you can update your app to use private endpoints. Run the application update command. For example,

ibmcloud ce application update -n myapp --visibility=private

Example output

Updating application 'myapp' to latest revision.
[...]
node.conn[0].timeo.login_timeout = 15
node.conn[0].timeo.logout_timeout = 15
node.conn[0].timeo.noop_out_interval = 10
node.conn[0].timeo.noop_out_timeout = 15
node.session.iscsi.InitialR2T = No
node.session.iscsi.ImmediateData = Yes
node.session.iscsi.FirstBurstLength = 262144
node.session.iscsi.MaxBurstLength = 16776192
node.conn[0].iscsi.MaxRecvDataSegmentLength = 65536
Show more
5. Start iSCSI.

systemctl start iscsi.service
6. Run a discovery against the iscsi target host.

iscsiadm -m discovery -t sendtargets -p [IP address in StorageLayer]
7. Connect to the iscsi target host.

iscsiadm -m node -T [output from previous command, starting with IQN.] -p [IP address in StorageLayer] -l
8. Restart the iSCSI service. Because node.startup is set to automatic in iscsid.conf, it automatically logs in to the target host.

systemctl restart iscsi.service