vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* [Verifying that the storage driver and plug-in pods show a status of Running](https://cloud.ibm.com/docs/containers?topic=containers-debug_storageverify_driver_pod_running_status)
* [Checking whether your PVC is successfully provisioned.](https://cloud.ibm.com/docs/containers?topic=containers-debug_storagecheck_pvc_provision)
* [Portworx](https://cloud.ibm.com/docs/containers?topic=containers-debug_storagets-portworx-helm)
* [OpenShift Data Foundation](https://cloud.ibm.com/docs/containers?topic=containers-debug_storagets-ocs-debug)



[Debugging IBM Cloud File Storage for Classic failures](https://cloud.ibm.com/docs/containers?topic=containers-debug_storage_filedebug_storage_file)



* [Checking whether the pod that mounts your storage instance is successfully deployed](https://cloud.ibm.com/docs/containers?topic=containers-debug_storage_filedebug_storage_file_deploy)
* [Restarting your app pod](https://cloud.ibm.com/docs/containers?topic=containers-debug_storage_filedebug_storage_file_restart)
* [Verifying that the storage driver and plug-in pods show a status of Running](https://cloud.ibm.com/docs/containers?topic=containers-debug_storage_filedebug_storage_file_driver_plugin)
* [Checking whether your PVC is successfully provisioned.](https://cloud.ibm.com/docs/containers?topic=containers-debug_storage_filedebug_storage_file_pvc)
* [Checking and updating the kubectl CLI version](https://cloud.ibm.com/docs/containers?topic=containers-debug_storage_filedebug_storage_file_cli)
2.29 icr.io/continuous-delivery/pipeline/pipeline-base-image:2.29 sha256:9454cc4fc70a21a1f5b59ede38910b30d29db69e5331e9e37a4d3516427ce66d 
 2.28 icr.io/continuous-delivery/pipeline/pipeline-base-image:2.28 sha256:5ce2b19d67e1e05bc70b0f5639ea7e7696cfac37aea62e9f2e75249f54d97c08 
 2.27 icr.io/continuous-delivery/pipeline/pipeline-base-image:2.27 sha256:e212bfbfa48f88f7b12ac77aa21fdc41d8eccf9ff89a2405706430738d09e24b 
 2.26 icr.io/continuous-delivery/pipeline/pipeline-base-image:2.26 sha256:31bd71102552d6d76b6660c4ca2cbae930367ff3d644acc0673e861085a23b12 
 2.25 icr.io/continuous-delivery/pipeline/pipeline-base-image:2.25 sha256:31f01a325fcb53651742fbb4af1d9a3ec425fc9b2662e1894c01389ff37426bf 
 2.24 icr.io/continuous-delivery/pipeline/pipeline-base-image:2.24 sha256:a97c10d27cdf8ee543cad4b29980ccdd5a697164f40ade7f399a0b7a3619f2ea
Example command to create a version 4.12 configuration.

ibmcloud sat storage config create --location LOCATION --name NAME --template-name odf-remote --template-version 4.12 --param "osd-size=OSD-SIZE" --param "osd-storage-class=OSD-STORAGE-CLASS" --param "num-of-osd=NUM-OF-OSD" [--param "worker-nodes=WORKER-NODES"] --param "odf-upgrade=ODF-UPGRADE" --param "billing-type=BILLING-TYPE" [--param "ibm-cos-endpoint=IBM-COS-ENDPOINT"] [--param "ibm-cos-location=IBM-COS-LOCATION"] [--param "ibm-cos-access-key=IBM-COS-ACCESS-KEY"] [--param "ibm-cos-secret-key=IBM-COS-SECRET-KEY"] --param "cluster-encryption=CLUSTER-ENCRYPTION" --param "iam-api-key=IAM-API-KEY" --param "perform-cleanup=PERFORM-CLEANUP" --param "kms-encryption=KMS-ENCRYPTION" [--param "kms-instance-name=KMS-INSTANCE-NAME"] [--param "kms-instance-id=KMS-INSTANCE-ID"] [--param "kms-base-url=KMS-BASE-URL"] [--param "kms-token-url=KMS-TOKEN-URL"] [--param "kms-root-key=KMS-ROOT-KEY"] [--param "kms-api-key=KMS-API-KEY"] --param "ignore-noobaa=IGNORE-NOOBAA"
6. Customize the command based on the settings that you want to use.
7. Run the command to create a configuration.
8. Verify your configuration was created.
[Building a high availability Certificate Authority (CA)](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-build-ha-caibp-console-build-ha-ca)



* [Configuring CA replica sets](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-build-ha-caibp-console-build-ha-ca-replica-sets)



* [Deploying a PostgreSQL database](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-build-ha-caibp-console-build-ha-ca-postgresql)



* [Considerations](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-build-ha-caibp-console-build-ha-ca-considerations)
* [Before you begin](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-build-ha-caibp-console-build-ha-ca-before)
* [ Creating the PostgreSQL connection file](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-build-ha-caibp-console-build-ha-ca-connx)
* [Creating an HA CA](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-build-ha-caibp-console-build-ha-ca-create)







 Data residency 

[Data residency](https://cloud.ibm.com/docs/blockchain?topic=blockchain-console-icp-about-data-residencyconsole-icp-about-data-residency)
"crn": "crn:v1:staging:public:is:us-south:a/123456::load-balancer:dd754295-e9e0-4c9d-bf6c-58fbc59e5727",
"hostname": "ac34687d.lb.appdomain.cloud",
"href": "https://us-south.iaas.cloud.ibm.com/v1/load_balancers/dd754295-e9e0-4c9d-bf6c-58fbc59e5727",
"id": "0738-dd754295-e9e0-4c9d-bf6c-58fbc59e5727",
"is_public": true,
"profile": {
"name": "network-fixed",
"family": "network"
},
"listeners": [
{
"id": "0738-70294e14-4e61-11e8-bcf4-0242ac110004",
"href": "https://us-south.iaas.cloud.ibm.com/v1/load_balancers/dd754295-e9e0-4c9d-bf6c-58fbc59e5727/listeners/70294e14-4e61-11e8-bcf4-0242ac110004"
}
],
"name": "example-balancer",
"operating_status": "offline",
"pools": [
{
"id": "0738-70294e14-4e61-11e8-bcf4-0242ac110004",
* [Using the Watson Assistant package](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_watson_assistantusage_conversation)



[Natural Language Classifier](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_natlang_classifierpkg_natlang_classifier)



* [Creating a Natural Language Classifier service instance](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_natlang_classifierservice_instance_classifier)
* [Installing the Natural Language Classifier package](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_natlang_classifierinstall_classifier)



* [Installing from the Cloud Functions CLI](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_natlang_classifiernlclassifier_cli)
* [Installing from the Cloud Functions console](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_natlang_classifiernlclassifier_ui)



* [Using the Natural Language Classifier package](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_natlang_classifierusage_classifier)



[Natural Language Understanding](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_natlang_understandingpkg_natlang_understanding)



* [Creating a Natural Language Understanding service instance](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_natlang_understandingservice_instance_understanding)
2.38 icr.io/continuous-delivery/pipeline/pipeline-base-image:2.38 sha256:2f11f01c9710ec711a17a9269be04f584e173c89b27b116c27ec93ec31981c07 
 2.37 icr.io/continuous-delivery/pipeline/pipeline-base-image:2.37 sha256:229503f75f9837a1fd0e8d38918d8904d3719eaeae84e8aaf94201e8409d78fd 
 2.36 icr.io/continuous-delivery/pipeline/pipeline-base-image:2.36 sha256:caf29e1e2ce8e1df165c4eb7a3124ae17b6438e2b04b8766dd0dfad502a79350 
 2.35 icr.io/continuous-delivery/pipeline/pipeline-base-image:2.35 sha256:f78e02d91386dbd9a2e1fb9686df130c36666ae67cfc0bc483f1f4ee34cdf9e2 
 2.33 icr.io/continuous-delivery/pipeline/pipeline-base-image:2.33 sha256:dc3a6d2a352b0019f8ce7ea4c10afd4017e45c48cb22ca692ab0b02b028538cc 
 2.32 icr.io/continuous-delivery/pipeline/pipeline-base-image:2.32 sha256:e66e380e37ad1f84891fbc9c708b7685356987895f2c397c20db0a5fae1efbed
Example request to create a version 4.10 configuration.

curl -X POST "https://containers.cloud.ibm.com/global/v2/storage/satellite/createStorageConfigurationByController" -H "accept: application/json" -H "Authorization: TOKEN" -H "Content-Type: application/json" -d "{ "config-name": "string", "controller": "string", "storage-class-parameters": [ { "additionalProp1": "string", "additionalProp2": "string", "additionalProp3": "string" } ], "storage-template-name": "local-volume-file", "storage-template-version": "4.10", "update-assignments": true, "user-config-parameters": { "entry.name": "AUTO-DISCOVER-DEVICES", { "entry.name": "LABEL-KEY", { "entry.name": "LABEL-VALUE", { "entry.name": "DEVICEPATH", { "entry.name": "FSTYPE","user-secret-parameters": }

Example request to create a version 4.11 configuration.
* [Binding a service instance to a Code Engine app, job, or function with the CLI](https://cloud.ibm.com/docs/codeengine?topic=codeengine-bind-servicesbind-cli)



* [Binding a service instance with a new credential](https://cloud.ibm.com/docs/codeengine?topic=codeengine-bind-servicesbind-credentials)
* [Binding a service instance with a specific role](https://cloud.ibm.com/docs/codeengine?topic=codeengine-bind-servicesbind-credentials-role)
* [Binding a service instance with existing credentials](https://cloud.ibm.com/docs/codeengine?topic=codeengine-bind-servicesbind-existing-credentials)



* [Unbinding service instances](https://cloud.ibm.com/docs/codeengine?topic=codeengine-bind-servicesunbind)



* [Unbinding a service instance from the console](https://cloud.ibm.com/docs/codeengine?topic=codeengine-bind-servicesunbind-ui)
* [Unbinding a service instance with the CLI](https://cloud.ibm.com/docs/codeengine?topic=codeengine-bind-servicesunbind-cli)









 Accessing container registries 

[Accessing container registries](https://cloud.ibm.com/docs/codeengine?topic=codeengine-add-registryadd-registry)



* [Types of image registries](https://cloud.ibm.com/docs/codeengine?topic=codeengine-add-registrytypes-registries)
* [Types of registry secrets](https://cloud.ibm.com/docs/codeengine?topic=codeengine-add-registrytypes-registryaccesssecrets)
* [save_artifact](https://cloud.ibm.com/docs/devsecops?topic=devsecops-devsecops-pipelinectlsave_artifact)



The start stage also clones the repositories found, each repo, and each commit pair. So, for example, repo1 with commit sha1 are cloned in a folder, but the pipeline clones the same repo1 with commit sha2 in a separate folder.

The pipeline registers artifacts and repositories for the pipeline run by using a simple naming notation and incrementing index, such as the following examples:



* repo-1, repo-2, repo-3
* artifact-1artifact-2, artifact-3



You can list these entries in the custom stages by using the following pipelinectl commands:



* [list_repos](https://cloud.ibm.com/docs/devsecops?topic=devsecops-devsecops-pipelinectllist_repos)
* [list_artifacts](https://cloud.ibm.com/docs/devsecops?topic=devsecops-devsecops-pipelinectllist_artifacts)



If you retrieve the branch information in your CC pipeline by using the pipelinectl command load_repo "$repo" branch, it always returns master as branch. Therefore, use commit hashes rather than branches.





 Setup stage 

The setup stage in the CC pipeline runs the script that is located in the setup stage that is defined by your .pipeline-config.yaml. You can determine which pipeline that the script is running in by using the following command:

get_env pipeline_namespace

This command returns either cc, cd, ci, or pr, depending on which pipeline is running. This way, you can reuse the setup script between pipelines if necessary.





 Static code scan 

The static code scan stage runs a static code analyzer tool on the specified app repo codebases.

CC pipeline provides the repos that are found in the inventory for the scanner.

You can use any of the following methods to add static code to your pipeline:
Example request to create a version 4.9 configuration.

curl -X POST "https://containers.cloud.ibm.com/global/v2/storage/satellite/createStorageConfigurationByController" -H "accept: application/json" -H "Authorization: TOKEN" -H "Content-Type: application/json" -d "{ "config-name": "string", "controller": "string", "storage-class-parameters": [ { "additionalProp1": "string", "additionalProp2": "string", "additionalProp3": "string" } ], "storage-template-name": "local-volume-file", "storage-template-version": "4.9", "update-assignments": true, "user-config-parameters": { "entry.name": "AUTO-DISCOVER-DEVICES", { "entry.name": "LABEL-KEY", { "entry.name": "LABEL-VALUE", { "entry.name": "DEVICEPATH", { "entry.name": "FSTYPE","user-secret-parameters": }

Example request to create a version 4.10 configuration.
Example request to create a version 1.8.0 configuration.

curl -X POST "https://containers.cloud.ibm.com/global/v2/storage/satellite/createStorageConfigurationByController" -H "accept: application/json" -H "Authorization: TOKEN" -H "Content-Type: application/json" -d "{ "config-name": "string", "controller": "string", "storage-class-parameters": [ { "additionalProp1": "string", "additionalProp2": "string", "additionalProp3": "string" } ], "storage-template-name": "gcp-compute-persistent-disk-csi-driver", "storage-template-version": "1.8.0", "update-assignments": true, "user-config-parameters":"user-secret-parameters": { "entry.name": "PROJECT_ID",{ "entry.name": "PRIVATE_KEY_ID",{ "entry.name": "PRIVATE_KEY",{ "entry.name": "CLIENT_EMAIL",{ "entry.name": "CLIENT_ID",{ "entry.name": "AUTH_URI",{ "entry.name": "TOKEN_URI",{ "entry.name": "AUTH_PROVIDER_X509_CERT_URL",{ "entry.name": "CLIENT_X509_CERT_URL",}







 Deploying an app that uses Google Compute Engine persistent disk 

You can use the gce-pd-csi-driver to create PVCs that you can use in your cluster workloads.



1. Create a PVC that references a GCP storage class that you created earlier.

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: pvc-gce
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
storageClassName: sat-gce-block-silver
2.
2.17 icr.io/continuous-delivery/pipeline/pipeline-base-image:2.17 sha256:c1e9d5a9674a093635c386f96d35781aea7cad6cc1da86991ee1a85c854216f8 
 2.16 icr.io/continuous-delivery/pipeline/pipeline-base-image:2.16 sha256:3a3b5a981caed4238ef7297bb54b4a32b974b0499b12744347bc661d3f323916 
 2.15 icr.io/continuous-delivery/pipeline/pipeline-base-image:2.15 sha256:f4bff8348fbfdb738c3c681cb6da04cb215f742abe5e09b5d2f5ef07dcfbf21b 
 2.14 icr.io/continuous-delivery/pipeline/pipeline-base-image:2.14 sha256:7bad3379f15fce2d169ae066520b6bdfe719ee4fc8ae271988b4ca772ffb69d5 
 2.13 icr.io/continuous-delivery/pipeline/pipeline-base-image:2.13 sha256:916d4a7cac5ee3102b5fbbbbda67387051a6f7a545353e4ba4bd489246ec8855 
 2.12 icr.io/continuous-delivery/pipeline/pipeline-base-image:2.12 sha256:ff4053b0bca784d6d105fee1d008cfb20db206011453071e86b69ca3fde706a4
Continuous deployment pipeline 

The continuous deployment pipeline generates all of the evidence and change request summary content. The pipeline deploys the build artifacts to an environment, such as staging or production, and then collects, creates, and uploads all existing log files, evidence, and artifacts to the evidence locker.



 Stages and tasks 

Review the following table to learn more about the stages and tasks that are part of the continuous deployment pipeline.



Table 1. Pipeline stages and tasks

 Task or stage Short description Customizable in .pipeline-config.yaml 

 start Set up the pipeline environment. No 
 setup Set up your build and test environment. Yes 
 change-request Generate the change request and create the evidence summary. No 
 deployment Deploy the build artifacts to the environment, such as staging or production. Yes 
 acceptance-test Run acceptance and integration tests on the deployment. Yes 
 finish Collect and upload log files, artifact, and evidence to the evidence locker. Yes 



For more information about how to customize stages by using the .pipeline-config.yaml file, see [Custom scripts](https://cloud.ibm.com/docs/devsecops?topic=devsecops-custom-scripts) and [Pipeline parameters](https://cloud.ibm.com/docs/devsecops?topic=devsecops-cd-devsecops-pipeline-parm) lists.





 Deployment delta 

When the inventory promotion is ready, the continuous deployment pipeline can start. The deployment delta is the difference between the contents of the last concluded deployment and the current deployment. The deployment delta lists the inventory items that are being deployed.

To access the deployment delta in your deployment scripts, you can use the following commands:

 return a JSON file path with an array of inventory entries that were changed
get_env DEPLOYMENT_DELTA_PATH

 return a JSON file path with an array of inventory entries that were deleted
get_env DEPLOYMENT_DELTA_DELETIONS_PATH

 returns a JSON file path with an array of all inventory entries
get_env INVENTORY_ENTRIES_PATH





 Calculate deployment BOM
* sign-artifact: Sign the artifacts.
* release: Add artifacts to the inventory by marking them available for deployment.
* deploy: Deploy artifacts to an environment such as test and dev or staging and prod.
* acceptance-test: Run tests on deployed artifacts. You can also include your post-deployment tests in this stage.
* verify-artifact: Run scripts to check whether the artifacts that are signed in the CI pipeline have valid signatures.
* finish: This stage is customizable stage and is always executed, irrespective of pipeline status.









 Configuration in pipeline-config.yaml 

You can use a .pipeline-config.yaml configuration file to extend pipeline behavior.



 File location 

For pull request and continuous integration pipelines, store the .pipeline-config.yaml configuration file in an app repo in the same manner as the .travis.yml, or Jenkinsfile files. For continuous deployment pipelines, store this file in a dedicated repo.

For all pipelines, you can customize the location and source of the .pipeline-config.yaml file with the following pipeline UI parameters:



* pipeline-config to set the path of the configuration file. The default value is .pipeline-config.yaml.
* pipeline-config-repo to set the repo to pull the configuration and scripts from. The default value is the continuous integration app repo.
* pipeline-config-branch to use as the branch for the configuration in the config repo. The default value is the continuous integration app repo branch, and the master branch in continuous deployment.







 Configuration parameters 

The configuration in the .pipeline-config.yaml file supports the following parameters:

These settings are not pipeline parameters, they must be part of your .pipeline-config.yaml file.



* image: You can use any Docker image that is accessible by the pipeline worker as a base image for the task.
* script: The script to run in the stage. Because this field is used as a script file, ensure that the contents act like a script file in the base image that you provided.
CP-6 (3) - Accessibility 



  Control requirements 

CP-6 (3) - 0
:   The organization identifies potential accessibility problems to the alternate storage site in the event of an area-wide disruption or disaster and outlines explicit mitigation actions.





  NIST supplemental guidance 

Area-wide disruptions refer to those types of disruptions that are broad in geographic scope (e.g., hurricane, regional power outage) with such determinations made by organizations based on organizational assessments of risk. Explicit mitigation actions include, for example: (i) duplicating backup information at other alternate storage sites if access problems occur at originally designated alternate sites; or (ii) planning for physical access to retrieve backup information if electronic accessibility to the alternate site is disrupted.
"result": "success",
"pipeline_id": "8c2b6750-91db-45fb-98ee-51684843b821",
"pipeline_run_id": "89a04de9-2795-4e8e-be90-52a92ac7f9c1",
"issues": [],
"artifacts": [
{
"url": "https://s3.us-south.cloud-object-storage.appdomain.cloud/cos-bucket-name/ci/89a04de9-2795-4e8e-be90-52a92ac7f9c1/artifacts/compliance-app-COMPACT-20210218231513608/unit-tests-results.json_d9619521e7444fef0ff052e59fd54049",
"hash": "d9619521e7444fef0ff052e59fd54049"
}
],
"toolchain_crn": "crn:v1:bluemix:public:toolchain:us-south:a/40111714589c4f7099032529b26a7a63:39d4f080-55e5-42ee-a787-26d936fb2b97::",
"log": [
{
"url": "https://cloud.ibm.com/devops/pipelines/tekton/8c2b6750-91db-45fb-98ee-51684843b821/runs/89a04de9-2795-4e8e-be90-52a92ac7f9c1/code-unit-tests/run-stage?env_id=ibm:yp:us-south",
"hash": null
},
{
* [Configuring a CA, peer, or ordering node to use the HSM](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-adv-deploymentibp-console-adv-deployment-cfg-hsm-node)





[Advanced channel deployment and management](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-governibp-console-govern)



* [General options](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-governibp-console-govern-update-channel-available-parameters-general)
* [Advanced options](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-governibp-console-govern-update-channel-available-parameters-advanced)
* [Updating a channel configuration](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-governibp-console-govern-update-channel)



* [Signature collection flow](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-governibp-console-govern-update-channel-signature-collection)
* [Channel configuration parameters you can update](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-governibp-console-govern-update-channel-available-parameters)



* [Tuning your ordering service](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-governibp-console-govern-orderer-tuning)



* [Block cutting parameters](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-governibp-console-govern-orderer-tuning-batch-size)
Adding a pipeline to an existing toolchain 

You can add a pipeline to an existing toolchain by creating a new Delivery Pipeline tool integration.

To add a pipeline to an existing toolchain, complete these steps:



1.  From the Toolchain Overview page, click Add + to add a tool integration for your toolchain.

Zoom

![Toolchain overview](https://cloud.ibm.com/docs-content/v1/content/5eb88a2575e30e316dbb83829c7f4c8b1ddbc67c/devsecops/images/toolchain-overview.png)

Figure 1. Toolchain overview
2.  Search and click Delivery Pipeline tool integration tile.

Zoom

![Set up your pipeline](https://cloud.ibm.com/docs-content/v1/content/5eb88a2575e30e316dbb83829c7f4c8b1ddbc67c/devsecops/images/setup-new-pipeline.png)

Figure 2. Set up your pipeline
3.  Choose between Classic pipeline that is defined through the UI, or the new Tekton-based 'pipeline as code' that is defined in a Git repository.

Tekton pipelines are currently available only with Private Workers.
4.  Name your pipeline, choose the pipeline configuration method, and then select Create Integration. This action takes you to the pipeline configuration page to finish setting it up.
5.  Click Create Integration.



For more information about setting up a Tekton-based delivery pipeline, see [Creating a Delivery Pipeline for Tekton](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-tekton-pipelines&interface=uiconfigure_tekton_pipeline).
kind: ClusterRole
name: vpc-block-external-attacher-role
subjects:
- kind: ServiceAccount
name: ibm-vpc-block-controller-sa
namespace: kube-system
- apiVersion: storage.k8s.io/v1beta1
kind: CSIDriver
metadata:
name: vpc.block.csi.ibm.io
spec:
attachRequired: true
podInfoOnMount: true
volumeLifecycleModes:
- Persistent
- apiVersion: apps/v1
kind: DaemonSet
metadata:
annotations:
version: 2.0.3_354
labels:
addonmanager.kubernetes.io/mode: Reconcile
app: ibm-vpc-block-csi-driver
name: ibm-vpc-block-csi-node
namespace: kube-system
spec:
selector:
matchLabels:
app: ibm-vpc-block-csi-driver
template:
metadata:
labels:
app: ibm-vpc-block-csi-driver
spec:
containers:
- args:
- --v=5
- --csi-address=$(ADDRESS)
- --kubelet-registration-path=$(DRIVER_REGISTRATION_SOCK)
env:
- name: ADDRESS
value: /csi/csi.sock
- name: DRIVER_REGISTRATION_SOCK
value: /var/lib/kubelet/plugins/vpc.block.csi.ibm.io/csi.sock
- name: KUBE_NODE_NAME
valueFrom:
fieldRef:
fieldPath: spec.nodeName
image: quay.io/k8scsi/csi-node-driver-registrar:v1.2.0
imagePullPolicy: Always
lifecycle:
preStop:
exec:
command:
- /bin/sh
- -c