vania-janet/multiturn-rag-retrieval-data huggingface dataset:
ibmcloud is instance-network-interface-update 

Update a network interface of a virtual server instance.

ibmcloud is instance-network-interface-update INSTANCE NIC --name NEW_NAME [--allow-ip-spoofing false | true] [--output JSON] [-q, --quiet]



 Command options 



* INSTANCE: ID or name of the instance.
* NIC: ID or name of the network interface.
* --name: New name of NIC.
* --allow-ip-spoofing: Disables the source and destination checks on this interface. If false, source IP spoofing is not allowed on this interface. One of: false, true.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



--------------------







 ibmcloud is instance-network-interfaces 

List all network interfaces of a virtual server instance.

ibmcloud is instance-network-interfaces INSTANCE [--output JSON] [-q, --quiet]



 Command options 



* INSTANCE: ID or name of the instance.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



--------------------







 ibmcloud is instance-profile 

View details of a virtual server instance profile.

ibmcloud is instance-profile PROFILE_NAME [--output JSON] [-q, --quiet]



 Command options 



* PROFILE_NAME: Name of the profile.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



--------------------







 ibmcloud is instance-profiles 

List all virtual server instance profiles in the region.
[the confirm icon](https://cloud.ibm.com/docs-content/v1/content/cd4be197c8921ed12923aa899ac93a8ab643c158/AnalyticsEngine/images/confirm.png) ![the confirm icon](https://cloud.ibm.com/docs-content/v1/content/cd4be197c8921ed12923aa899ac93a8ab643c158/AnalyticsEngine/images/confirm.png) 
 Invoke instance management REST API to view logging configuration ![the confirm icon](https://cloud.ibm.com/docs-content/v1/content/cd4be197c8921ed12923aa899ac93a8ab643c158/AnalyticsEngine/images/confirm.png) ![the confirm icon](https://cloud.ibm.com/docs-content/v1/content/cd4be197c8921ed12923aa899ac93a8ab643c158/AnalyticsEngine/images/confirm.png) ![the confirm icon](https://cloud.ibm.com/docs-content/v1/content/cd4be197c8921ed12923aa899ac93a8ab643c158/AnalyticsEngine/images/confirm.png) 
 Invoke instance management REST API to start or stop Spark history server ![the confirm icon](https://cloud.ibm.com/docs-content/v1/content/cd4be197c8921ed12923aa899ac93a8ab643c158/AnalyticsEngine/images/confirm.png) ![the confirm icon](https://cloud.ibm.com/docs-content/v1/content/cd4be197c8921ed12923aa899ac93a8ab643c158/AnalyticsEngine/images/confirm.png)
Time series key functionality 

The time series library provides various functions on univariate, multivariate, multi-key time series as well as numeric and categorical types. The functionality provided by the library can be broadly categorized into:



* Time series I/O, for creating and saving time series data
* Time series functions, transforms, windowing or segmentation, and reducers
* Time series SQL and SQL extensions to Spark to enable executing scalable time series functions



Some of the key functionality is shown in the following sections using examples.



 Time series I/O 

The primary input and output (I/O) functionality for a time series is through a pandas DataFrame or a Python list. The following code sample shows constructing a time series from a DataFrame:

>>> import numpy as np
>>> import pandas as pd
>>> data = np.array(['', 'key', 'timestamp', "value"],'', "a", 1, 27], '', "b", 3, 4], '', "a", 5, 17], '', "a", 3, 7], '', "b", 2, 45]])
>>> df = pd.DataFrame(data=data[1:, 1:], index=data[1:, 0], columns=data[0, 1:]).astype(dtype={'key': 'object', 'timestamp': 'int64', 'value': 'float64'})
>>> df
key timestamp value
a 1 27.0
b 3 4.0
a 5 17.0
a 3 7.0
b 2 45.0

Create a timeseries from a dataframe, providing a timestamp and a value column
>>> ts = tspy.time_series(df, ts_column="timestamp", value_column="value")
>>> ts
TimeStamp: 1 Value: 27.0
TimeStamp: 2 Value: 45.0
curl -H 'Authorization: Bearer <TOKEN>' -H 'Content-Type: application/json' -X GET https://api.us-south.ae.cloud.ibm.com/v3/analytics_engines/<instance-id>/livy/batches/<batch-id>/state

The response body for getting the state of the batch job:



Table 4. Response body for getting state of batch job

 Name Description Type 

 id The batch ID int 
 state State of submitted batch job string 



For example:

curl -i -X GET https://api.us-south.ae.cloud.ibm.com/v3/analytics_engines/43f79a18-768c-44c9-b9c2-b19ec78771bf/livy/batches/14/state -H 'content-type: application/json' -H "Authorization: Bearer $TOKEN"

Sample response:

{
"id": 14,
"state": "success"
}





 List all submitted jobs 

To list all of the submitted Spark batch jobs enter:

curl -H 'Authorization: Bearer <TOKEN>' -H 'Content-Type: application/json' -X GET https://api.us-south.ae.cloud.ibm.com/v3/analytics_engines/<instance-id>/livy/batches

The from and size properties are not supported in the request body although they are supported in the open source Livy REST interface.

The response body for listing all submitted Spark batch jobs:



Table 5. Response body for listing all submitted batch jobs

 Name Description Type 

 from The start index of the Spark batch jobs that are retrieved int 
 total The total number of batch jobs that are retireved int 
 sessions The details for each batch job in a session list 



For example:
"href": "https://uko.us-south.hs-crypto.cloud.ibm.com:9549/api/v4/vaults/5295ad47-2ce9-43c3-b9e7-e5a9482c362b"
},
"id": "314d0c9c-8808-47f0-829a-e63bdbb93854",
"name": "Azure Keystore Name ",
"description": "The AZURE keystore for testing.",
"groups":
"Azure Keystore Name "
],
"type": "azure_key_vault",
"created_at": "2022-03-09T11:00:04Z",
"updated_at": "2022-03-09T11:00:04Z",
"created_by": "IBMid-1308197YB4",
"updated_by": "IBMid-1308197YB4",
"href": "https://uko.us-south.hs-crypto.cloud.ibm.com:9549/api/v4/keystores/314d0c9c-8808-47f0-829a-e63bdbb93854",
"azure_resource_group": "EKMF-Web-Tests",
"azure_location": "europe_north",
"azure_service_principal_client_id": "c8e8540f-4f15-4b6b-8862-3ccdb389e35d",
"azure_service_principal_password": "",
"azure_tenant": "fcf67057-50c9-4ad4-98f3-ffca64add9e9",
"azure_subscription_id": "a9867d9b-582f-42f3-9392-26856b06b808",
"updated_at": "2022-03-09T15:40:52Z",
"created_by": "IBMid-1308197YB4",
"updated_by": "IBMid-1308197YB4",
"keystores": [
{
"group": "Production",
"type": "ibm_cloud_kms"
}
],
"href": "https://uko.us-south.hs-crypto.cloud.ibm.com:9549/api/v4/templates/ada4293c-07ed-4903-b3ee-419bd1a05fde"
}







 hpcs uko keystores 

List all target keystores in the instance.

If the --all-pages option is not set, the command only retrieves a single page of the collection.

ibmcloud hpcs uko keystores [--type TYPE] [--name NAME] [--description DESCRIPTION] [--group GROUP] [--groups GROUPS] [--vault-id VAULT-ID] [--location LOCATION] [--limit LIMIT] [--offset OFFSET] [--sort SORT]



* Command options

--type ([]string)
: Optional. The type of keystores that you want to retrieve. Values that can be set are: aws_kms, azure_key_vault, ibm_cloud_kms, and google_kms.

--name (string)
: Optional. Return only keystores whose name contains the string. The length must be between 1 and 100 characters. The value must match regular expression /.+/.

--description (string)
: Optional. Return only keystores whose description contains the string. The length must be between 1 and 200 characters. The value must match regular expression /.+/.

--group (string)
: Optional. The keystore group. This query parameter cannot be used in conjunction with the groups[] query parameter.
VMware vCenter and ESXi authenticate with the KMIP adapter instance by using certificates in VMware vCenter when the connection to the key management server (KMS) is created. The public certificate is installed into KMIP to identify the vCenter client or clients that are allowed to connect. Each client is authorized to all keys stored in that KMIP for VMware instance.





 Hyper Protect Crypto Services for vSphere encryption - no third parties 

The following figure shows a typical vSphere encryption setup with HPCS/KMIP integration:

Zoom

![vSphere encryption with Hyper Protect Crypto Services](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/images/vmware-vsphere-encryption.svg)

Figure 1. vSphere encryption with Hyper Protect Crypto Services - no third parties





 Hyper Protect Crypto Services for vSphere encryption - SaaS provider use case 

With HPCS, SaaS providers and SaaS consumers can move their most mission critical workloads to IBM Cloud with the highest level of security to prevent unauthorized access to their regulated data. SaaS providers and SaaS consumers both maintain complete control over their respective keys and regulated data in the cloud and no one, including IBM, has access to the regulated data. Additionally, no single person has access to the full key and if required multiple crypto unit administrators can be deployed.

Zoom

![vSphere encryption with Hyper Protect Crypto Services](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/images/vrw-hpcs-mgmt.svg)

Figure 2. vSphere encryption with Hyper Protect Crypto Services for SaaS providers

The SaaS provider is responsible for deploying and managing both Hyper Protect Crypto Services and the KMIP for VMware instance for their IBM Cloud for VMware Regulated Workloads instance.
"activation_date": "P5Y1M1W2D",
"expiration_date": "P1Y2M1W4D",
"state": "active"
},
"description": "IBM CLOUD key template description",
"created_at": "2022-03-09T15:40:52Z",
"updated_at": "2022-03-09T15:40:52Z",
"created_by": "IBMid-1308197YB4",
"updated_by": "IBMid-1308197YB4",
"keystores": [
{
"group": "Production",
"type": "ibm_cloud_kms"
}
],
"href": "https://uko.us-south.hs-crypto.cloud.ibm.com:9549/api/v4/templates/ada4293c-07ed-4903-b3ee-419bd1a05fde"
}







 hpcs uko keystores 

List all target keystores in the instance.

If the --all-pages option is not set, the command only retrieves a single page of the collection.

ibmcloud hpcs uko keystores [--type TYPE] [--name NAME] [--description DESCRIPTION] [--group GROUP] [--groups GROUPS] [--vault-id VAULT-ID] [--location LOCATION] [--limit LIMIT] [--offset OFFSET] [--sort SORT]



* Command options

--type ([]string)
: Optional. The type of keystores that you want to retrieve. Values that can be set are: aws_kms, azure_key_vault, ibm_cloud_kms, and google_kms.

--name (string)
: Optional. Return only keystores whose name contains the string. The length must be between 1 and 100 characters.
HCX Syslog User configured Connection between HCX (the client) and the Syslog server. Values for the Syslog port and protocol are specified in the vSphere Web Client. For example, port 514 for UDP protocol. 
 HCX HCX-IX 8123 TCP Send host-based replication service instructions to the HCX-IX. HTTP 
 HCX HCX-IX 9443 TCP Send management instructions to the local HCX-IX by using the REST API. HTTP <br>HTTPS 
 HCX-IX HCX-NE 443 TCP Send management instructions from HCX-IX to HCX-NE when HCX-NE uses the same path as the HCX-IX. HTTP <br>HTTPS 
 HCX-IX HCX-NE 8443 TCP Bidirectional management instructions from HCX-IX to HCX-NE, when HCX-NE uses an alternative data path. HTTP <br>HTTPS 
 HCX-NE HCX-NE (remote) 443 TCP Bidirectional management instructions from HCX-IX to HCX-NE, when HCX-NE uses an alternative data path. HTTP <br>HTTPS 
 HCX-IX ESXi hosts 80, 902 TCP Management and OVF deployment Internal 
 ESXi Hosts HCX-IX 31031, 44046 TCP Internal host-based replication traffic Internal 
 HCX-IX ESXi hosts 8000 TCP vMotion (zero downtime migration) 
 HCX-IX (local) HCX-IX <br>(remote) 4500 UDP Internet Key Exchange (IKEv2) to encapsulate workloads for the bidirectional tunnel IPsec 
 HCX-IX (local) HCX-IX <br>(remote) 500 UDP Internet Key Exchange (ISAKMP) for the bidirectional tunnel IPsec 





 Related links 



