vania-janet/multiturn-rag-retrieval-data huggingface dataset:
You can find your worker node names by running oc get nodes. false N/A 
 Upgrade odf-upgrade Config If you are upgrading an existing ODF installation, set to true. true false 
 Billing type billing-type Config The billing type you want to use. Choose from essentials or advanced. true advanced 
 IBM COS endpoint ibm-cos-endpoint Config The IBM COS regional public endpoint. false N/A 
 IBM COS location constraint ibm-cos-location Config The location constraint that you want to use when creating your bucket. For example us-east-standard. false N/A 
 Access key ID ibm-cos-access-key Secret Your IBM COS HMAC access key ID . false N/A 
 Secret access key ibm-cos-secret-key Secret Your IBM COS HMAC secret access key. false N/A 
 Encryption enabled cluster-encryption Config Set to true if you want to enable cluster-wide encryption. true false 
 IAM API key iam-api-key Secret Your IAM API key. true N/A 
 Perform Cleanup perform-cleanup Config Set to true if you want to perform complete cleanup of ODF on assignment deletion true false 







 4.10 parameter reference 



Table 2. 4.10 parameter reference

 Display name CLI option Type Description Required? Default value 

 OSD pod volume size osd-size Config The OSD storage size in Gi. The default value is 100Gi. true 100Gi 
 OSD pod storage class osd-storage-class Config The storage class to use when dynamically provisioning volumes for the OSD pods. true N/A 
 Number of OSD volumes num-of-osd Config The number of storage device replicas to create. The default value is 1, which creates 1 device across 3 nodes. Increase by 1 for each additional set of 3 devices. For must use cases, leave the default value of 1. true 1 
 Worker node names worker-nodes Config A comma separated list of the worker node names where you want to deploy ODF.
The following example shows four checks, the zonecheck.json, regioncheck.json, defaultcheck.json, and a check template. You can use these example checks to define rules for worker nodes in a specific zone (zonecheck.json), region (regioncheck.json), or for all worker nodes that don't match any of the checks that you defined in the config map (defaultcheck.json). Use the check template to create your own check. For every check, to identify a worker node, you must choose one of the worker node labels that you retrieved in the previous step.

For every check, you can set only one value for NodeSelectorKey and NodeSelectorValue. If you want to set rules for more than one region, zone, or other worker node labels, create a new check. Define up to 15 checks in a config map. If you add more checks, only 1 worker node will be reloaded at a time until all workers requested are updated.

Example

apiVersion: v1
kind: ConfigMap
metadata:
name: ibm-cluster-update-configuration
namespace: kube-system
data:
drain_timeout_seconds: "120"
zonecheck.json: 
{
"MaxUnavailablePercentage": 30,
"NodeSelectorKey": "failure-domain.beta.kubernetes.io/zone",
"NodeSelectorValue": "dal13"
}
regioncheck.json: 
{
"MaxUnavailablePercentage": 20,
"NodeSelectorKey": "failure-domain.beta.kubernetes.io/region",
"NodeSelectorValue": "us-south"
}
defaultcheck.json: 
{
"MaxUnavailablePercentage": 20
}
<check_name>: 
{
"MaxUnavailablePercentage": <value_in_percentage>,
You can monitor the provisioning process in the Status column of your CLI output. If your worker node is stuck in this state for a long time, check whether a problem occurred during the provisioning.





 Provision pending state 

You can view the current worker node state by running the ibmcloud oc worker ls --cluster <cluster_name_or_ID> command and locating the State and Status fields.

A Provision pending state means that another process is completing before the worker node provisioning process starts. You can monitor the other process that must complete first in the Status column of your CLI output. For example, in VPC clusters, the Pending security group creation indicates that the security group for your worker nodes is creating first before the worker nodes can be provisioned. If your worker node is stuck in this state for a long time, check whether a problem occurred during the other process.





 Provision_failed state 

You can view the current worker node state by running the ibmcloud oc worker ls --cluster <cluster_name_or_ID> command and locating the State and Status fields.

Your worker node could not be provisioned. List the details for the worker node to find the details for the failure by running ibmcloud oc worker get --cluster <cluster_name_or_id> --worker <worker_node_id>.





 Reloading state 

You can view the current worker node state by running the ibmcloud oc worker ls --cluster <cluster_name_or_ID> command and locating the State and Status fields.

A Reloading state means that your worker node is being reloaded and is not available in the cluster. You can monitor the reloading process in the Status column of your CLI output. If your worker node is stuck in this state for a long time, check whether a problem occurred during the reloading.





 Reloading_failed state 

You can view the current worker node state by running the ibmcloud oc worker ls --cluster <cluster_name_or_ID> command and locating the State and Status fields.

A Reloading_failed state means that your worker node could not be reloaded.
Run [job logs](https://cloud.ibm.com/apidocs/schematics/schematicsget-job) to pull your workspace logs.

curl -X GET https://schematics.cloud.ibm.com/v1/workspaces/workspaces/{w_id}/runtime_data/{template_id}/log_store -H 'authorization: <auth>' -H 'cache-control: no-cache' -H 'content-type: application/json'
7. Review the output to view the [Agent service workspace](https://cloud.ibm.com/docs/schematics?topic=schematics-agents-setupagents-svc-output) execution.









 Next steps 

You have completed the Schematics Agent set up.



* Now, you need to [Connect your Agent](https://cloud.ibm.com/docs/schematics?topic=schematics-register-agent) with your Schematics service instance.
* For any challenges in Agents installation or configuration, see [FAQ about Agent](https://cloud.ibm.com/docs/schematics?topic=schematics-faqs-agent&interface=cli) and [Troubleshooting guide](https://cloud.ibm.com/docs/schematics?topic=schematics-agent-crn-not-found&interface=cli).
vpn_peer_cidrs Comma-separated list of peer CIDRs (for example, 192.168.0.0/24) to which the VPN will be connected. No NOT_SET 
 vpn_preshared_key The pre-shared key for the VPN. No NOT_SET 
 worker_node_instance_type Specify the virtual server instance profile type to be used to create the worker nodes for the Spectrum LSF cluster. The worker nodes are the ones where the workload execution takes place and the choice should be made according to the characteristics of the workloads. For choices on profile types, see [Instance profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-profiles). Note: If dedicated_host_enabled == true, the available instance prefix (for example, bx2 and cx2) can be limited depending on your target region. Check ibmcloud target -r {region_name}; ibmcloud is dedicated-host-profiles. No bx2-4x16 
 worker_node_max_count The maximum number of worker nodes that can be deployed in the Spectrum LSF cluster. In order to use the [Resource Connector](https://www.ibm.com/docs/en/spectrum-lsf/10.1.0?topic=lsf-resource-connnector) feature to dynamically create and delete worker nodes based on workload demand, the value that is selected for this parameter must be larger than worker_node_min_count. If you plan to deploy only static worker nodes in the LSF cluster, for example, when you use Spectrum Scale storage, the value for this parameter should be equal to worker_node_min_count. Enter a value in the range 1 - 500. No 10 
 worker_node_min_count The minimum number of worker nodes. This is the number of static worker nodes that will be provisioned at the time the cluster is created. If using NFS storage, enter a value in the range 0 - 500. If using Spectrum Scale storage, enter a value in the range 1 - 64.
Change log for worker node fix pack 1.17.17_1555, released 1 March 2021 

The following table shows the changes that are in the worker node fix pack 1.17.17_1555. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node.



Changes since version 1.17.17_1553

 Component Previous Current Description 

 Ubuntu 18.04 packages 4.15.0-135-generic 4.15.0-136-generic Updated worker node image with package updates for [CVE-2020-27619](https://nvd.nist.gov/vuln/detail/CVE-2020-27619), [CVE-2020-29372](https://nvd.nist.gov/vuln/detail/CVE-2020-29372), [CVE-2020-29374](https://nvd.nist.gov/vuln/detail/CVE-2020-29374), [CVE-2020-8625](https://nvd.nist.gov/vuln/detail/CVE-2020-8625), [CVE-2021-23840](https://nvd.nist.gov/vuln/detail/CVE-2021-23840), [CVE-2021-23841](https://nvd.nist.gov/vuln/detail/CVE-2021-23841), [CVE-2021-26937](https://nvd.nist.gov/vuln/detail/CVE-2021-26937), [CVE-2021-27212](https://nvd.nist.gov/vuln/detail/CVE-2021-27212), and [CVE-2021-3177](https://nvd.nist.gov/vuln/detail/CVE-2021-3177).
ibmcloud ks worker update --cluster CLUSTER --worker WORKER-NODE-1-ID --worker WORKER-NODE-2-ID
8. Optional: Verify the events that are triggered by the config map and any validation errors that occur. The events can be reviewed in the Events section of your CLI output.

kubectl describe -n kube-system cm ibm-cluster-update-configuration
9. Confirm that the update is complete by reviewing the Kubernetes version of your worker nodes.

kubectl get nodes
10. Verify that you don't have duplicate worker nodes. Sometimes, older clusters might list duplicate worker nodes with a NotReady status after an update. To remove duplicates, see [troubleshooting](https://cloud.ibm.com/docs/containers?topic=containers-cs_duplicate_nodes).



Next steps:



* Repeat the update process with other worker pools.
* Inform developers who work in the cluster to update their kubectl CLI to the version of the Kubernetes master.
* If the Kubernetes dashboard does not display utilization graphs, [delete the kube-dashboard pod](https://cloud.ibm.com/docs/containers?topic=containers-cs_dashboard_graphs).







 Updating classic worker nodes in the console 

After you set up the config map for the first time, you can then update worker nodes by using the IBM Cloud console.

To update worker nodes from the console:



1. Complete the [prerequisite steps](https://cloud.ibm.com/docs/containers?topic=containers-updateworker-up-prereqs) and [set up a config map](https://cloud.ibm.com/docs/containers?topic=containers-updateworker_node) to control how your worker nodes are updated.
2. From the [IBM Cloud console](https://cloud.ibm.com/) menu !
[Create your cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-clusters) with the worker pool flavor and number of worker nodes that you [previously estimated](https://cloud.ibm.com/docs/openshift?topic=openshift-strategysizing_workers).
2. Review what compute resources your cluster uses by default and calculate the remaining cluster capacity that you can use for your workloads.



1. With the IBM Cloud IAM Manager service access role for the cluster in all namespaces: [Access your Red Hat OpenShift cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-access_cluster).
2. Find the CPU and memory usage across all worker nodes. From the [Red Hat OpenShift clusters console](https://cloud.ibm.com/kubernetes/clusters?platformType=openshift), you can also click your cluster and review the Cluster Insights card.

oc top nodes

Example output

NAME CPU(cores) CPU% MEMORY(bytes) MEMORY%
10.xxx.xx.xxx 149m 7% 2402Mi 84%
10.xxx.xx.xxx 122m 6% 2395Mi 83%
10.xxx.xx.xxx 144m 7% 2376Mi 83%
3. Add the CPU and memory usage amounts to the [worker node resource reserves](https://cloud.ibm.com/docs/openshift?topic=openshift-planning_worker_nodesresource_limit_node) that are set for each worker node by default.
4. Subtract the worker node reserved and default app usage amounts from the total worker node size. This amount represents the total compute resources of your worker nodes before you deploy any apps or other workloads.



3.
If the previous steps do not solve the issue, [reload](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-cli&interface=uics_worker_reload) or [replace](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-cli&interface=uicli_worker_replace) the affected workers one at a time.







 If all worker nodes in a single zone, subnet, or VLAN are affected 

If all worker nodes in a single zone, subnet, or VLAN are in a Critical or NotReady state, but all other worker nodes in the cluster are functioning normally, there might be an issue with a networking component. Follow the steps in [If all worker nodes in a cluster are affected](https://cloud.ibm.com/docs/openshift?topic=openshift-ts-critical-notreadyts-critical-notready-steps-all), especially to the steps regarding any networking components that may affect the zone, subnet or VLAN, such as firewall or gateway rules, ACLs or custom routes, or Calico and Kubernetes network policies.

If you checked your networking components and still cannot resolve the issue, [gather your worker node data](https://cloud.ibm.com/docs/openshift?topic=openshift-ts-critical-notreadyts-critical-notready-gather) and open a support ticket.





 If all worker nodes in a cluster are affected 

If all the worker nodes in your cluster show Criticalor NotReady at the same time, there might be a problem with either the cluster apiserver or the networking path between the workers and the apiserver. Follow these troubleshooting steps to determine the cause and resolve the issue.

Some steps are specific to a specialized area, such as networking or automation. Consult with the relevant administrator or team in your organization before completing these steps.



1. Check if there were any recent changes to your cluster, environment, or account that might impact your worker nodes. If so, revert the changes and then check the worker node status to determine if the changes caused the issue.
If applicable, target the appropriate resource group. Set the context for your cluster.](https://cloud.ibm.com/docs/containers?topic=containers-access_cluster)



1. Retrieve the following details of your VPC instance. These parameters are used to apply labels to your worker nodes.



* <instanceID> - The VPC instance ID. To retrieve this value, run ibmcloud is ins.
* <node-name> - The names of the worker nodes. To retrieve this value, run kubectl get nodes.
* <region-of-instanceID> and <zone-of-instanceID> - The region and zone that your VPC instance is in. To retrieve these values, run ibmcloud is in <instanceID>. Example region value: eu-de. Example zone value: eu-de-1.



2. Copy the following shell script and save it to a file on your local machine called setup.sh

!/bin/bash

function help()
{
echo "Run the script in the following format..."
echo "./setup.sh <node-name> <instanceID> <region-of-instanceID> <zone-of-instanceID>"
exit 1
}

function apply_labels()
{
kubectl label nodes $1 "ibm-cloud.kubernetes.io/worker-id"=$2
kubectl label nodes $1 "failure-domain.beta.kubernetes.io/region"=$3
kubectl label nodes $1 "failure-domain.beta.kubernetes.io/zone"=$4
kubectl label nodes $1 "topology.kubernetes.io/region"=$3
kubectl label nodes $1 "topology.kubernetes.io/zone"=$4
}

function verify_node()
{
kubectl get nodes | grep $1
if (( $? == 0 ))
then
return 0
else
return 1
chmod 400 /.ssh/id_rsa_worker_private
4. Use the private key to SSH into the worker node that you found in step 2.

ssh -i /.ssh/id_rsa_worker_private root@<WORKER_PRIVATE_IP>







 Public network classic clusters that are connected to a public VLAN only 

Debug classic clusters that are connected to a public VLAN by logging in to your worker nodes.



1. [Install and configure the Calico CLI, and set the context for your cluster to run Calico commands](https://cloud.ibm.com/docs/containers?topic=containers-network_policiescli_install).
2. Create a Calico global network policy that is named ssh-open to allow inbound SSH traffic on port 22.

calicoctl apply [-c <path_to_calicoctl_cfg>/calicoctl.cfg] -f - <<EOF
apiVersion: projectcalico.org/v3
kind: GlobalNetworkPolicy
metadata:
name: ssh-open
spec:
selector: ibm.role == 'worker_public'
ingress:
- action: Allow
protocol: TCP
destination:
ports:
- 22
- action: Allow
protocol: UDP
destination:
ports:
- 22
order: 1500
EOF
Show more
3. Get the public IP address of your worker node.

kubectl get nodes -o wide
4. SSH into the worker node via its public IP address.

ssh root@<WORKER_PUBLIC_IP>
5. Run debug commands to help you gather information and troubleshoot issues, such as ip, ifconfig, nc, tcpdump, ping, ps, and curl. You can also install other tools, such as mtr, by running yum install <tool>.







 Cleaning up after debugging 

After you finish debugging, clean up resources to disable SSH access.
Don't specify this parameter if you want to use all the worker nodes in your cluster. To retrieve your worker node name, run the oc get nodes command. N/A 
 clusterEncryption Available for add-on version 4.7.0 and later. Enter true or false to enable encryption. 
 autoDiscoverDevices Optional: Automatically discover the available disks on your worker nodes. Enter true or false. 
 hpcsServiceName Enter the name of your Hyper Protect Crypto Services instance. For example: Hyper-Protect-Crypto-Services-eugb. false 
 hpcsInstanceId Enter your Hyper Protect Crypto Services instance ID. For example: d11a1a43-aa0a-40a3-aaa9-5aaa63147aaa. false 
 hpcsSecretName Enter the name of the secret that you created by using your Hyper Protect Crypto Services credentials. For example: ibm-hpcs-secret. false 
 hpcsBaseUrl Enter the public or private endpoint of your Hyper Protect Crypto Services instance. For example: https://api.eu-gb.hs-crypto.cloud.ibm.com:8389. false 
 hpcsTokenUrl Enter https://iam.cloud.ibm.com/identity/token. false 
 ignore-noobaa Enter true if you do not want to deploy MultiCloud Object Gateway. false 







 Version 4.9 parameters 



Classic parameter reference for 4.9

 Parameter Description Default value 

 name Note that Kubernetes resource names can't contain capital letters or special characters. Enter a name for your resource that uses only lowercase letters, numbers, - or . N/A 
 osdStorageClassName Enter localblock. N/A 
 osdSize Enter a size for your storage devices. Example: 100Gi. The total storage capacity of your ODF cluster is equivalent to the osdSize multiplied by the numOfOsd. N/A 
 osdDevicePaths Enter a comma separated list of the device paths for the devices that you want to use for the OSD devices.
Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node.



Changes since version 1.24.9_1548

 Component Previous Current Description 

 Ubuntu 18.04 packages N/A N/A N/A 
 Ubuntu 20.04 packages N/A N/A N/A 
 Kubernetes N/A N/A N/A 







 Change log for worker node fix pack 1.24.9_1548, released 19 December 2022 

The following table shows the changes that are in the worker node fix pack 1.24.9_1548. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node.



Changes since version 1.24.8_1546

 Component Previous Current Description 

 Containerd 1.6.10 1.6.12 See the [1.6.12 change log](https://github.com/containerd/containerd/releases/tag/v1.6.12), the [1.6.11 change log](https://github.com/containerd/containerd/releases/tag/v1.6.11), and the security bulletin for [CVE-2022-23471](https://www.ibm.com/support/pages/node/6850799).
Change log for worker node fix pack 1.17.17_1564, released 24 May 2021 

The following table shows the changes that are in the worker node fix pack 1.17.17_1564. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node.



Changes since version 1.17.17_1562

 Component Previous Current Description 

 HA proxy e0fa2f 26c5cc Updated image with fixes for [CVE-2020-26116](https://nvd.nist.gov/vuln/detail/CVE-2020-26116), [CVE-2020-27619](https://nvd.nist.gov/vuln/detail/CVE-2020-27619), [CVE-2021-23336](https://nvd.nist.gov/vuln/detail/CVE-2021-23336), [CVE-2021-3177](https://nvd.nist.gov/vuln/detail/CVE-2021-3177), [CVE-2019-3842](https://nvd.nist.gov/vuln/detail/CVE-2019-3842), [CVE-2020-13776](https://nvd.nist.gov/vuln/detail/CVE-2020-13776), [CVE-2019-18276](https://nvd.nist.gov/vuln/detail/CVE-2019-18276), [CVE-
(https://cloud.ibm.com/docs/containers?topic=containers-faqssmallest_cluster).
* Include the --label option to automatically label worker nodes that are in the pool with the label key=value.
* If you provision a bare metal or dedicated VM worker pool, specify --hardware dedicated.
* The new worker nodes run the same major.minor version as the cluster master, but the latest worker node patch of that major.minor version.



ibmcloud ks worker-pool create classic --name <pool_name> --cluster <cluster_name_or_ID> --flavor <flavor> --size-per-zone <number_of_workers_per_zone_min_1> [--operating-system UBUNTU_20_64|UBUNTU_18_64] [--label key=value]
5. Verify that the worker pool is created.

ibmcloud ks worker-pool ls --cluster <cluster_name_or_ID>
6. By default, adding a worker pool creates a pool with no zones. To deploy worker nodes in a zone, you must add the zones that you previously retrieved to the worker pool. If you want to spread your worker nodes across multiple zones, repeat this command for each zone.

ibmcloud ks zone add classic --zone <zone> --cluster <cluster_name_or_ID> --worker-pool <pool_name> --private-vlan <private_VLAN_ID> --public-vlan <public_VLAN_ID>
7. Verify that worker nodes provision in the zone that you added. Your worker nodes are ready when the status changes from provision_pending to normal.

ibmcloud ks worker ls --cluster <cluster_name_or_ID> --worker-pool <pool_name>

Example output

ID Public IP Private IP Machine Type State Status Zone Version
kubectl apply -f enable-ssh.yaml
5. Use the private or public network to access the worker node by using your SSH key.





 Private network 

Create a new or choose an existing server instance that has access to the same private network as the worker node. For VPC clusters, the [virtual server instance](https://cloud.ibm.com/vpc-ext/compute/vs) must exist in the same VPC as the worker node.

For classic clusters, the [device](https://cloud.ibm.com/gen1/infrastructure/devices) can access the worker node from any private VLAN if a [Virtual Router Function (VRF)](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpointvrf) or [VLAN spanning](https://cloud.ibm.com/docs/vlans?topic=vlans-vlan-spanningvlan-spanning) is enabled. Otherwise, the device must exist on the same private VLAN as the worker node.



1. Copy your SSH private key from step 1 from your local machine to this server instance.

scp <SSH_private_key_location> <user@host>:/.ssh/id_rsa_worker_private
2. SSH into the server instance.
3. Set the correct permissions for using the SSH private key that you copied.

chmod 400 /.ssh/id_rsa_worker_private
4. Use the private key to SSH into the worker node that you found in step 2.

ssh -i /.ssh/id_rsa_worker_private root@<WORKER_PRIVATE_IP>







 Public network classic clusters that are connected to a public VLAN only 

Debug classic clusters that are connected to a public VLAN by logging in to your worker nodes.



1.