vania-janet/multiturn-rag-retrieval-data huggingface dataset:
If you want to check your existing tags so as not to duplicate any, run ibmcloud resource tags.

ibmcloud resource tag-attach --resource-name <cluster_name> --tag-names <tag1,tag2>

If you have more than one resource of the same name in your IBM Cloud account, the error message lists the resource CRNs and details, and instructs you to try again with the --resource-idoption.









 Adding labels to existing worker pools 

You can assign a worker pool a label when you [create the worker pool](https://cloud.ibm.com/docs/openshift?topic=openshift-add_workersadd_pool), or later by following these steps. After a worker pool is labeled, all existing and subsequent worker nodes get this label. You might use labels to deploy specific workloads only to worker nodes in the worker pool, such as [edge nodes for load balancer network traffic](https://cloud.ibm.com/docs/openshift?topic=openshift-edge).

Do not include personal information in your labels. Learn more about [securing your personal information](https://cloud.ibm.com/docs/containers?topic=containers-securitypi) when you work with Kubernetes resources.

Before you begin: [Access your Red Hat OpenShift cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-access_cluster).



1. List the worker pools in your cluster.

ibmcloud oc worker-pool ls --cluster <cluster_name_or_ID>
2. List the existing custom labels on worker nodes in the worker pool that you want to label.

ibmcloud oc worker-pool get --cluster <cluster_name_or_ID> --worker-pool <pool>
3. Label the worker pool with a key=value label. When you set a worker pool label, all the existing custom labels are replaced. To keep any existing custom labels on the worker pool, include those labels with this option.
[menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > VPC Infrastructure > Storage > File Shares.
2. Select a file share to view its details.
3. On the file share details page, user tags appear next to the file share name. Click the pencil icon to edit tags.
4. In the Edit tags window, type a tag in the User tags text box.
5. Click Save.







 Add or modify file share user tags from the CLI 

To add tags when you provision a file share, run the ibmcloud is share-create command. To update an existing file share, run the ibmcloud is share-update command. The --user-tags option specifies tags for the file share.

The following example updates an existing file share that is identified by ID and adds the user tags env:test and env:prod.

$ ibmcloud is share-update 50fda9c3-eecd-4152-b473-a98018ccfb10 --user-tags env:test,env:prod
Updating share 50fda9c3-eecd-4152-b473-a98018ccfb10 under account VPC1 as user user.mycompany.com...

ID 50fda9c3-eecd-4152-b473-a98018ccfb10
Name myshare-1
CRN crn:[...]
Lifecycle State stable
Zone us-south-1
Profile tier-3iops
Size(GB) 40
IOPS 3000
Encryption provider_managed
Mount targets ID Name VPC ID VPC Name
87171615-f8b4-4ccd-a216-bab12eb1a973 my-target121 81ee2425-7c2f-4042-9d8f-d02b0ee8886c vpc1
A valid contract is required for creating an instance. For more information, see [About the contract](https://cloud.ibm.com/docs/vpc?topic=vpc-about-contract_se&interface=ui).





 23 August 2022 

Additional user tag support for boot and data volumes
: You can now add user tags to boot and data volumes when provisioning a virtual server instance or creating an instance template. You can add tags to the boot volume by editing it during instance provisioning. You can also add user tags for any data volumes you create and attach. If you import from a snapshot, any tags defined for the snapshot will be applied to the new volume. For more information, see [Create and attach a block storage volume when you create a new instance](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-block-storage&interface=api). For more information about user tags, see [Working with tags](https://cloud.ibm.com/docs/account?topic=account-tag&interface=api).





 17 August 2022 

New stock image for bare metal servers
: Debian 11 is now supported as an image when you provision a bare metal server.





 15 August 2022 

Health check metrics for application load balancer pools
: Two new health check metrics have now been added to IBM Cloud Monitoring for application load balancers, specifically for pools:



* A metric for reporting the total number of members in a pool.
* A second metric for reporting the total number of healthy (or active) members in a pool.



: For more information on these new metrics or the IBM Cloud Monitoring service, refer to [Monitoring Application Load Balancer for VPC metrics](https://cloud.ibm.com/docs/vpc?topic=vpc-monitoring-metrics-alb).





 09 August 2022 

VPC Instance Metadata service
[Actions icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/icons/action-menu-icon.svg). Select Add tags or Edit tags.
5. Enter the tag HIPAA.
6. Click Save.









 Next steps 

Restrict access to manage and view the data. [Learn more](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-iam).
If your cluster does not have any existing tags, you don't have an Edit tags pencil icon. Instead, use the [resource list](https://cloud.ibm.com/docs/account?topic=account-tag) or CLI.
4. Enter the tag that you want to add to your cluster. To assign a key-value pair, use a colon such as costctr:1234.







 Adding tags to clusters with the CLI 



1. Log in to the [IBM Cloud CLI](https://cloud.ibm.com/docs/cli/reference/ibmcloud?topic=cli-ibmcloud_cliibmcloud_login).

ibmcloud login [--sso]
2. [Tag your cluster](https://cloud.ibm.com/docs/cli/reference/ibmcloud?topic=cli-ibmcloud_commands_resourceibmcloud_resource_tag_attach). Replace the --resource-name with the name of your cluster. To list available clusters, run ibmcloud ks cluster ls. If you want to check your existing tags so as not to duplicate any, run ibmcloud resource tags.

ibmcloud resource tag-attach --resource-name <cluster_name> --tag-names <tag1,tag2>

If you have more than one resource of the same name in your IBM Cloud account, the error message lists the resource CRNs and details, and instructs you to try again with the --resource-idoption.









 Adding labels to existing worker pools 

You can assign a worker pool a label when you [create the worker pool](https://cloud.ibm.com/docs/containers?topic=containers-add_workersadd_pool), or later by following these steps. After a worker pool is labeled, all existing and subsequent worker nodes get this label. You might use labels to deploy specific workloads only to worker nodes in the worker pool, such as [edge nodes for load balancer network traffic](https://cloud.ibm.com/docs/containers?topic=containers-edge).
4. When you are satisfied with the changes, modify the configurations for the rest of your custom gateways to update them to the latest patch.



Do not set the tag to a version that is later than your Istio add-on's control plane version.

Update your custom gateway pods as soon as possible after a version is released. Custom gateways that run earlier versions can be exposed to security vulnerabilities.





 Additional gateway customizations 

Custom ingress gateways can be configured with additional customizations, including deploying the gateway load balancer to a specific zone, specifying the minimum number of gateway pod replicas, scheduling custom gateway pods onto [edge nodes](https://cloud.ibm.com/docs/containers?topic=containers-edge), adding preStop lifecycle hooks for graceful shutdowns, and specifying anti-affinity and worker node affinity.

Review examples of these additional customizations in the following IOP YAML file.

apiVersion: install.istio.io/v1alpha1
kind: IstioOperator
metadata:
namespace: ibm-operators
name: custom-ingressgateway-iop
spec:
profile: empty
hub: icr.io/ext/istio
 tag: 1.18.0 Force the gateway to a specific managed Istio version
components:
ingressGateways:
- name: custom-ingressgateway
label:
istio: custom-ingressgateway
namespace: custom-gateways
enabled: true
k8s:
serviceAnnotations:
service.kubernetes.io/ibm-load-balancer-cloud-provider-ip-type: public
service.kubernetes.io/ibm-load-balancer-cloud-provider-zone: "dal12" Deploy the load balancer to a specific zone in your cluster
hpaSpec: Specify the minimum number of pod replicas
minReplicas: 2
tolerations: Schedule the custom gateway pods onto edge nodes
- key: dedicated
value: edge
env:
- name: TERMINATION_DRAIN_DURATION
value: 30s
affinity:
SC-16 - Transmission of Security Attributes 



  Control requirements 

SC-16 - 0
:   The information system associates [Assignment: organization-defined security attributes] with information exchanged between information systems and between system components.





  Additional IBM Cloud for Financial Services specifications 



*  This control is required for ISVs.







  Implementation guidance 

See the resources that follow to learn more about how to implement this control.



*  [Tagging IBM Cloud resources and managing access with tags](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-shared-tagging-resources)







  NIST supplemental guidance 

Security attributes can be explicitly or implicitly associated with the information contained in organizational information systems or system components.
If you disable an existing feature flag and apply the workflow, and then enable the feature flag, its status changes to Workflow initiated and a change request workflow will be initiated.



 How to add a mandatory tag to the ServiceNow workflow change request? 

Follow these steps to add a mandatory tag to the change request for the ServiceNow workflow integration:



1. Login to your ServiceNow instance as an administrator.
2. Open an existing Change Request.

Zoom

![ServiceNow change request](https://cloud.ibm.com/docs-content/v1/content/f3dada89f147af3b88388a2218ddbf64b3c41e5f/app-configuration/images/ac-sn-08.png)

Figure 2. ServiceNow change request
3. Click the additional actions icon to open up the additional options.

Zoom

![ServiceNow additional actions](https://cloud.ibm.com/docs-content/v1/content/f3dada89f147af3b88388a2218ddbf64b3c41e5f/app-configuration/images/ac-sn-09.png)

Figure 3. ServiceNow additional actions
4. Click Configure and select the Form Layout.

Zoom

![Form Layout](https://cloud.ibm.com/docs-content/v1/content/f3dada89f147af3b88388a2218ddbf64b3c41e5f/app-configuration/images/ac-sn-10.png)

Figure 4. ServiceNow additional configure option - Form Layout
5. In the Form Layout under Form view and section, select Change Request and create a new field with Name exactly as Appconfiguration tag, Type as String, and Field length as Medium (100).

Make sure to enter the field Name exactly as Appconfiguration tag (case sensitive).

Zoom

!
eu-de-1 true 2023-02-17T18:53:57+00:00

Source volume ID Name
r010-df8ffd90-f2e5-470b-83d7-76e64995a1aa vicky-block-test1

Bootable false
Encryption provider_managed
Encryption key -
Minimum capacity(GB) 20
Size(GB) 1
Resource group ID Name
a0eb5d9062af485fa5bb2c6999c74eac test-snap

Created 2023-02-17T18:53:57+00:00
Captured at 2023-02-17T18:53:57+00:00
Tags env:test,env:prod

When the user tags are matched with a backup policy, a backup is triggered based on the backup plan schedule. For more information, see [Creating a backup policy](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-policy-create).





 Adding user tags to a snapshot with the API 

You can add user tags to a snapshot by using the API.

Make a PATCH /snapshots call and specify the snapshot ID and user tags. The following example adds user tags env:test and env:prod to the snapshot.

curl -X PATCH "$vpc_api_endpoint/v1/snapshots/7528eb61-bc01-4763-a67a-a414a103f96d?version=2022-01-12&generation=2" -H "Authorization: Bearer ${API_TOKEN}" -d {
"user_tags": [
"env:test",
"env:prod"
]
}'

When the user tags are matched with a backup policy, a backup is triggered based on the backup plan schedule. For more information, see [Creating a backup policy](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-policy-create).
},
/* more items /
]
},
Prefix: 'STRING_VALUE',
Tag: {
Key: 'STRING_VALUE', /* required /
Value: 'STRING_VALUE' /* required /
}
},
ID: 'STRING_VALUE',
Prefix: 'STRING_VALUE',
Priority: 'NUMBER_VALUE',
}
}
]
},
ContentMD5: 'STRING_VALUE',
};
cos.putBucketReplication(params, function(err, data) {
if (err) console.log(err, err.stack); // an error occurred
else console.log(data); // successful response
});
Show more
Customizing your dashboard includes the ability to add, remove, and rearrange the widgets. For more information, see [Customizing your dashboard](https://cloud.ibm.com/docs/account?topic=account-custom-dashboard).







 April 2019 



 04 April 2019 

Export usage data with associated tags
: You can now use our newest tagging capabilities to manage resources, usage, and costs in the exported usage report. When you add a tag to a resource, you can view the tag that is associated with the resource. In the IBM Cloud console, go to Manage> Billing and Usage> Usage> Export CSV> Instances to download your usage report. For more information on exporting tags, check out the [Export tags within your usage data to help with cost allocation](https://www.ibm.com/cloud/blog/export-your-tagged-usage-data-within-the-enhanced-ibm-cloud) blog post.







 March 2019 



 25 March 2019 

Enabling public access to resources
: You can now enable public access to objects in your IBM Cloud® Object Storage buckets by using a new access group that is provided for you in your account. This new access group is called the Public access group, and all users and service IDs are added to it by default. You can update the policies for the access group to enable all users, even unauthenticated users, access to the resource that you specify in the policy. [Learn more about the public access group](https://cloud.ibm.com/docs/account?topic=account-publicpublic).





 12 March 2019 

Multifactor authentication for users with federated IDs
: Account owners or users assigned the administrator role for the billing account management service can enable multifcator authentication (MFA) for all users in their account. Federated users who use their corporate or enterprise single sign-on ID can now be required to authenticate by using MFA for logging in to IBM Cloud.
cf-ray: 69903d250c4966ef-DFW
cache-control: max-age=0, no-cache, no-store, must-revalidate
expires: -1
strict-transport-security: max-age=31536000; includeSubDomains
cf-cache-status: DYNAMIC
expect-ct: max-age=604800, report-uri="[uri...]"
pragma: no-cache
x-content-type-options: nosniff
x-request-id: 1fbe2384-6828-4503-ae7d-050426d1b11b
x-xss-protection: 1; mode=block
server: cloudflare
etag: W/xxxyyyzzz123
Show more
2. Make a PATCH /shares/{share_id} request. Specify the ETag hash string for the If-Match property in the header. Specify the user tags in the user_tags property.

This example updates the file share user tags to env:test and env:prod. The hash string value that you obtained from the ETag property (W/xxxyyyzzz123) is specified in the If-Match header in the call.

curl -X PATCH "$vpc_api_endpoint/v1/shares/50fda9c3-eecd-4152-b473-a98018ccfb10?version=2023-07-11&generation=2&maturity=beta&maturity=beta" -H "Authorization: Bearer" -H "If-Match: W/xxxyyyzzz123" -d {
"user_tags": [
"env:test2",
"env:prod2"
]
}'











 Add access management tags to a file share 

Access management tags are metadata that you can add to your file shares to help organize access control resource relationships. You first create the tag and then add it to an existing file share or when you create a file share.
* For a team to use Schematics, you must assign the appropriate [service access role for Schematics](https://cloud.ibm.com/docs/schematics?topic=schematics-accessaccess-roles), and the permissions that are required for the IBM Cloud resources that this team manages with Schematics. You can review the [documentation](https://cloud.ibm.com/docs/home/alldocs) for each of the IBM Cloud services to find the appropriate IAM access policy.









 Manage access tag in your account 

You can now centrally manage access tags to the Schematics Workspaces in your account at scale. Tags contains the metadata values in the form of key and value to help you organize your cloud data. Tags are essential, as it helps to efficiently optimize your workspace within your account. Following steps helps to create and associate access tags for Schematics Workspaces in your account.



* To create an access tag, see [Create an access management tag](https://cloud.ibm.com/docs/account?topic=account-access-tags-tutorialtagging-resources-create).
* To associate access tags, see [Attach your access management tag to a Schematics Workspaces](https://cloud.ibm.com/docs/account?topic=account-access-tags-tutorialtagging-resources-add)



For more information about managing access tags, see [Controlling access to resources by using tags](https://cloud.ibm.com/docs/account?topic=account-access-tags-tutorial).
"name": "serviceId-test",
"description": "serviceId-test",
"unique_instance_crns": []
}
}
Show more
4. To attach the tag to your service ID, call the [Global Search and Tagging - Tagging API](https://cloud.ibm.com/apidocs/taggingdetach-tag) with the following command.

Replace {SERVICEID_CRN} with the value that you extracted in the previous step.

Replace (serviceidCRN) with the value that you extracted in the previous step.

Replace serviceidCrn with the value that you extracted in the previous step.

Replace serviceid_crn with the value that you extracted in the previous step.

Replace &serviceidCRN with the value that you extracted in the previous step.



* Curl
* Java
* Python
* Go
* Node



curl -X POST --header "Authorization: Bearer {iam_token}" --header "Accept: application/json" --header "Content-Type: application/json" -d '{ "resources": [{ "resource_id": "{SERVICEID_CRN}" }], "tag_names": ["tag_test_1", "tag_test_2"] }' "{base_url}/v3/tags/attach?tag_type=user"

Resource resourceModel = new Resource.Builder().resourceId(serviceidCRN).build();
AttachTagOptions attachTagOptions = new AttachTagOptions.Builder()
.addResources(resourceModel)
.addTagNames("tag_test_1")
.addTagNames("tag_test_2")
.build();

Response<TagResults> response = service.attachTag(attachTagOptions).execute();
TagResults tagResults = response.getResult();
System.out.println(tagResults.toString());
2. Enter the name and URL, and click Add license.
3. Enter all additional license agreements, and click Next.







 Step 7: Review your readme file 

When users install the software, they can view product information by clicking the Readme file link. This information is generated from the readme file that you uploaded to your source repository.



1. From the Edit readme tab, click the Edit icon ![Edit icon](https://cloud.ibm.com/docs-content/v1/content/ff5860bfede49db3197c4bbba7f7123769bdc068/icons/edit-tagging.svg).
2. Preview how the information in the readme file is displayed to users when they install the Terraform template.
3. If you need to make changes, edit the repository where you uploaded the Terraform template and re-create the .tgz file. Then, you can import the updated file to your private catalog again.
4. Click Save.
5. Click Next.







 Step 8: Validate the Terraform template 



1. From the Validate product tab, enter the name of your workspace, select a resource group, select a Schematics region, and click Next.

In the Tags field, you can enter a name of a specific tag to attach to your template. This tag is put on the IBM Cloud Schematics workspace. Tags provide a way to organize, track usage costs, and manage access to the resources in your account.
2. From the Deployment values section, review your parameter values, and click Next.
3. In the Validate version section, select I have read and agree to the following license agreements.
4. Click Validate.

To monitor the progress of the validation process, click View logs.







 Step 9: Manage compliance 

Controls are safeguards that are used to meet security and compliance requirements. Only controls that are supported by Security and Compliance Center, formatted correctly, and validated by Code Risk Analysis and Security and Compliance Center scans appear in the catalog.
* Image tags: 1.19.1 106-8, 1.20.0 106-8, 1.21.0 106-8, 1.22.0 106-8, 1.23.0 106-8, 1.24.0 106-8.
* Updates the storage-secret-sidecar image to v1.2.21
* Golang updated to 1.19.8.
* Fixes issue where cluster-autoscaler stops retrying requests return HTTP401 code.







 Change log for patch update 1.0.6_1010, released 5 April 2023 



* Image tags: 1.19.1 106-7, 1.20.0 106-7, 1.21.0 106-7, 1.22.0 106-7, 1.23.0 106-7, and 1.24.0 106-7.
* Updates the golang version to 1.19.7.







 Change log for patch update 1.0.6_955, released 7 March 2023 



* Image tags: 1.19.1 106-6, 1.20.0 106-6, 1.21.0 106-6, 1.22.0 106-6, 1.23.0 106-6, and 1.24.0 106-6.
* Updates the golang version to 1.19.6.
console.warn(err)
});

When you detach an access management tag from a resource, any associated access policies are also detached from that resource.







 Attaching tags to a resource by using Terraform 

Before you can attach tags to a resource by using Terraform, make sure that you have completed the following:



* Install the Terraform CLI and configure the IBM Cloud Provider plug-in for Terraform. For more information, see the tutorial for [Getting started with Terraform on IBM Cloud®](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-getting-started). The plug-in abstracts the IBM Cloud APIs that are used to complete this task.
* Create a Terraform configuration file that is named main.tf. In this file, you define resources by using HashiCorp Configuration Language. For more information, see the [Terraform documentation](https://www.terraform.io/docs/language/index.html).



Use the following steps to attach tags to a resource by using Terraform:



1. The following example attaches the imb_tag tag to the ibm resource for the resource ID ibm_satellite_location.location.crn.

resource "ibm_resource" "ibm" {
resource_id = ibm_satellite_location.location.crn
tags = [ "ibm_tag" ]
}
2. After you finish building your configuration file, initialize the Terraform CLI. For more information, see [Initializing Working Directories](https://www.terraform.io/cli/init).

terraform init
3. Provision the resources from the main.tf file. For more information, see [Provisioning Infrastructure with Terraform](https://www.terraform.io/cli/run).



1. Run terraform plan to generate a Terraform execution plan to preview the proposed actions.

terraform plan
2. Run terraform apply to create the resources that are defined in the plan.