* [VMware HCX ports and protocols](https://ports.vmware.com/home/VMware-HCX)
* Key Management Interoperability Protocol (KMIP) adapter is used to configure the KMIP for VMware service with Hyper Protect Crypto Services to enable vSphere encryption or vSAN encryption by using your own root keys.
* Certificate Manager Server receives and processes requests for setting up certificate administrator signature keys and client certificates to enable the second layer of authentication in GREP11 or PKCS #11 API connections.



Trusted Key Entry commands

Key management

HSM APIs



Table 3. Lists service access roles as they apply to Hyper Protect Crypto Services TKE commands

 Action Reader ReaderPlus Writer Manager Crypto unit administrator 

 TKE view state: ibmcloud tke cryptounit-admins,ibmcloud tke cryptounit-compare,ibmcloud tke cryptounit-thrhlds,ibmcloud tke cryptounit-mk. ![checkmark icon](https://cloud.ibm.com/docs-content/v1/content/217f108cc44e2ce15fb692d4b57b4c628464e908/icons/checkmark-icon.svg) 
 TKE set context: ibmcloud tke-cryptounit-add, ibmcloud tke-cryptounit-rm. ![checkmark icon](https://cloud.ibm.com/docs-content/v1/content/217f108cc44e2ce15fb692d4b57b4c628464e908/icons/checkmark-icon.svg) 
 TKE admin add or remove: ibmcloud tke cryptounit-admin-add, ibmcloud tke cryptounit-admin-rm. ![checkmark icon](https://cloud.ibm.com/docs-content/v1/content/217f108cc44e2ce15fb692d4b57b4c628464e908/icons/checkmark-icon.svg) !
"azure_service_principal_client_id": "c8e8540f-4f15-4b6b-8862-3ccdb389e35d",
"azure_service_principal_password": "",
"azure_tenant": "fcf67057-50c9-4ad4-98f3-ffca64add9e9",
"azure_subscription_id": "a9867d9b-582f-42f3-9392-26856b06b808",
"azure_environment": "azure"
},
{
"vault": {
"id": "5295ad47-2ce9-43c3-b9e7-e5a9482c362b",
"name": "Test Vault Name",
"href": "https://uko.us-south.hs-crypto.cloud.ibm.com:9549/api/v4/vaults/5295ad47-2ce9-43c3-b9e7-e5a9482c362b"
},
"id": "f6a5ccc1-7fc3-435e-9637-482e470ba8e8",
"name": "IBM Keystore Name",
"description": "The description of the created keystore.",
"groups":
"IBM Keystore Name"
],
"type": "ibm_cloud_kms",
"created_at": "2022-03-09T11:00:11Z",
"updated_at": "2022-03-09T11:00:11Z",
"created_by": "IBMid-1308197YB4",
"updated_by": "IBMid-1308197YB4",
"azure_subscription_id": "a9867d9b-582f-42f3-9392-26856b06b808",
"azure_environment": "azure"
},
{
"vault": {
"id": "5295ad47-2ce9-43c3-b9e7-e5a9482c362b",
"name": "Test Vault Name",
"href": "https://uko.us-south.hs-crypto.cloud.ibm.com:9549/api/v4/vaults/5295ad47-2ce9-43c3-b9e7-e5a9482c362b"
},
"id": "f6a5ccc1-7fc3-435e-9637-482e470ba8e8",
"name": "IBM Keystore Name",
"description": "The description of the created keystore.",
"groups":
"IBM Keystore Name"
],
"type": "ibm_cloud_kms",
"created_at": "2022-03-09T11:00:11Z",
"updated_at": "2022-03-09T11:00:11Z",
"created_by": "IBMid-1308197YB4",
"updated_by": "IBMid-1308197YB4",
"href": "https://uko.us-south.hs-crypto.cloud.ibm.com:9549/api/v4/keystores/f6a5ccc1-7fc3-435e-9637-482e470ba8e8",
"ibm_api_endpoint": "https://us-south.kms.cloud.ibm.com",
: See the Istio release notes for [Istio 1.16.3](https://istio.io/latest/news/releases/1.16.x/announcing-1.16.3/.).
: Resolves the following CVEs:



* [CVE-2022-28321](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-28321)
* [CVE-2022-4203](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-4203)
* [CVE-2022-4304](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-4304)
* [CVE-2022-4450](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-4450)
* [CVE-2023-0215](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-0215)
* [CVE-2023-0216](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-0216)
* [CVE-2023-0217](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-0217)
* [CVE-2023-0286](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-0286)
* [CVE-2023-0401](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-0401)
"href": "https://us-south.iaas.cloud.ibm.com/v1/bare_metal_servers/2302-5e095b83-ceb4-49b5-9699-0aa5a2c996a4/disks/2302-8372237f-77cb-47e4-9c61-b9d19ddfdbcd",
"id": "2302-8372237f-77cb-47e4-9c61-b9d19ddfdbcd",
"interface_type": "nvme",
"name": "could-kilt-twisty-unloaded",
"resource_type": "bare_metal_server_disk",
"size": 3200
},
{
"created_at": "2021-03-12T09:29:17.000Z",
"href": "https://us-south.iaas.cloud.ibm.com/v1/bare_metal_servers/2302-5e095b83-ceb4-49b5-9699-0aa5a2c996a4/disks/2302-e544d72d-ca08-4924-b748-a8f67b66286d",
"id": "2302-e544d72d-ca08-4924-b748-a8f67b66286d",
"interface_type": "nvme",
"name": "wildcat-impromptu-dribble-hesitate",
"resource_type": "bare_metal_server_disk",
"size": 3200
},
{
"created_at": "2021-03-12T09:29:17.000Z",
: See the Istio release notes for [Istio 1.17.3](https://istio.io/latest/news/releases/1.17.x/announcing-1.17.3/).
: Resolves the following CVEs:



* [CVE-2019-17594](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17594)
* [CVE-2019-17595](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17595)
* [CVE-2021-39537](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-39537)
* [CVE-2022-29458](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29458)
* [CVE-2023-29491](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-29491)
* [CVE-2023-1255](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-1255)
* [CVE-2023-2650 ](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-2650)
* [CVE-2022-3996](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-3996)
* [CVE-2023-0464](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-0464)
The content of the encrypted registration definition is located [here](https://cloud.ibm.com/docs/hp-virtual-servers?topic=hp-virtual-servers-imagebuilddeploysecurebuild).

Then, use the following command line to provision a new instance of the Secure Build Server. Insert the values for the environment variables CLIENT_CRT and CLIENT_CA, SERVER_CRT and SERVER_KEY taken from the output of the preceding command.

ibmcloud hpvs instance-create SBContainer lite-s dal13 --rd-path "secure_build.asc" -i 1.3.0.10 --hostname sbs.example.com -e CLIENT_CRT=... -e CLIENT_CA=... -e SERVER_CRT=... -e SERVER_KEY=...

SBContainer defines the name of the instance to be created, lite-s is the pricing plan, and dal13 is the location - you can use a different one. Ensure that you use the image tag 1.3.0.10 because this tag references the up-to-date version of the Secure Build Server. sbs.example.com is the server hostname that was specified in the sbs-config.json file. For more information about available pricing plans and regions and datacenters, see [here](https://cloud.ibm.com/docs/hpvs-cli-plugin?topic=hpvs-cli-plugin-hpvs_cli_plugincreate_instance).





 9. Display your Secure Build Server instance. 

To view information about the Secure Build Server instance and other Hyper Protect Virtual Servers instances that you have provisioned, use the following command line:

ibmcloud hpvs instances

The command displays detailed information about the Hyper Protect Virtual Servers instances you have provisioned.

The following snippet shows example output for a Secure Build Server instance that is being provisioned:

Name SBContainer
"name": "Azure Keystore Name ",
"description": "The AZURE keystore for testing.",
"groups":
"Azure Keystore Name "
],
"type": "azure_key_vault",
"created_at": "2022-03-09T11:00:04Z",
"updated_at": "2022-03-09T11:00:04Z",
"created_by": "IBMid-1308197YB4",
"updated_by": "IBMid-1308197YB4",
"href": "https://uko.us-south.hs-crypto.cloud.ibm.com:9549/api/v4/keystores/314d0c9c-8808-47f0-829a-e63bdbb93854",
"azure_resource_group": "EKMF-Web-Tests",
"azure_location": "europe_north",
"azure_service_principal_client_id": "c8e8540f-4f15-4b6b-8862-3ccdb389e35d",
"azure_service_principal_password": "",
"azure_tenant": "fcf67057-50c9-4ad4-98f3-ffca64add9e9",
"azure_subscription_id": "a9867d9b-582f-42f3-9392-26856b06b808",
"azure_environment": "azure"
},
{
"vault": {
"id": "5295ad47-2ce9-43c3-b9e7-e5a9482c362b",
"name": "Test Vault Name",
CRN crn:v1:staging:public:is:us-south-1:a/efe5afc483594adaa8325e2b4d1290df::share:0e8ee997-bf1d-4165-9573-726c3a4d3b36
Lifecycle state stable
Zone us-south-1
Profile tier-5iops
Size(GB) 40
IOPS 3000
Encryption provider_managed
Mount targets ID Name VPC ID VPC Name
No mounted targets found.

Resource group ID Name
11caaa983d9c4beb82690daab08717e9 Default

Created 2023-05-07T18:13:04+05:30
Last sync at 2023-05-06T05:53:28+05:53
Latest job succeeded
Replication share ID Name Resource type
0bb9c083-2ac5-43d5-962a-757f69d5e6c8 replica-p-share-4 share

Replication role source
Replication status active
Source share ID Name Resource type





 View mount targets for a file share from the CLI 

Run the ibmcloud is share-mount-targets command and specify the file share ID to see all mount targets for a file share.

ibmcloud is share-mount-targets SHARE_ID [--output JSON] [-q, --quiet]





 View mount target details from the CLI 

Run the ibmcloud is share-mount-target command and specify the share ID or name with the mount target name or ID.

See the following example.

ibmcloud is share-mount-target my-file-share-3 my-target1

Getting mount target ID my-target1 for share ID my-file-share-3 under account Test Account as user test.user@ibm.com...

ID r026-c33d31bd-50e0-4401-abba-9c46ca698cb9
Name my-target1
VPC ID Name
helm ibmc --update
4. Install the most recent version of the ibm-object-storage-plugin for your operating system.

Example helm ibmc upgrade command for OS X and Linux.

helm ibmc upgrade ibm-object-storage-plugin ibm-helm/ibm-object-storage-plugin --set license=true [--set bucketAccessPolicy=false]

Example helm upgrade command for Windows.

helm upgrade ibm-object-storage-plugin ./ibm-object-storage-plugin --set dcname="${DC_NAME}" --set provider="${CLUSTER_PROVIDER}" --set workerOS="${WORKER_OS}" --region="${REGION} --set platform="${PLATFORM}" --set license=true [--set bucketAccessPolicy=false]

DC_NAME
: The cluster data center. To retrieve the data center, run oc get cm cluster-info -n kube-system -o jsonpath="{.data.cluster-config.json}{'n'}". Store the data center value in an environment variable by running SET DC_NAME=<datacenter>. Optional: Set the environment variable in Windows PowerShell by running $env:DC_NAME="<datacenter>".

CLUSTER_PROVIDER
: The infrastructure provider. To retrieve this value, run oc get nodes -o jsonpath="{.items[].metadata.labels.ibm-cloud.kubernetes.io/iaas-provider}{'n'}". If the output from the previous step contains softlayer, then set the CLUSTER_PROVIDER to "IBMC". If the output contains gc, ng, or g2, then set the CLUSTER_PROVIDER to "IBMC-VPC". Store the infrastructure provider in an environment variable. For example: SET CLUSTER_PROVIDER="IBMC-VPC".

WORKER_OS and PLATFORM
: The operating system of the worker nodes.