vania-janet/multiturn-rag-retrieval-data huggingface dataset:
[Available](https://cloud.ibm.com/docs-content/v1/content/11f96f96f8f4b60cf6f3fa4d904856a2c4528bc2/icons/checkmark-icon.svg) 
 Certificate Library: Manage ![Available](https://cloud.ibm.com/docs-content/v1/content/11f96f96f8f4b60cf6f3fa4d904856a2c4528bc2/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/11f96f96f8f4b60cf6f3fa4d904856a2c4528bc2/icons/checkmark-icon.svg) 
 Certificate Library: View ![Available](https://cloud.ibm.com/docs-content/v1/content/11f96f96f8f4b60cf6f3fa4d904856a2c4528bc2/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/11f96f96f8f4b60cf6f3fa4d904856a2c4528bc2/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/11f96f96f8f4b60cf6f3fa4d904856a2c4528bc2/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/11f96f96f8f4b60cf6f3fa4d904856a2c4528bc2/icons/checkmark-icon.svg) 
 Custom entity: View all custom entity instances in org !
* [Version 1.0.384](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelogcli-10384)
* [Version 1.0.374](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelogcli-10374)
* [Version 1.0.372](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelogcli-10372)
* [Version 1.0.353](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelogcli-10353)
* [Version 1.0.347](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelogcli-10347)
* [Version 1.0.344](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelogcli-10344)
* [Version 1.0.334](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelogcli-10334)
* [Version 1.0.331](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelogcli-10331)
* [Version 1.0.312](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelogcli-10312)
* [Version 1.0.300](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelogcli-10300)
* [Version 1.0.295](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelogcli-10295)
flavor](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/container_dedicated_host_flavor)<br> * [ibm_container_dedicated_host_flavors](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/container_dedicated_host_flavors)<br> * [ibm_container_dedicated_host_pool](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/container_dedicated_host_pool)<br> * [ibm_container_nlb_dns](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/container_nlb_dns)<br> * [ibm_container_storage_attachment](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/container_storage_attachment)<br> * [ibm_container_vpc_
* [ibmcloud ks ingress instance ls](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_ingress_instance_ls)
* [ibmcloud ks ingress instance register](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_ingress_instance_register)
* [ibmcloud ks ingress instance unregister](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_ingress_instance_unregister)
* [ibmcloud ks ingress lb get](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_ingress_lb_proxy-protocol_get)
* [ibmcloud ks ingress lb proxy-protocol disable](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_ingress_lb_proxy-protocol_disable)
* [ibmcloud ks ingress lb proxy-protocol enable](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_ingress_lb_proxy-protocol_enable)
* [ibmcloud ks ingress secret create](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_ingress_secret_create)
* [ibmcloud ks ingress secret field add](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_ingress_secret_field_add)
* [ibmcloud ks ingress secret field ls](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_ingress_secret_field_ls)
* [2 February 2022](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_release_notesregistry-02feb2022)



* [Replication of exemption policies between IBM regions is discontinued](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_release_notes02feb2022_exemption)



* [1 February 2022](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_release_notesregistry-01feb2022)



* [Storage that is used by untagged images is being charged for](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_release_notes01feb2022_billing)



* [17 January 2022](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_release_notesregistry-17jan2022)



* [View IBM Cloud Activity Tracker events for Red Hat signing](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_release_notes17jan2022_sig)



* [7 December 2021](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_release_notesregistry-07dec2021)



* [Define configuration rules for Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_release_notes07dec2021_gov)



* [1 November 2021](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_release_notesregistry-01nov2021)



* [Using Notary v1 for signing images is discontinued](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_release_notes01nov2021_notary)



* [5 October 2021](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_release_notesregistry-05oct2021)
[Available](https://cloud.ibm.com/docs-content/v1/content/11f96f96f8f4b60cf6f3fa4d904856a2c4528bc2/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/11f96f96f8f4b60cf6f3fa4d904856a2c4528bc2/icons/checkmark-icon.svg) 
 Catalog: View Private and Shared Catalogs ![Available](https://cloud.ibm.com/docs-content/v1/content/11f96f96f8f4b60cf6f3fa4d904856a2c4528bc2/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/11f96f96f8f4b60cf6f3fa4d904856a2c4528bc2/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/11f96f96f8f4b60cf6f3fa4d904856a2c4528bc2/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/11f96f96f8f4b60cf6f3fa4d904856a2c4528bc2/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/11f96f96f8f4b60cf6f3fa4d904856a2c4528bc2/icons/checkmark-icon.svg) 
 Catalog: View Published Catalogs !
* [Version 1.0.312](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelogcli-10312)
* [Version 1.0.300](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelogcli-10300)
* [Version 1.0.295](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelogcli-10295)
* [Version 1.0.275](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelogcli-10275)
* [Version 1.0.258](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelogcli-10258)
* [Version 1.0.233](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelogcli-10233)
* [Version 1.0.231](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelogcli-10231)
* [Version 1.0.223](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelogcli-102238)
* [Version 1.0.208](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelogcli-10208)
* [Version 1.0.206](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelogcli-10206)
* [Version 1.0.197](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelogcli-10197)
: Updated the [CLI reference page](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-cli) to reflect multiple changes for the release of version [0.3.34](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelog) of the IBM Cloud Kubernetes Service CLI plug-in.





 4 June 2019 

Version change logs
: Updated the change logs for the [1.14.2_1521](https://cloud.ibm.com/docs/containers?topic=containers-114_changelog1142_1521), [1.13.6_1524](https://cloud.ibm.com/docs/containers?topic=containers-113_changelog1136_1524), [1.12.9_1555](https://cloud.ibm.com/docs/containers?topic=containers-112_changelog1129_1555), and [1.11.10_1561](https://cloud.ibm.com/docs/containers?topic=containers-111_changelog11110_1561) patch releases.





 3 June 2019 

Bringing your own Ingress controller
: Updated the steps to reflect changes to the default community controller and to require a health check for controller IP addresses in multizone clusters.

IBM Cloud Object Storage
: Updated the [steps](https://cloud.ibm.com/docs/containers?topic=containers-storage_cos_install) to install the IBM Cloud Object Storage plug-in with or without the Helm server, Tiller.

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

Kustomize
* [Version 1.0.459](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelogcli-10459)
* [Version 1.0.454](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelogcli-10454)
* [Version 1.0.452](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelogcli-10452)
* [Version 1.0.446](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelogcli-10446)
* [Version 1.0.444](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelogcli-10444)
* [Version 1.0.439](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelogcli-10439)
* [Version 1.0.433](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelogcli-10433)
* [Version 1.0.431](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelogcli-10431)
* [Version 1.0.430](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelogcli-10430)
* [Version 1.0.426](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelogcli-10426)
* [Version 1.0.419](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelogcli-10419)
* [24 February 2022](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-feb2422)



* Container service CLI
* Kubernetes Ingress image



* [23 February 2022](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-feb2322)



* Cluster autoscaler
* Istio add-on



* [18 February 2022](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-feb1822)



* Container service CLI



* [17 February 2022](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-feb1722)



* IBM Cloud Object Storage plug-in



* [15 February 2022](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-feb1522)



* Istio add-on



* [14 February 2022](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-feb1422)



* Worker node fix pack
* IBM Cloud Object Storage doc restructuring.
* Block Storage for VPC add-on.



* [10 February 2022](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-feb1022)



* Certified Kubernetes
* ALB OAuth Proxy add-on



* [9 February 2022](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-feb922)



* New! Kubernetes 1.23
* Deprecated and unsupported Kubernetes versions
Allow hosts to communicate with IBM Cloud Container Registry.
: 

* Destination IP addresses: N/A
* Destination hostnames: icr.io, registry.bluemix.net, jp2.icr.io, au.icr.io, registy.au-syd.bluemix.net
* Protocol and ports: HTTPS 443



Optional: Allow hosts to communicate with IBM Cloud Log Analysis.
: 

* Destination IP addresses and hostnames: [IBM Cloud Log Analysis endpoints](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-endpointsendpoints_api_public)
* Protocol and ports: HTTPS 443



: If you plan to use IBM Cloud Log Analysis in your Red Hat OpenShift on IBM Cloud Satellite clusters, then include these network options.

Optional: Allow hosts to communicate with IBM Cloud Monitoring.
: 

* Destination IP addresses and hostnames: [Monitoring endpoints](https://cloud.ibm.com/docs/monitoring?topic=monitoring-endpoints)
* Protocol and ports: HTTPS 443 and 6443



: If you plan to use Monitoring in your Red Hat OpenShift on IBM Cloud Satellite clusters, then include these network options.
For step-by-step instructions for assigning, removing, and reviewing access, see [Assigning access resources by using the CLI](https://cloud.ibm.com/docs/account?topic=account-assign-access-resources&interface=cliaccess-resources-cli). The following example shows a command for assigning the Editor role to a user:

Use directlink for the service name. Also, use quotations around role names that are more than one word like the example here.

ibmcloud iam user-policy-create USER@EXAMPLE.COM --service-name directlink --roles Editor





 Assigning access to Direct Link by using the API 

For step-by-step instructions for assigning, removing, and reviewing access, see [Assigning access to resources by using the API](https://cloud.ibm.com/docs/account?topic=account-assign-access-resources&interface=api) or the [Create a policy API docs](https://cloud.ibm.com/apidocs/iam-policy-managementcreate-policy). Role cloud resource names (CRN) in the following table are used to assign access with the API.



Table 3. Role ID values for API use

 Role name Role CRN 

 Viewer crn:v1:bluemix:public:directlink::::serviceRole:Viewer 
 Operator crn:v1:bluemix:public:directlink::::serviceRole:Operator 
 Editor crn:v1:bluemix:public:directlink::::serviceRole:Editor 
 Administrator crn:v1:bluemix:public:directlink::::serviceRole:Administrator 
 Reader crn:v1:bluemix:public:directlink::::serviceRole:Reader 
 Writer crn:v1:bluemix:public:directlink::::serviceRole:Writer 
 Manager crn:v1:bluemix:public:directlink::::serviceRole:Manager
If messages in the events describe an error in your resource configuration, fix the values in your resource file and reapply the file for the resource.

oc describe ingress myingressresource



Your Ingress resource is created in the same project as your app services, and your apps are registered with the Ingress controller.





 Step 4: Access your app 

In a web browser, enter the URL of the app service to access.

https://<domain>/<app1_path>

If you exposed multiple apps, access those apps by changing the path that is appended to the URL.

https://<domain>/<app2_path>

If you use a wildcard domain, access those apps with their own subdomains.

http://<subdomain1>.<domain>/<app1_path>

http://<subdomain2>.<domain>/<app1_path>

Can't connect to your app through Ingress? Try [Troubleshooting Ingress](https://cloud.ibm.com/docs/openshift?topic=openshift-ingress-status).
* [Creating a set of service credentials](https://cloud.ibm.com/docs/containers?topic=containers-storage-cos-tutorial-quotastorage-cos-quota-credentials)
* [Creating a secret to store your credentials](https://cloud.ibm.com/docs/containers?topic=containers-storage-cos-tutorial-quotastorage-cos-quota-secret)
* [Installing the plug-in](https://cloud.ibm.com/docs/containers?topic=containers-storage-cos-tutorial-quotastorage-cos-quota-install)
* [Dynamically provisioning a bucket with a quota](https://cloud.ibm.com/docs/containers?topic=containers-storage-cos-tutorial-quotastorage-cos-quota-create-bucket)
* [Uploading a file to your bucket](https://cloud.ibm.com/docs/containers?topic=containers-storage-cos-tutorial-quotastorage-cos-quota-create-file)
* [Creating an app that mounts the bucket](https://cloud.ibm.com/docs/containers?topic=containers-storage-cos-tutorial-quotastorage-cos-quota-create-app)
* [Review](https://cloud.ibm.com/docs/containers?topic=containers-storage-cos-tutorial-quotastorage-cos-quota-review)
* [Next steps](https://cloud.ibm.com/docs/containers?topic=containers-storage-cos-tutorial-quotastorage-cos-quota-next)



[VPC: Setting up authorized IP addresses for IBM Cloud Object Storage](https://cloud.ibm.com/docs/containers?topic=containers-storage_cos_vpc_ipstorage_cos_vpc_ip)

[Storage class reference](https://cloud.ibm.com/docs/containers?topic=containers-storage_cos_referencestorage_cos_reference)
Access the files through your browser or by using curl:

curl http://$BUCKET_NAME.$PUBLIC_ENDPOINT/index.html
echo open http://$BUCKET_NAME.$PUBLIC_ENDPOINT/index.html

It will look like:

<html>
<head>
<title>Files hosted in Cloud Object Storage and accessible through a Content Delivery Network</title>
...
</html>
open http://fredflinstone-mywebsite.s3.us-south.cloud-object-storage.appdomain.cloud/index.html







 Step 4: Make the files globally available with a CDN 

In this section, you will create a CDN service. The CDN service distributes content to where it is needed. The first time content is requested, it’s pulled from the host server (your bucket in IBM Cloud Object Storage) to the delivery network and stays there for other users to access it quickly without the network latency to reach the host server again.



 Create a CDN instance 



1. Go to the catalog in the console, and select [Content Delivery Network](https://cloud.ibm.com/catalog/infrastructure/cdn-powered-by-akamai) from the Network section. This CDN is powered by Akamai. Click Create.

The Hostname has two purposes. It is a unique name that identifies the CDN instance. It can also be the [DNS subdomain](https://en.wikipedia.org/wiki/Subdomain). When filling out this form you will choose one of the following options:



1. To use a DNS subdomain in a domain that you control:



* Fill in the hostname as the DNS subdomain. For example if you control example.com then static.example.com would be a valid choice.
* Choose HTTP port if required by your application.
* Choose HTTPS port if required by your application and chose the SSL certificate DV SAN certificate.
* CDN Content will be available at your subdomain, static.example.com, for example.
When the list is filtered by subnet, the subnets that are displayed are subscribed subnets in the same data center as the storage volume.
4. Select one or more hosts from the list and click Save.



After the host is authorized, go to the File Storage for Classic Details page, and take note of the mount point information.





 Authorizing the host from the SLCLI 

You can authorize a host to access the File Storage for Classic volume by using the file access-authorize command.

 slcli file access-authorize --help
Usage: slcli file access-authorize [OPTIONS] VOLUME_ID

Options:
-h, --hardware-id TEXT The ID of one hardware server to authorize.
-v, --virtual-id TEXT The ID of one virtual server to authorize.
-i, --ip-address-id TEXT The ID of one IP address to authorize.
-p, --ip-address TEXT An IP address to authorize.
-s, --subnet-id TEXT An ID of one subnet to authorize.
--help Show this message and exit.





 Authorizing the host with Terraform 

To authorize a compute host to access the share, use the ibm_storage_file resource and specify the allowed_virtual_guest_ids for virtual servers, or allowed_hardware_ids for bare metal servers. Specify allowed_ip_addresses to define which IP addresses have access to the storage.

The following example defines that the Virtual Server with the ID 28961689 can access the volume from the 10.146.139.64/26 subnet, and 10.146.139.84 address.

resource "ibm_storage_file" "fs_endurance" {
type = "Endurance"
datacenter = "dal09"
capacity = 20
iops = 0.25

allowed_virtual_guest_ids = ["28961689"]
allowed_subnets = ["10.146.139.64/26"]
allowed_ip_addresses = ["10.146.139.84"]
snapshot_capacity = 10
hourly_billing = true
Consider using [Secrets Manager](https://cloud.ibm.com/docs/containers?topic=containers-secrets-mgr) to centrally manage and automatically update your Ingress subdomain certificates and other secrets.

Setting up Ingress with TLS certificates involves creating or importing secrets. If you want to use the IBM Cloud Ingress API to complete these steps, you must have a default Secrets Manager instance. Otherwise, you can use kubectl commands to copy your certificates.







 Getting started with Ingress 

When you are ready to use Ingress in your cluster, [create an Ingress resource](https://cloud.ibm.com/docs/containers?topic=containers-managed-ingress-setup) to configure your Ingress components, define rules for routing requests, and specify the path to app services. A separate Ingress resource is required for each namespace that contains an app or service that you want to expose.
You can use the cbr-zone-create command to add network locations, VPCs, and service references to network zones. For more information, see the CBR [CLI reference](https://cloud.ibm.com/docs/account?topic=account-cbr-plugincbr-zones-cli). Add Secrets Manager to network zones as a service reference to allow Secrets Manager to access resources and services in your account that are the subject of a rule.



1. To create network zones from the CLI, [install the CBR CLI plug-in](https://cloud.ibm.com/docs/cli?topic=cli-cbr-plugininstall-cbr-plugin).
2. Use the cbr-zone-create command to add resources to network zones. For more information, see the CBR [CLI reference](https://cloud.ibm.com/docs/cli?topic=cli-cbr-plugincbr-zones-cli). Note that the service_name for Secrets Manager is secrets-manager.



To find a list of available service references, run the ibmcloud cbr service-ref-targets[command](https://cloud.ibm.com/docs/account?topic=account-cbr-plugincbr-cli-service-ref-targets-command).

Example command to add the secrets-manager service to a network zone.

ibmcloud cbr zone-create --name example-zone-1 --description "Example zone 1" --service-ref service_name=secrets-manager







 Understanding rules 

After you create your zones, you can attach the zones to your network resources by creating rules. When you add resources to a rule, you can choose from the available [types of endpoints](https://cloud.ibm.com/docs/account?topic=account-context-restrictions-whatiscontext-restrictions-endpint-type) that are specific to your network topology.



 Create rules by using the API 

You can define rules with the API by using the information that you collected from creating network zones.
Configuring a Catalog 

You can create and configure your API Manager Catalogs in the Lite, Enterprise, and Hybrid plans.

Catalogs are useful for separating Products and APIs for testing before you make them available to Developer organizations. When you configure a Catalog, you can also configure custom branding so that you do not have to use the default API URL provided by the API Manager.

Complete the following steps to create your Catalog:



1. Click ![Navigate icon](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/images/navigate_to_icon.png) > Dashboard.
2. Click + Add > Catalog. The Add Catalog window is displayed.
3. Enter the name of your new Catalog in the Display Name field.
4. Enter the text that you want to form the Catalog segment of the URL, in the Name field. Note: The Name field can contain only lowercase alphanumeric characters (a-z and 0-9), or hyphen characters (-). A hyphen cannot be used as the first or last character in the name.
5. Click Add. Your Catalog is created, and is displayed on your dashboard.
6. To configure the Catalog, click the name of the Catalog, then click Settings > Info, and proceed with the following steps:

a. If the new Catalog is a development Catalog, select Development mode.

Development and Production catalogs behave differently:



* Development catalog:

If you select the development mode, staging and publishing actions are forced. If you republish a Product, it is overwritten without warning. If conflicts are found, they are automatically resolved by the system. Unpublish actions happen automatically.

Note: Approval boxes are not displayed for development Catalogs. You cannot enable the approval process for lifecycles.
* Production catalog: