vania-janet/multiturn-rag-retrieval-data huggingface dataset:
"description" : "Stage environment configuration, which includes services common to all the environment regions. There must be a blueprint configuring all the services common to the stage regions. It is a terraform_template type of configuration that points to a GitHub repo hosting the Terraform modules that can be deployed by a Schematics workspace.",
"labels" : "env:stage", "governance:test", "build:0" ],
"locator_id" : "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global",
"type" : "terraform_template",
"input" : {
"name" : "account_id",
"value" : "$configs].name"account-stage"].input.account_id",
"type" : "string"
}, {
"name" : "resource_group",
"value" : "stage",
"type" : "string"
}, {
"name" : "access_tags",
"value" : "env:stage" ],
"type" : "string"
}, {
"name" : "logdna_name",
"value" : "name of the LogDNA stage service instance",
"type" : "string"
}, {
"name" : "sysdig_name",
"value" : "name of the SysDig stage service instance",
"type" : "string"
} ],
"output" : {
"name" : "resource_group_id"
}, {
"name" : "logdna_id"
}, {
"name" : "sysdig_id"
} ] ! ! !
},
4. Create a PV configuration file called static-file-share.yaml that references your file share.

apiVersion: v1
kind: PersistentVolume
metadata:
name: static-file-share
spec:
mountOptions:
- hard
- nfsvers=4.1
- sec=sys
accessModes:
- ReadWriteMany
capacity:
storage: 10Gi
csi:
volumeAttributes:
nfsServerPath: NFS-SERVER-PATH
driver: vpc.file.csi.ibm.io
volumeHandle: FILE-SHARE-ID:SHARE-TARGET-ID
Show more
5. Create the PV.

oc apply -f static-file-share.yaml
6. To mount the storage to your deployment, create a configuration .yaml file and specify the PVC that binds the PV.

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: pvc-static
spec:
accessModes:
- ReadWriteMany
resources:
requests:
storage: 10Gi
storageClassName: "" Leave the storage class blank.
7. Create the PVC to bind your PV.

oc apply -f pvc-static
8. Attach your fileshare to the desired application pod.

apiVersion: apps/v1
kind: Deployment
metadata:
name: testpod
labels:
app: testpod
spec:
replicas: 1
selector:
matchLabels:
app: testpod
template:
metadata:
labels:
app: testpod
spec:
containers:
- image: IMAGE
name: CONTAINER-NAME
volumeMounts:
- mountPath: /myvol
name: pvc-name
volumes:
- name: pvc-name
persistentVolumeClaim:
claimName: pvc-static The name of the PVC that you created earlier
Show more
image: icr.io/continuous-delivery/pipeline/pipeline-base-image:2.12@sha256:ff4053b0bca784d6d105fee1d008cfb20db206011453071e86b69ca3fde706a4
script: 
!/usr/bin/env bash
echo "Please insert script to invoke/execute dynamic scan tool like OWASP ZAP on the built and deployed application."





 Related information 

For more information about the stages, see [Custom scripts](https://cloud.ibm.com/docs/devsecops?topic=devsecops-custom-scripts).
Post-deployment (checks that evaluate the CD pipeline) 



* Asset type (for example image, commit, , or any asset)



* Evidence



* Evidence type id (for example com.ibm.acceptance_tests)



* Required (evidence must be present in the success state)



* Tool (tool type, for example jest, , or any tool)



* Optional (if the evidence is present, then it must be in the success state)



* Tool (tool type, for example servicenow-v3, , or any tool)



* Ignore (evidence is not validated)









To enable the validation of evidence in your toolchain, set the environment variable opt-in-evidence-checks to 1 in the CD toolchain.

To define the config file path, set evidence-checks-config-path to the file path present in the pipeline-config-repo, otherwise the default config file is used. Different deployment environments might have different config files. For example, stage might have evidence checks that differ from the production evidence checks. If evidence-checks-config-path is not defined, the config file searches for the file with the name <region>.<target>.validation.json, <target>.validation.JSON, or validation.json in the pipeline-config-repo.





 Sample config file 

{
"pre-deployment": [
{
"asset_type": "commit",
"evidences":
{
"evidence_type_id": "com.ibm.branch_protection",
"rules": {
"required": ],
"optional":
{
"tool": ""
}
],
"ignore": ]
}
},
{
"evidence_type_id": "com.ibm.peer_review",
"rules": {
"required": ],
"optional":
{
"tool": ""
}
],
"ignore": ]
}
},
{
"commit_sha": "b85e3d472e9cc35b429c39e8c3f9eb282738c20a",
"name": "hello-compliance-app",
"pipeline_run_id": "f21321bf-9054-4bf3-80a8-4fb34743b7d9",
"version": "v1",
"app_artifacts": {
"signature": "owFNUX1IE3EY3vwAEy0VyoSJdkVWtu0+d3eTjNIIi0jETCSU3353cz+83V23myi2BlFgYiUFqSmZLciUzCJkRYJp9IEWFWXB0hAyrBQxEjIIuhFSf70vL8/7vM/zPi3JsaYEc+TnbqG8qrnTPDZ8w2WqiqwtacCghnQEgYQ5GzAkiLKO9PpoLyiwRtSsmugWNVGGIubE/D4bgpoNKXag60gCdo8oSYoVKl5VQsDAWIGqOkmcxAmSYHGO4AjC6gU+3eBxcYxICTRLijyEFOOiSR5SvMhBys2LLpIjWYqDJA6wwHYMeUG1+J8GL5CRW/TpVgFVG8VQ4vMAknE4BUA5OIoQGIKhKZwFkIeAdnECj+OCmxQADh2QoFmG5lkWUiTN8gJ0kDxPuxiWJAU8ekyvV6PegK54EcyGiqwDJItatg9Vy0D3a2IUpKg6UuS/T4KaaIC1fzuMDbfhmMGEvIY64FUxJ+Ew3PMU
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 
 2.11 icr.io/continuous-delivery/pipeline/pipeline-base-image:2.11 sha256:61d35cdad7e77dbcedbf6ab47591b38121b03c5a4f41041f2d628cb8485602e1 
 2.10 icr.io/continuous-delivery/pipeline/pipeline-base-image:2.10 sha256:c59986a7a4e5931f1172ba3c6fc5f535edbbcc60daf6f3e092df9851283f8ceb 
 2.9 icr.io/continuous-delivery/pipeline/pipeline-base-image:2.9 sha256:2976e1374e87f5cddabcf80179d9708868d52dbf656fdde60f803553be633db2 
 2.8 icr.io/continuous-delivery/pipeline/pipeline-base-image:2.8 sha256:119e05bad27ccc899df5b895ccba41135fd5edbc5786a77c1c763621b00dee0f
: Kubernetes version [1.18.8_1525](https://cloud.ibm.com/docs/containers?topic=containers-118_changelog1188_1525_master), [1.17.11_1537](https://cloud.ibm.com/docs/containers?topic=containers-117_changelog11711_1537_master), [1.16.14_1544](https://cloud.ibm.com/docs/containers?topic=containers-116_changelog11614_1544_master), and [1.15.12_1550](https://cloud.ibm.com/docs/containers?topic=containers-115_changelog11512_1550_master).





 17 August 2020 

Locations
: You can create [clusters on VPC infrastructure](https://cloud.ibm.com/docs/containers?topic=containers-regions-and-zoneszones-vpc) in the Tokyo multizone region.

Versions
: Worker node fix pack update change log documentation is available.
: Kubernetes version [1.18.8_1525](https://cloud.ibm.com/docs/containers?topic=containers-118_changelog1188_1525), [1.17.11_1537](https://cloud.ibm.com/docs/containers?topic=containers-117_changelog11711_1537), [1.16.14_1544](https://cloud.ibm.com/docs/containers?topic=containers-116_changelog11614_1544), and [1.15.12_1550](https://cloud.ibm.com/docs/containers?topic=containers-115_changelog11512_1550) .

VPC Gen 2
: Added a tutorial for migrating VPC Gen 1 cluster resources to VPC Gen 2.





 12 August 2020 

Istio add-on
- kind: ServiceAccount
name: ibm-vpc-block-controller-sa
namespace: kube-system
- apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
annotations:
version: 2.0.3_354
labels:
addonmanager.kubernetes.io/mode: Reconcile
app: ibm-vpc-block-csi-driver
name: vpc-block-external-attacher-role
rules:
- apiGroups:
- ""
resources:
- persistentvolumes
verbs:
- get
- list
- watch
- update
- patch
- apiGroups:
- ""
resources:
- nodes
verbs:
- get
- list
- watch
- apiGroups:
- csi.storage.k8s.io
resources:
- csinodeinfos
verbs:
- get
- list
- watch
- apiGroups:
- storage.k8s.io
resources:
- volumeattachments
verbs:
- get
- list
- watch
- update
- patch
- apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
annotations:
version: 2.0.3_354
labels:
addonmanager.kubernetes.io/mode: Reconcile
app: ibm-vpc-block-csi-driver
name: vpc-block-external-attacher-binding
roleRef:
apiGroup: rbac.authorization.k8s.io
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
: Kubernetes [1.24.3_1531](https://cloud.ibm.com/docs/containers?topic=containers-changelog_124), [1.23.9_1539](https://cloud.ibm.com/docs/containers?topic=containers-changelog_123), [1.22.12_1564](https://cloud.ibm.com/docs/containers?topic=containers-changelog_122), and [1.21.14_1574](https://cloud.ibm.com/docs/containers?topic=containers-changelog_121).





 22 July 2022 

Cluster autoscaler add-on
: Version 1.1.0_729 is available. See [Cluster autoscaler add-on change log](https://cloud.ibm.com/docs/containers?topic=containers-ca_changelog).





 19 July 2022 

Ingress ALB change log updates
: Updated the [Ingress ALB change log](https://cloud.ibm.com/docs/containers?topic=containers-cluster-add-ons-changelog) for versions 1.1.2_2368_iks and 1.2.1_2415_iks.

Cluster autoscaler add-on
: Version 1.0.5_728 is available. See [Cluster autoscaler add-on change log](https://cloud.ibm.com/docs/containers?topic=containers-ca_changelog).





 18 July 2022 

Block Storage for VPC add-on.
: [Version 4.3.4_1551](https://cloud.ibm.com/docs/containers?topic=containers-vpc_bs_changelog) and [Version 4.4.8_1550](https://cloud.ibm.com/docs/containers?topic=containers-vpc_bs_changelog) are available.

Worker node fix pack
"crn": "crn:v1:bluemix:public:is:us-east-2:a/be636a7a6e4d4b6296bedf669ce8f757::subnet:0767-064498f3-4df5-4fa5-b2ed-de5a3bfea024",
"name": "lb-subnet"
}
],
"resource_group": {
"id": "42c4f51adc3147b4b4049ad9826c30a1",
"href": "https://resource-controller.cloud.ibm.com/v1/resource_groups/42c4f51adc3147b4b4049ad9826c30a1",
"name": "Default"
},
"resource_type": "load_balancer",
"logging": {
"datapath": {
"active": false
}
},
"profile": {
"href": "https://us-east.iaas.cloud.ibm.com/v1/load_balancer/profiles/dynamic",
"name": "dynamic",
"family": "Application"
},
"security_groups": [
{
"id": "r014-b739c959-fb3c-44cc-9ec5-41c45b4d637e",
"href": "https://us-east.iaas.cloud.ibm.com/v1/security_groups/r014-b739c959-fb3c-44cc-9ec5-41c45b4d637e",
-c, --cluster CLUSTER
: The name or ID of the cluster.

--version IMAGE_VERSION
: Optional: The version of the image that you want the ALB to run. To list available versions, run ibmcloud ks ingress alb versions. To specify a version other than the default, you must first disable automatic updates by running the ibmcloud ks ingress alb autoupdate disable command. If you omit this option, the ALB runs the default version of the same image that the ALB previously ran: either the Kubernetes Ingress image or the IBM Cloud Kubernetes Service Ingress image.

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



 Example ingress alb enable vpc-gen2 command 

ibmcloud ks ingress alb enable vpc-gen2 --alb private-cr18a61a63a6a94b658596aa93a087aaa9-alb1 --cluster mycluster --version 1.1.2_2507_iks







 ibmcloud ks ingress alb get 

Virtual Private Cloud

Classic infrastructure

View the details of an Ingress ALB in a cluster.

ibmcloud ks ingress alb get --alb ALB_ID --cluster CLUSTER [--output json] [-q]

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

Command options:

--alb ALB_ID
: Required: The ID for an ALB. To view the IDs for the ALBs in a cluster, run ibmcloud ks ingress alb ls --cluster CLUSTER.

-c, --cluster CLUSTER
: 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.



 Example ingress alb get command
public-crdf253b6025d64944ab99ed63bb4567b6-alb4 true enabled public 169.50.35.62 dal10 ingress:1.1.2_2507_iks 2234940
6. Optional for public ALBs: Verify that the IP addresses of the new ALBs are listed under the IBM-provided Ingress subdomain for your cluster. You can find this subdomain by running ibmcloud ks cluster get --cluster <cluster_name_or_ID>.

nslookup <Ingress_subdomain>

Example output.

Non-authoritative answer:
Name: mycluster-<hash>-0000.us-south.containers.appdomain.cloud
Addresses: 169.49.28.09
169.50.35.62
7. Optional: If you no longer need the subnets on the old VLANs, you can [remove them](https://cloud.ibm.com/docs/containers?topic=containers-subnetsremove-subnets).
Consider naming the public gateway in the format <cluster>-<zone>-gateway. In the output, note the public gateway's ID.



ibmcloud is public-gateway-create <gateway_name> <VPC_ID> <zone>

Example output

ID 26466378-6065-4716-a90b-ac7ed7917c63
Name mycluster-us-south-1-gateway
Floating IP 169.xx.xx.xxx(26466378-6065-4716-a90b-ac7ed7917c63)
Status pending
Created 2019-09-20T16:27:32-05:00
Zone us-south-1
VPC myvpc(36c8f522-4f0d-400c-8226-299f0b8198cf)
Resource group -
4. Using the IDs of the public gateway and the subnet, attach the public gateway to the subnet.

ibmcloud is subnet-update <subnet_ID> --public-gateway-id <gateway_ID>

Example output

ID 91e946b4-7094-46d0-9223-5c2dea2e5023
Name mysubnet1
IPv4 CIDR 10.240.xx.xx/24
Address available 250
Address total 256
ACL allow-all-network-acl-36c8f522-4f0d-400c-8226-299f0b8198cf(585bc142-5392-45d4-afdd-d9b59ef2d906)
Gateway mycluster-us-south-1-gateway(26466378-6065-4716-a90b-ac7ed7917c63)
Created 2019-08-21T09:43:11-05:00
Status available
Zone us-south-1
"type": "",
"description": ""
},
{
"name": "compute_cluster_key_pair",
"secure": false,
"value": "scale-hpcc-key",
"type": "",
"description": ""
}
],
"has_githubtoken": true
}
],
"runtime_data": [
{
"id": "434f99a3-2633-4b",
"engine_name": "terraform",
"engine_version": "v1.0.11",
"state_store_url": "https://us.schematics.cloud.ibm.com/v1/workspaces/us-south.workspace.Sample-Schematic-Scale-API-workspace.096bd8d8/runtime_data/434f99a3-2633-4b/state_store",
"log_store_url": "https://us.schematics.cloud.ibm.com/v1/workspaces/us-south.workspace.Sample-Schematic-Scale-API-workspace.096bd8d8/runtime_data/434f99a3-2633-4b/log_store"
}
],
"shared_data": {
"resource_group_id": ""
},
"applied_shareddata_ids": null,
"updated_at": "0001-01-01T00:00:00Z",
"last_health_check_at": "0001-01-01T00:00:00Z",
"cart_id": "",
"last_action_name": "",
"last_activity_id": "",
"last_job": {
"job_id": "",
"job_name": "",
app: ibm-vpc-block-csi-driver
name: vpc-block-driver-registrar-role
rules:
- apiGroups:
- ""
resources:
- events
verbs:
- get
- list
- watch
- create
- update
- patch
- apiGroups:
- ""
resources:
- nodes
verbs:
- get
- list
- watch
- apiGroups:
- ""
resources:
- persistentvolumes
verbs:
- get
- list
- watch
- create
- delete
- apiGroups:
- ""
resources:
- persistentvolumeclaims
verbs:
- get
- list
- watch
- update
- apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
annotations:
version: 2.0.3_354
labels:
addonmanager.kubernetes.io/mode: Reconcile
app: ibm-vpc-block-csi-driver
name: vpc-block-driver-registrar-binding
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: vpc-block-driver-registrar-role
subjects:
- kind: ServiceAccount
name: ibm-vpc-block-node-sa
namespace: kube-system
- apiVersion: v1
imagePullSecrets:
- name: bluemix-default-secret
- name: bluemix-default-secret-regional
- name: bluemix-default-secret-international
- name: icr-io-secret
kind: ServiceAccount
metadata:
annotations:
version: 2.0.3_354
labels:
addonmanager.kubernetes.io/mode: Reconcile
app: ibm-vpc-block-csi-driver
name: vpc-block-driver-registrar-role
rules:
- apiGroups:
- ""
resources:
- events
verbs:
- get
- list
- watch
- create
- update
- patch
- apiGroups:
- ""
resources:
- nodes
verbs:
- get
- list
- watch
- apiGroups:
- ""
resources:
- persistentvolumes
verbs:
- get
- list
- watch
- create
- delete
- apiGroups:
- ""
resources:
- persistentvolumeclaims
verbs:
- get
- list
- watch
- update
- apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
annotations:
version: 2.0.2_285
labels:
addonmanager.kubernetes.io/mode: Reconcile
app: ibm-vpc-block-csi-driver
name: vpc-block-driver-registrar-binding
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: vpc-block-driver-registrar-role
subjects:
- kind: ServiceAccount
name: ibm-vpc-block-node-sa
namespace: kube-system
- apiVersion: v1
imagePullSecrets:
- name: bluemix-default-secret
- name: bluemix-default-secret-regional
- name: bluemix-default-secret-international
- name: icr-io-secret
kind: ServiceAccount
metadata:
annotations:
version: 2.0.2_285
labels:
addonmanager.kubernetes.io/mode: Reconcile
To view the IDs for the ALBs in a cluster, run ibmcloud ks ingress alb ls --cluster CLUSTER.

-c, --cluster CLUSTER
: 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.



 Example ingress alb get command 

ibmcloud ks ingress alb get --alb public-cr18a61a63a6a94b658596aa93a087aaa9-alb1 --cluster mycluster







 ibmcloud ks ingress alb health-checker disable 

Virtual Private Cloud

Classic infrastructure

Disable the health checker for an Ingress ALB in a cluster.

ibmcloud ks ingress alb health-checker disable --cluster CLUSTER [-q]

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

Command options:

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

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



 Example ingress alb health-checker disable command 

ibmcloud ks ingress alb health-checker disable --cluster mycluster







 ibmcloud ks ingress alb health-checker enable 

Virtual Private Cloud

Classic infrastructure

Enable the health checker for an Ingress ALB in a cluster.

ibmcloud ks ingress alb health-checker enable --cluster CLUSTER [-q]

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

Command options:

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

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



 Example ingress alb health-checker enable command 

ibmcloud ks ingress alb health-checker enable --cluster mycluster
: Kubernetes [1.21.14_1578](https://cloud.ibm.com/docs/containers?topic=containers-changelog_121), [1.22.15_1573](https://cloud.ibm.com/docs/containers?topic=containers-changelog_122), [1.23.12_1547](https://cloud.ibm.com/docs/containers?topic=containers-changelog_123) and [1.24.6_1539](https://cloud.ibm.com/docs/containers?topic=containers-changelog_124).





 23 September 2022 

Block Storage for VPC add-on version 4.4.11_1614.
: For more information, see [the change log](https://cloud.ibm.com/docs/containers?topic=containers-vpc_bs_changelog).





 22 September 2022 

Cluster autoscaler add-on versions 1.1.0_798, 1.0.6_800, and 1.0.5_779.
: For more information, see [Cluster autoscaler add-on change log](https://cloud.ibm.com/docs/containers?topic=containers-ca_changelog).

Block Storage for VPC add-on version 4.3.7_1613.
: For more information, see [the change log](https://cloud.ibm.com/docs/containers?topic=containers-vpc_bs_changelog).





 21 September 2022 

CLI change log update
: The [CLI change log](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelog) is updated for version 1.0.452.

Ingress ALB change log updates
: Updated the [Ingress ALB change log](https://cloud.ibm.com/docs/containers?topic=containers-cluster-add-ons-changelog) for versions 1.2.1_2558_iks and 1.1.2_2586_iks.
: Kubernetes version [1.18.4_1517](https://cloud.ibm.com/docs/containers?topic=containers-118_changelog1184_1517), [1.17.7_1529](https://cloud.ibm.com/docs/containers?topic=containers-117_changelog1177_1529), [1.16.11_1536](https://cloud.ibm.com/docs/containers?topic=containers-116_changelog11611_1536), and [1.15.12_1543](https://cloud.ibm.com/docs/containers?topic=containers-115_changelog11512_1543).





 18 June 2020 

Ingress ALB change log
: Updated the [ingress-auth image build to 413](https://cloud.ibm.com/docs/containers?topic=containers-cluster-add-ons-changelogkube_ingress_changelog).





 16 June 2020 

CLI change log
: Updated the IBM Cloud Kubernetes Service CLI plug-in change log page for the [release of version 1.0.99](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelog10).





 9 June 2020 

CLI change log
: Updated the IBM Cloud Kubernetes Service CLI plug-in change log page for the [release of version 1.0.94](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelog10).

Permissions
: Added a [Permissions to create a cluster](https://cloud.ibm.com/docs/containers?topic=containers-access_referencecluster_create_permissions) reference topic, and restructured cluster creation and user access topics to refer to this reference topic.

New! Static routes add-on
"href": "https://us-south.iaas.cloud.ibm.com/v1/load_balancers/dd754295-e9e0-4c9d-bf6c-58fbc59e5727",
"name": "example-balancer",
"created_at": "2018-07-13T22:22:24.489Z",
"hostname": "dd754295-e9e0-4c9d-bf6c-58fbc59e5727.lb.appdomain.cloud",
"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"
}
],
"operating_status": "online",
"pools": [
{
"id": "0738-70294e14-4e61-11e8-bcf4-0242ac110004",
"href": "https://us-south.iaas.cloud.ibm.com/v1/load_balancers/dd754295-e9e0-4c9d-bf6c-58fbc59e5727/pools/70294e14-4e61-11e8-bcf4-0242ac110004",
"name": "example-pool"
}
],
"private_ips": [
At your on-premises cluster, you can test the following job:

$ bsub -q send_q sh -c 'echo $HOSTNAME > /home/lsfadmin/shared/mc-test.txt'

You can see that the job comes to the HPCCluster at 10.244.128.37.

$ bjobs -aw

JOBID USER STAT QUEUE FROM_HOST EXEC_HOST JOB_NAME SUBMIT_TIME
304 lsfadmin DONE recv_q on-premise-management@OnPremiseCluster:911 icgen2host-10-244-128-39 sh -c 'echo $HOSTNAME > /home/lsfadmin/shared/mc-test.txt' Jun 17 02:27





 Additional resources 

For more information, check out the following IBM Spectrum LSF documentation:



* [IBM Spectrum LSF multi-cluster capability](https://www.ibm.com/docs/en/spectrum-lsf/10.1.0?topic=lsf-multicluster-capability)
* [Set common ports](https://www.ibm.com/docs/en/spectrum-lsf/10.1.0?topic=overview-set-common-ports)
* [Enable queues for the LSF multi-cluster capability](https://www.ibm.com/docs/en/spectrum-lsf/10.1.0?topic=queues-enable-multicluster)
* [Using the IBM Spectrum LSF Resource Connector](https://www.ibm.com/docs/en/spectrum-lsf/10.1.0?topic=lsf-resource-connnector)
* [IBM Spectrum LSF Data Manager](https://www.ibm.com/docs/en/spectrum-lsf/10.1.0?topic=lsf-data-manager)
name: ibm-vpc-block-controller-sa
namespace: kube-system
- apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
annotations:
version: 2.0.2_285
labels:
addonmanager.kubernetes.io/mode: Reconcile
app: ibm-vpc-block-csi-driver
name: vpc-block-external-attacher-role
rules:
- apiGroups:
- ""
resources:
- persistentvolumes
verbs:
- get
- list
- watch
- update
- patch
- apiGroups:
- ""
resources:
- nodes
verbs:
- get
- list
- watch
- apiGroups:
- csi.storage.k8s.io
resources:
- csinodeinfos
verbs:
- get
- list
- watch
- apiGroups:
- storage.k8s.io
resources:
- volumeattachments
verbs:
- get
- list
- watch
- update
- patch
- apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
annotations:
version: 2.0.2_285
labels:
addonmanager.kubernetes.io/mode: Reconcile
app: ibm-vpc-block-csi-driver
name: vpc-block-external-attacher-binding
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: vpc-block-external-attacher-role
subjects:
- kind: ServiceAccount
name: ibm-vpc-block-controller-sa
namespace: kube-system
- apiVersion: apps/v1
kind: DaemonSet
metadata:
annotations: