vania-janet/multiturn-rag-retrieval-data huggingface dataset:
: Optional: Do not show the message of the day or update reminders.



 Example cluster service unbind command 

ibmcloud oc cluster service unbind --cluster my_cluster --namespace my_namespace --service 8567221







 ibmcloud oc cluster subnet add 

Classic infrastructure

Make an existing portable public or private classic subnet in your IBM Cloud infrastructure account available to a cluster or reuse subnets from a deleted cluster instead of using the automatically provisioned subnets.

When you make a subnet available to a cluster, IP addresses of this subnet are used for cluster networking purposes. To avoid IP address conflicts, make sure that you use a subnet with one cluster only. Do not use a subnet for multiple clusters or for other purposes outside of IBM Cloud Kubernetes Service at the same time. If you use the same subnet across multiple clusters, your default Ingress TLS certificate might become invalidated. To enable communication between workers that are on different subnets on the same VLAN in non-VRF accounts, you must [enable routing between subnets on the same VLAN](https://cloud.ibm.com/docs/openshift?topic=openshift-subnetssubnet-routing).

ibmcloud oc cluster subnet add --cluster CLUSTER --subnet-id SUBNET [-q]

Minimum required permissions
: Operator platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

-c, --cluster CLUSTER
: Required: The name or ID of the cluster.

--subnet-id SUBNET
: Required: The ID of the subnet.

-q
: Optional: Do not show the message of the day or update reminders.



 Example cluster subnet add command 

ibmcloud oc cluster subnet add --cluster my_cluster --subnet-id 1643389







 ibmcloud oc cluster subnet create 

Classic infrastructure

Create a portable classic subnet in an IBM Cloud infrastructure account on your public or private VLAN and make it available to a cluster.

Portable public IP addresses are charged monthly.
Example:

ibmcloud oc ingress instance get --cluster my-cluster --name my-secrets-manager





 ibmcloud oc ingress instance ls 

Virtual Private Cloud

Classic infrastructure

List all Secrets Manager instances registered to a cluster.

ibmcloud oc ingress instance ls --cluster CLUSTER [--output OUTPUT] [-q] [--show-deleted]

Minimum required permissions
: Viewer platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

--c, --cluster CLUSTER
: Required. The name or ID of the cluster.

--output json
: Optional: Prints the command output in JSON format.

-q
: Optional: Do not show the message of the day or update reminders.

--show-deleted
: Optional. Add this option to include instances that were unregistered from the cluster.

Example:

ibmcloud oc ingress instance ls --cluster my-cluster --show-deleted





 ibmcloud oc ingress instance register 

Virtual Private Cloud

Classic infrastructure

Register a Secrets Manager instance to a cluster.

ibmcloud oc ingress instance register --cluster CLUSTER --crn CRN [--is-default] [--secret-group GROUP] [-q]

Minimum required permissions
: Administrator platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

--c, --cluster CLUSTER
: Required. The name or ID of the cluster.

--crn
: Required. The CRN of the IBM Cloud Secret Manager instance.

--is-default
: Optional. Include this option to also set the registered instance as the default Secrets Manager instance where all Ingress subdomain certificates are stored. If another instance is already set as default, it is removed. Note that you must manually update any certificates or secrets to upload them to the new default instance. Otherwise, they are uploaded at the next scheduled update time for the secret.

-q
List available flavors for a zone.

ibmcloud oc flavor ls --zone ZONE [--output OUTPUT] [--provider PROVIDER] [-q] [--show-storage]

Minimum required permissions
: None

Command options:

--zone ZONE
: The zone where you want to get flavor information for. To see available zones for classic clusters, run ibmcloud oc zone ls. To see available zones for VPC clusters, run ibmcloud oc zone ls --provider vpc-gen2 for Generation 2 compute.

--provider PROVIDER
: Optional: The infrastructure provider for which you want to get flavor information for. Available options are classic, vpc-classic and vpc-gen2.

--show-storage
: Optional: Show additional raw disks that are available for SDS worker node flavors. For more information, see [Software-defined storage (SDS) machines](https://cloud.ibm.com/docs/openshift?topic=openshift-planning_worker_nodessds).

--output json
: Optional: Prints the command output in JSON format.

-q
: Optional: Do not show the message of the day or update reminders.



 Example flavor ls command 

ibmcloud oc flavor ls --zone us-south-1 --provider vpc-gen2 --show-storage









 messages command 

Virtual Private Cloud

Classic infrastructure

View current messages from the IBM Cloud Kubernetes Service CLI plug-in for the IBMid user.

ibmcloud oc messages

Minimum required permissions
: None

Command options: None





 locations command 

Virtual Private Cloud

Classic infrastructure

List the locations that are supported by IBM Cloud Kubernetes Service. For more information about the locations that are returned, see [IBM Cloud Kubernetes Service locations](https://cloud.ibm.com/docs/openshift?topic=openshift-regions-and-zoneslocations).

ibmcloud oc locations [--output json]

Minimum required permissions
: None
Classic infrastructure

View information about Ingress secrets in your cluster, including secrets stored in IBM Cloud® Secrets Manager.

The previous alias for this command, ibmcloud ks ingress alb cert get, is deprecated. In CLI version 1.0.157 and later, the ibmcloud ks ingress alb cert category is deprecated, and these commands are now listed in the ibmcloud ks ingress secret subcategory. For more information, see the [CLI change log](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelog10).

ibmcloud ks ingress secret get --cluster CLUSTER --name SECRET_NAME --namespace NAMESPACE [--output json] [-q]

Minimum required permissions
: Administrator platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

-c, --cluster CLUSTER
: Required: The name or ID of the cluster.

--name SECRET_NAME
: Required: The name of the secret.

--namespace NAMESPACE
: Required: The namespace that the secret is deployed to.

--output json
: Optional: Prints the command output in JSON format.

-q
: Optional: Do not show the message of the day or update reminders.



 Example ingress secret get command 

ibmcloud ks ingress secret get --cluster my_cluster --name my_alb_secret --namespace demo_ns







 ibmcloud ks ingress secret ls 

Virtual Private Cloud

Classic infrastructure

List Ingress secrets in your cluster, including secrets stored in IBM Cloud® Secrets Manager.

The previous alias for this command, ibmcloud ks ingress alb cert ls, is deprecated.

ibmcloud ks ingress secret ls --cluster CLUSTER [--show-deleted] [--output json] [-q]

Minimum required permissions
: Administrator platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

-c, --cluster CLUSTER
: Required: The name or ID of the cluster.
: Optional: The ID of the account that contains the KMS instance you want to use for local disk or secret encryption.

--public-endpoint
: Optional: Specify this option to use the KMS public cloud service endpoint. If you don't include this option, the private cloud service endpoint is used by default.

-q
: Optional: Do not show the message of the day or update reminders.



 Example kms enable command 

ibmcloud ks kms enable -c mycluster --instance-id a11aa11a-bbb2-3333-d444-e5e555e5ee5 --crk 1a111a1a-bb22-3c3c-4d44-55e555e55e55







 ibmcloud ks kms instance ls 

Virtual Private Cloud

Classic infrastructure

List available [key management service (KMS) instances](https://cloud.ibm.com/docs/containers?topic=containers-encryptionkms) in your IBM Cloud account that you can choose to enable in your cluster.

ibmcloud ks kms instance ls [--output json] [-q]

Minimum required permissions
: Viewer platform access role in IBM Cloud Kubernetes Service

Command options:

--output json
: Optional: Prints the command output in JSON format.

-q
: Optional: Do not show the message of the day or update reminders.

Example:

ibmcloud ks kms instance ls







 quota commands 



 ibmcloud ks quota ls 

Virtual Private Cloud

Classic infrastructure

List all quota and limits for cluster-related resources in your IBM Cloud account.

ibmcloud ks quota ls [--provider PROVIDER] [--output json]

Minimum required permissions
: Viewer platform access role for IBM Cloud Kubernetes Service

Command options:

--provider (classic | vpc-gen2)
: The infrastructure provider type to list quota and limits for.

--output json
: Optional: Prints the command output in JSON format.

Example:

ibmcloud ks quota ls
kubectl config current-context

Example output

<cluster_name>/<cluster_ID>



2. Launch your Kubernetes dashboard with the default port 8001.



1. Set the proxy with the default port number.

kubectl proxy

Starting to serve on 127.0.0.1:8001
2. Open the following URL in a web browser to see the Kubernetes dashboard.

http://localhost:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/









 Accessing clusters through the private cloud service endpoint 

Allow authorized cluster users to access your [VPC](https://cloud.ibm.com/docs/containers?topic=containers-access_clustervpc_private_se) or [classic](https://cloud.ibm.com/docs/containers?topic=containers-access_clusteraccess_private_se) cluster through the private cloud service endpoint.



 Accessing VPC clusters through the private cloud service endpoint 

The Kubernetes master is accessible through the private cloud service endpoint if authorized cluster users are in your IBM Cloud private network or are connected to the private network, such as through a [VPC VPN connection](https://cloud.ibm.com/docs/vpc?topic=vpc-vpn-onprem-example). However, communication with the Kubernetes master over the private cloud service endpoint must go through the 166.X.X.X IP address range, which you must configure in your VPN gateway and connection setup.



1. Set up your IBM Cloud VPC VPN and connect to your private network through the VPN.



1. [Configure a VPN gateway on your local machine](https://cloud.ibm.com/docs/vpc?topic=vpc-vpn-onprem-example). For example, you might choose to set up strongSwan on your machine.
2.
Key Management Service 



 Resources Data sources 

 <br><br> * [ibm_kms_instance_policies](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/kms_instance_policies)<br> * [ibm_kms_key](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/kms_key)<br> * [ibm_kms_key_alias](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/kms_key_alias)<br> * [ibm_kms_key_policies](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/kms_key_policies)<br> * [ibm_kms_key_rings](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/kms_key_rings)<br> * [ibm_kms_key_with_policy_overrides](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/kms_key_with_policy_overrides)<br> * [ibm_kp_key](
* [Operating VMware Shared](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_vcd-ops-guide)
* [VMware Cloud Director](https://docs.vmware.com/en/VMware-Cloud-Director/10.4/VMware-Cloud-Director-Tenant-Portal-Guide/GUID-74C9E10D-9197-43B0-B469-126FFBCB5121.html)
* [Troubleshooting NSX Edge](https://docs.vmware.com/en/VMware-NSX-Data-Center-for-vSphere/6.4/com.vmware.nsx.troubleshooting.doc/GUID-E6CD6FAA-3DA7-4AD7-9577-EE121AA7E1E6.html)
* [Hints and tips for migrating workloads to IBM POWER9 processor-based systems](https://www.ibm.com/downloads/cas/39XWR7YM)
* [IBM i on Power - Performance FAQ](https://www.ibm.com/downloads/cas/QWXA9XKN)
* [IBM Power Systems Performance Report](https://www.ibm.com/downloads/cas/K90RQOW8)







 Lab services 

[IBM Systems Lab Services](https://www.ibm.com/it-infrastructure/services/lab-services) has service offerings available to assist you with resolving system, application, and database performance problems. Formal and informal training opportunities are also available where you can learn how to use performance tools and resolve issues on your own. If you need help with assessing the potential impact of a migration, benchmarking a system environment, or identifying ways to improve performance, contact [IBM Lab Services](mailto:ibmsls@us.ibm.com).
* [SAP Business One Platform Support Matrix](https://support.sap.com/en/offerings-programs/support-small-medium-enterprises/business-one.html)



For a list of Microsoft Windows Server versions supported for the following SAP Business One server platforms, see the [SAP Business One Platform Support Matrix](https://help.sap.com/doc/011000358700000032462013e/9.3/en-US/B1_Platform_Support_Matrix.pdf).

More information on SAP HANA versions can be found in [SAP Note 2058870 - SAP Business One, version for SAP HANA on public Infrastructure-as-a-Service (IaaS) platforms](https://launchpad.support.sap.com//notes/2058870) and [SAP Note 2586742 - Overview Note for SAP Business One 9.3 PL03, version for SAP HANA](https://launchpad.support.sap.com//notes/2586742).

The [SAP Business One community page](https://community.sap.com/topics/business-one) has links to blogs where community members share their experiences with implementing and running SAP Business One.



 SAP Business One upgrade guides 

SAP Business One offers you several upgrade options when a new release is available

For more information, see the [SAP Business One Upgrade Strategy](https://help.sap.com/doc/011000358700001396142012e/9.3/en-US/B1_Upgrade_Strategy.pdf) guide.

These options are available if you're using SAP HANA or Microsoft SQL. See the [SAP Business One upgrade patches and programs information](https://support.sap.com/en/offerings-programs/support-small-medium-enterprises/business-one/upgrades-patches.html) for more detail on upgrades, patches, and hot fixes.







 SAP Business One training information 

Training is available on the integration framework for SAP Business One. The self-paced, online course takes you through scenario design basics, the integration of SAP Business One, and integrating the SAP Business One database.
Cyber Recovery 

For more information about [Cyber Recovery](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-cr_overview), see the following topics:



*  [Planning for Cyber Recovery](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-cr_planning)
*  [Procedure to order Cyber Recovery instance](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-cr_orderinginstance-order-procedure)
*  [Expanding and contracting capacity for Cyber Recovery instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-cr_addingservers)
*  [Adding, viewing, and deleting services for Cyber Recovery instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-cr_addingservices)
*  [Viewing and deleting Cyber Recovery instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-cr_viewinginstances)
ibmcloud resource service-key (NAME | ID) [-g RESOURCE_GROUP] [--id]



 Command options 

NAME
: Name of the key

ID
: ID of the key

-g
: Resource group name

--id
: Display the ID of service key. This option is exclusive with '--output'.

-g RESOURCE_GROUP
: Resource group name





 Examples 

Show details of service keys my-service-key:

ibmcloud resource service-key my-service-key

Show details of service key with ID crn:v1:bluemix:public:cloudantnosqldb:us-south:a/537860630a5ba7115be954e8d5aa5689:cc2a6d6c-8f5e-4038-b975-b09b51d1d8dc:resource-key:9057f12e-fbf5-421d-8865-764422217a79:

ibmcloud resource service-key crn:v1:bluemix:public:cloudantnosqldb:us-south:a/537860630a5ba7115be954e8d5aa5689:cc2a6d6c-8f5e-4038-b975-b09b51d1d8dc:resource-key:9057f12e-fbf5-421d-8865-764422217a79







 ibmcloud resource service-key-create 

Create a service key.
IR-7 - Incident Response Assistance 



  Control requirements 

IR-7 - 0
:   The organization provides an incident response support resource, integral to the organizational incident response capability that offers advice and assistance to users of the information system for the handling and reporting of security incidents.





  NIST supplemental guidance 

Incident response support resources provided by organizations include, for example, help desks, assistance groups, and access to forensics services, when required.
This parameter is now specified in the run() method of the Sampler class.
* Required: False



* parameters - DEPRECATED



* Type: array
* Description: Parameters of the quantum circuits. This parameter is now specified in the run() method of the Sampler class.
* Required: False



* service - DEPRECATED:



* Type: object
* Description: Optional instance of the qiskit_ibm_runtime.QiskitRuntimeService class. Defaults to QiskitRuntimeService(), which tries to initialize your default saved account. This parameter can now be specified when you initialize a Session instance.
* Required: False



* options



* Type: dictionary or Options class
* Description: Runtime settings that control the execution environment.
* Required: False



* backend: Optional instance of qiskit_ibm_runtime.IBMBackend class or string name of backend. If not specified, the least busy backend is used. This parameter can now be specified when you initialize a Session instance.





* skip_transpilation - DEPRECATED:



* Description: Skip circuit transpilation. The default value is False. This parameter is now specified in the Optionstranspilation setting: options = Options(transpilation={"skip_transpilation": True}).
* Required: False.











 Example 

from qiskit.test.reference_circuits import ReferenceCircuits
from qiskit_ibm_runtime import QiskitRuntimeService, Session, Sampler

service = QiskitRuntimeService(channel="ibm_cloud")
bell = ReferenceCircuits.bell()

with Session(service) as session:
sampler = Sampler(session=session)
sampler.options.resilience_level = 1

job = sampler.run(bell)
print(f"Job ID: {job.job_id()}")
print(f"Job result: {job.result()}")





 Next steps
</xsd:element>
<xsd:element name="jdbc">
<xsd:annotation>
<xsd:documentation>Defines jdbc connection parameters.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="jdbcUrl" type="xsd:string"/>
<xsd:element name="driverClassName" type="xsd:string" minOccurs="0"/>
<xsd:element name="connectionProperties" type="xsd:string" minOccurs="0"/>
<xsd:element name="catalog" type="xsd:string" minOccurs="0"/>
<xsd:element name="schema" type="xsd:string" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="srcUrl">
<xsd:annotation>
<xsd:documentation>Defines URI source parameters.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="sourceUrl" type="xsd:string"/>
<xsd:element name="mimeType" type="mimeType"/>
<xsd:element name="property" type="propertyType" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="table">
<xsd:annotation>
<xsd:documentation>Represents a table.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
'exampleParameter': 'exampleValue'
}
resource_key = resource_controller_service.create_resource_key(
name=key_name,
source=instance_guid,
parameters=parameters
).get_result()

print('ncreate_resource_key() response:n',
json.dumps(resource_key, indent=2))

createResourceKeyOptions := resourceControllerService.NewCreateResourceKeyOptions(
keyName,
instanceGUID,
)

parameters := &resourcecontrollerv2.ResourceKeyPostParameters{}
parameters.SetProperty("exampleParameter", "exampleValue")
createResourceKeyOptions.SetParameters(parameters)

resourceKey, response, err := resourceControllerService.CreateResourceKey(createResourceKeyOptions)
if err != nil {
panic(err)
}
b, _ := json.MarshalIndent(resourceKey, "", " ")
fmt.Printf("nCreateResourceKey() response:n%sn", string(b))

const parameters = {
'exampleParameter': 'exampleValue'
};

const params = {
name: keyName,
source: instanceGuid,
parameters: parameters,
};

resourceControllerService.createResourceKey(params)
.then(res => {
instanceKeyGuid = res.result.guid;
console.log('createResourceKey() response:n' + JSON.stringify(res.result, null, 2));
})
.catch(err => {
console.warn(err)
});





 Adding a credential when binding an IAM-enabled service by using Terraform
"instance": "Composer-qp",
"credentials": "Credentials-1"
},
}
}
],
}

In this example, the credentials for the composer service, along with any other credentials for other service types belong to a parameter called __bx_creds. The action code can access the necessary information by getting the __bx_creds parameter.



For more information about passing parameters to an action or package, see [Binding parameters to actions](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-actionsactions_params).





 Unbinding services from actions 

Unbinding a service from an action or package removes existing service bindings.

ibmcloud fn service unbind SERVICE_NAME ACTION_NAME
The parameter directs the service to split the transcript into multiple final results based on semantic features of the input, such as at the conclusion of sentences. The service bases its understanding of semantic features on the base language model that you use with a request. Custom language models and grammars can also influence how and where the service splits a transcript.

The parameter causes the service to add an end_of_utterance field to each final result to indicate the motivation for the split: full_stop, silence, end_of_data, or reset.

For more information, see [Split transcript at phrase end](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-parsingsplit-transcript).

Improved speaker_labels parameter
: For speech recognition, the speaker_labels parameter has been updated to improve the identification of individual speakers for further analysis of your audio sample. For more information about the speaker labels feature, see [Speaker labels](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-speaker-labels). For more information about the improvements to the feature, see [IBM Research AI Advances Speaker Diarization in Real Use Cases](https://www.ibm.com/blogs/research/2020/07/speaker-diarization-in-real-use-cases/).





 27 November 2019 (Version 1.1.2) 

Version 1.1.2 is available
: Speech to Text for IBM Cloud Pak for Data version 1.1.2 is now available.

Maximum number of custom models
: You can create no more than 1024 custom language models and no more than 1024 custom acoustic models per owning credentials. For more information, see [Maximum number of custom models](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-customizationcustomMaximum).





 30 August 2019 (Version 1.0.1) 

Version 1.0.1 is available
: Speech to Text for IBM Cloud Pak for Data version 1.0.1 is now available. The service now works with IBM Cloud Pak for Data 2.1.0.1.