vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* [Increasing the number of ALB pod replicas](https://cloud.ibm.com/docs/containers?topic=containers-ingress-alb-managealb_replicas)
* [Disabling ALBs](https://cloud.ibm.com/docs/containers?topic=containers-ingress-alb-managealb-disable)



* [Moving ALBs across VLANs in classic clusters](https://cloud.ibm.com/docs/containers?topic=containers-ingress-alb-managemigrate-alb-vlan)



[Creating your own Ingress domain](https://cloud.ibm.com/docs/containers?topic=containers-ingress-domainsingress-domains)



* [Setting up domains with the IBM Cloud internal provider](https://cloud.ibm.com/docs/containers?topic=containers-ingress-domainsingress-domain-int)
* [Setting up domains with IBM Cloud Internet Services](https://cloud.ibm.com/docs/containers?topic=containers-ingress-domainsingress-domain-cis)



* [Set up service-to-service authorization](https://cloud.ibm.com/docs/containers?topic=containers-ingress-domainsingress-domain-cis-s2s)
* [Create a domain](https://cloud.ibm.com/docs/containers?topic=containers-ingress-domainsingress-domain-cis-create)



* [Setting up domains from other external providers](https://cloud.ibm.com/docs/containers?topic=containers-ingress-domainsingress-domain-external)



* [Set up credentials for your provider](https://cloud.ibm.com/docs/containers?topic=containers-ingress-domainsingress-domains-ext-cred)
* [Create a domain, or add an existing domain](https://cloud.ibm.com/docs/containers?topic=containers-ingress-domainsingress-domains-ext-create)
For more information, see the [Kubernetes documentation](https://kubernetes.io/docs/concepts/services-networking/).
4. Create the service in your cluster.

oc apply -f myloadbalancer.yaml



3. Verify that the NLB service was created successfully. It might take a few minutes for the NLB service to be created properly and for the app to be available.

oc describe service myloadbalancer

Example CLI output:

NAME: myloadbalancer
Namespace: default
Labels: <none>
Selector: app=liberty
Type: LoadBalancer
Zone: dal10
IP: 172.21.xxx.xxx
LoadBalancer Ingress: 169.xx.xxx.xxx
Port: <unset> 8080/TCP
NodePort: <unset> 32040/TCP
Endpoints: 172.30.xxx.xxx:8080
Session Affinity: None
Events:
FirstSeen LastSeen Count From SubObjectPath Type Reason Message
--------- -------- ----- ---- ------------- ---- ------ -------
10s 10s 1 {service-controller } Normal CreatingLoadBalancer Creating load balancer
10s 10s 1 {service-controller } Normal CreatedLoadBalancer Created load balancer

The LoadBalancer Ingress IP address is the portable IP address that was assigned to your NLB service.
4. If you created a public NLB, access your app from the internet.



1. Open your preferred web browser.
2. Enter the portable public IP address of the NLB and port.

http://169.xx.xxx.xxx:8080



5. To achieve high availability, repeat the steps 2 - 4 to add an NLB 2.0 in each zone where you have app instances.
6.
Create a namespace to which you install the operator.

oc new-project grafana
2. From the web interface of your Red Hat OpenShift on IBM Cloud cluster switch to the grafana project.
3. From the web interface, select Operators -> OperatorHub and find Grafana Operator (community).
4. Click Continue to accept the disclaimer and then click Install.
5. Keep the configuration as is and make sure that the Installed Namespace is grafana.



2. Apply the following Grafana resource. The settings are configurable.

apiVersion: integreatly.org/v1alpha1
kind: Grafana
metadata:
name: grafana
namespace: grafana
spec:
dataStorage:
accessModes:
- ReadWriteOnce
class: ibmc-vpc-block-metro-10iops-tier
size: 10Gi
config:
auth:
disable_signout_menu: false
auth.anonymous:
enabled: false
log:
level: warn
mode: console
security:
admin_password: secret
admin_user: root
tolerations:
- key: "logging-monitoring"
operator: "Equal"
value: "node"
effect: "NoExecute"
ingress:
enabled: true
dashboardLabelSelector:
- matchExpressions:
- key: app
operator: In
values:
- grafana
Show more
3. Wait for all pods in the Grafana namespace to be in Running state.
4. Log in to the Grafana instance. The default username and password is root/secret. After you are logged in, change the password. You can locate the route by using the following command:

oc get route
5. [Add Grafana users](https://grafana.com/tutorials/create-users-and-teams/).
6.
With Red Hat OpenShift on IBM Cloud, you have [a mix of flavors](https://cloud.ibm.com/docs/openshift?topic=openshift-planning_worker_nodesplanning_worker_nodes) that you can deploy: from bare metal for intensive workloads to virtual machines for rapid scaling. Use labels or namespaces to organize deployments to your machines. When you create a deployment, limit it so that your app's pod deploys only on machines with the best mix of resources. For example, you might want to limit a database application to a bare metal machine with a significant amount of local disk storage like the md1c.28x512.4x4tb.





 Set up multiple namespaces when you have multiple teams and projects that share the cluster 

Namespaces are kind of like a cluster within the cluster. They are a way to divide up cluster resources by using [resource quotas](https://kubernetes.io/docs/concepts/policy/resource-quotas/) and [default limits](https://kubernetes.io/docs/tasks/administer-cluster/manage-resources/memory-default-namespace/). When you make new namespaces, be sure to set up proper [RBAC policies](https://cloud.ibm.com/docs/openshift?topic=openshift-usersrbac) to control access. For more information, see [Share a cluster with namespaces](https://kubernetes.io/docs/tasks/administer-cluster/namespaces/) in the Kubernetes documentation.

If you have a small cluster, a couple dozen users, and resources that are similar (such as different versions of the same software), you probably don't need multiple namespaces. You can use labels instead.





 Set resource quotas so that users in your cluster must use resource requests and limits 

To ensure that every team has the necessary resources to deploy services and run apps in the cluster, you must set up [resource quotas](https://kubernetes.io/docs/concepts/policy/resource-quotas/) for every namespace.
The workspace location does not have to match the resource location.
* Select Next.



6. Select Create to create your workspace. The files from the GitHub repo are loaded in to Schematics. It can take several minutes for the files to load.
7. On the workspace Settings page, in the Input variables section, review the default input variables and provide values that match your solution. Some parameters have default values. Make sure to mark as “sensitive” the parameters that contain sensitive information like API keys. The values that you must specify include:



 Component type Parameter values needed 

 User-specific information <br><br> * API key<br> * SSH key name. For example, "ibmcloud_ssh_key_name1,ibmcloud_ssh_key_name2,..."<br> * Resource Group<br> * IP address. Enter the IP address in the format: "public_ip_address1/32,public_ip_address2/32,...". For example, "103.42.91.78/32"<br> * Your local machine OS<br> * Prefix to add to resource names<br><br><br> 
 Region Regions where resources are deployed 
 Image ID to use for region VSIs -Bastion Server<br><br><br><br> * App Server<br> * Web Server<br> * Db Server <br> Images are region-specific. To find the image IDs for your region, open the IBM Cloud shell and enter ibmcloud target -r < region_name > to set your region, then ibmcloud is images to see a list of images for that region.<br><br><br> 
 Load Balancer <br><br> * Domain Name<br> * Region Code<br><br><br> 
 Auto scale App VSI parameters <br><br> * Min server<br> * Max servers<br> * CPU threshold<br><br><br>
* UI
* CLI
* API







 Creating a workspace 

With IBM Cloud® Schematics workspaces, you can manage the Terraform-based templates to create and manage IBM Cloud resources. A workspace allows you to view and update configuration properties, view the list of resources that are provisioned through the workspace, and clean up resources if and when needed.



 Creating a workspace using the UI 



1. Go to [Schematics, IBM Cloud’s deployment manager](https://cloud.ibm.com/schematics), select Workspaces, and then select Create workspace.
2. In the Specify template section:



* Provide your GitHub, GitLab, or Bitbucket repository URL where your Terraform files reside. The Slurm repository is provided by IBM Cloud in this [public GitHub repository](https://github.com/IBM-Cloud/hpc-cluster-slurm).
* If you are using a private GitHub repository, provide your personal GitHub access token.
* Select the version of the Terraform engine that's used in the Schematics workspace, and then click Next.



3. In the Workspace details section:



* Specify the name for your Schematics workspace.
* Define any tags that you want to associate with the resources provisioned through the offering. The tags can later be used to query the resources in the IBM Cloud console.
* Select a resource group.
* Select a location. The location determines where the workspace actions are run.
* Provide a description (optional) of the Schematics workspace.
* Click Next and then click Create. The Schematics workspace is created with the name that you specified.



4. Go to Schematic Workspace Settings, and in the variable section, click "burger icons" to update the following parameters:



* Update api_key with the API key value. Mark it as sensitive to hide the API key in the IBM Cloud console.
The following example shows sample output from the ibmcloud resource service-instances --service-name functions command.

Name Location State Type
playground us-south active service_instance





 How do I see the Cloud Functions entities in my namespace? 

You can see a list of your Cloud Functions entities by running the [namespace get](https://cloud.ibm.com/docs/openwhisk?topic=cloud-functions-cli-plugin-functions-clicli_namespace_get) command. Replace <namespace_name> or <namespace_id> with the name or ID of your namespace.

ibmcloud fn namespace get <namespace_name> or <namespace_id>







 Creating an IAM-based namespace 

You can create an IAM-managed namespace as part of a resource group and manage access policies for your resources by targeting the resource group when a namespace is created. If you have other users that require access to your namespace, or if you want to access other resources from your namespace's actions, be sure that you set IAM policies after your namespace is created.

If you are creating a namespace in a resource group of an account that is not your own, you must have the Administrator Platform access role for Cloud Functions. Account owners have the Administrator role by default. For more information, see [Platform management roles](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-iamiam_platform_roles).

If you are an Administrator and want to allow other users to create namespaces, see [How do I set IAM policies so that others can create namespaces in my account?](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-iamiam_namespace_policies).



 Creating an IAM-based namespace from the console 

Create your IAM-based namespace by using the console.



1. From the [Cloud Functions console](https://cloud.ibm.com/functions) namespace menu, select Create namespace.
2.
* [Before you begin](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_tutorial_workflowregistry_tutorial_workflow_prereqs)
* [From code to a running container](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_tutorial_workflowregistry_tutorial_workflow_code_run)



* [Create a namespace](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_tutorial_workflowregistry_tutorial_workflow_create_namespace)
* [Build and push an image](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_tutorial_workflowregistry_tutorial_workflow_build_push_image)
* [Deploy a container that uses your image](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_tutorial_workflowregistry_tutorial_workflow_deploy)



* [Secure your images and clusters](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_tutorial_workflowregistry_tutorial_workflow_secure)



* [View the vulnerability report for your image](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_tutorial_workflowregistry_tutorial_workflow_vulnerability_report)
* [Enforce security in your cluster](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_tutorial_workflowregistry_tutorial_workflow_enforce_security)
* [Resolve vulnerabilities in your image](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_tutorial_workflowregistry_tutorial_workflow_resolve_vulnerabilities)
The scope can be the account, [namespace](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_namespace), [repository](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_repository), [digest](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_digest), or [tag](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_tag).

You can identify the images in the scope by using either the tag or the digest. You can reference the image by digest <dns>/<namespace>/<repo>@<digest>, which affects the digest and all its tags in the same repository, or by tag <dns>/<namespace>/<repo>:<tag>. Where <dns> is the domain name, <namespace> is the namespace, <repo> is the repository, <digest> is the digest, and <tag> is the tag. To list all images, including [untagged](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_untagged) images, run the [ibmcloud cr image-digests](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_image_digests) command.

ibmcloud cr exemption-add --scope SCOPE --issue-type ISSUE_TYPE --issue-id ISSUE_ID



 Prerequisites 

To find out about the required permissions, see [Access roles for configuring Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-iamaccess_roles_configure).





 Command options 

--scope SCOPE
: To set your account as the scope, use "" as the value.
* [Namespace API methods](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_at_iamregistry_at_iam_reg_namespace)
* [Plan API methods](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_at_iamregistry_at_iam_reg_plans)
* [Quota API methods](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_at_iamregistry_at_iam_reg_quota)
* [Retention API methods](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_at_iamregistry_at_iam_reg_retention)
* [Settings API methods](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_at_iamregistry_at_iam_reg_set)
* [Tag API methods](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_at_iamregistry_at_iam_reg_tags)
* [Trash API methods](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_at_iamregistry_at_iam_reg_trash)



* [Vulnerability Advisor API methods](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_at_iamregistry_at_iam_vuln)



* [Report API methods](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_at_iamregistry_at_iam_vuln_report)
* [Exemption API methods](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_at_iamregistry_at_iam_vuln_exempt)









 Container Registry CLI
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).





1. Create a Terraform configuration file that is named main.tf. In this file, you add the configuration to create a VLAN service instance and to assign a user an access policy in Identity and Access Management (IAM) for that instance by using HashiCorp Configuration Language (HCL). For more information, see the [Terraform documentation](https://www.terraform.io/docs/language/index.html).

The VLAN resource in the following example is named test_vlan. This PUBLIC VLAN resides in the sjc04 data center and fcr01a.sjc04 is the hostname of the primary router associated with the VLAN.

For more information, see the [ibm_network_vlan](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/network_vlan) usage example.

resource "ibm_network_vlan" "test_vlan" {
name = "test_vlan"
datacenter = "sjc04"
type = "PUBLIC"
router_hostname = "fcr01a.sjc04"
tags = [
"collectd",
"mesos-master",
]
}
2. After you finish building your configuration file, initialize the Terraform CLI.
Navigate to [Create Schematics Workspaces](https://cloud.ibm.com/schematics/workspaces/create?repository=https://github.com/IBM-Cloud/vpc-tutorials/tree/master/vpc-site2site-vpn&terraform_version=terraform_v1.2) Under the Specify Template section, verify:



1. Repository URL is https://github.com/IBM-Cloud/vpc-tutorials/tree/master/vpc-site2site-vpn
2. Terraform version is terraform_v1.2



3. Under Workspace details,



1. Provide a workspace name : vpnsts.
2. Choose a Resource Group and a Location.
3. Click on Next.



4. Verify the details and then click on Create.
5. Under the Variables section, provide the required values (resource_group_name, ssh_key_name) by clicking the overflow menu and selecting Edit for each row. The value for the variable maintenance must be set to true.
6. Scroll to the top of the page and click Apply plan. Check the logs to see the status of the services created.



Explore the resources that were created by clicking below and selecting the instance with matching prefix. Locate all of the resources in the diagram above.



* [IBM Cloud VPC](https://cloud.ibm.com/vpc-ext/network/vpcs)
* [Virtual Servers for VPC](https://cloud.ibm.com/vpc-ext/compute/vs)
* [IBM® VPN](https://cloud.ibm.com/vpc-ext/network/vpngateways)
* [VPE for VPC](https://cloud.ibm.com/vpc-ext/network/endpointGateways)
* [Databases for PostgreSQL instance in Databases](https://cloud.ibm.com/resources)
: The wsk client KEY. This flag is optional.

--namespaceNAMESPACE
: An IAM namespace name or ID. This flag cannot be set for Cloud Foundry namespaces. This flag is optional.





 Example 

ibmcloud fn property set --namespace myNamespace

Output

ok: whisk namespace set to myNamespace







 ibmcloud fn property unset 

Unset a property for the wsk CLI. At least one flag is required.

If properties are retained after running the property unset command, you can delete the config.json file located at <home_dir>/.bluemix/plugins/cloud-functions/config.json to remove all properties.

ibmcloud fn property unset [--apihost HOST] [--apiversion VERSION] [--auth KEY] [--cert STRING] [--key STRING] [--namespace NAMESPACE]



 Command options 

--apihostHOST
: The wsk API host. This flag is optional.

--apiversionVERSION
: The wsk API version. This flag is optional.

--authKEY, -u
: The wsk authorization KEY. This flag is optional.

--certSTRING
: The wsk client certificate. This flag is optional.

--keySTRING
: The wsk client KEY. This flag is optional.

--namespaceNAMESPACE
: An IAM namespace name or ID. This flag cannot be set for Cloud Foundry namespaces. This flag is optional.





 Example 

ibmcloud fn property unset --namespace









 Rule commands 

Create, delete, enable, disable, update, and find information about rules.

To see CLI help for the rule command, run ibmcloud fn rule.



 ibmcloud fn rule create 

Create a rule to associate a trigger with an action. Before you can create a rule, create a trigger and an action first.
[Install the operator in the openshift-operators namespace](https://cloud.ibm.com/docs-content/v1/content/c5288bed34c3820e3a5251d820ee91adcd2591a3/blockchain/images/allnamespace-install-operator.png)

Figure 1. Install the operator in the openshift-operators namespace
8. The Console and Fabric components can be installed in any namespace.

Zoom

![Console and Fabric components can be installed in any namespace](https://cloud.ibm.com/docs-content/v1/content/c5288bed34c3820e3a5251d820ee91adcd2591a3/blockchain/images/allnamespace-installed-operators.png)

Figure 2. Console and Fabric components can be installed in any namespace
9. Next, update the Security Context Constraint command settings to use the Fabric and Console namespaces.

Zoom

![Update Security Context Constraint command settings to use the Fabric and Console namespaces.](https://cloud.ibm.com/docs-content/v1/content/c5288bed34c3820e3a5251d820ee91adcd2591a3/blockchain/images/allnamespace-ibp-consoles.png)

Figure 3. Update Security Context Constraint command settings to use the Fabric and Console namespaces.
10. If your OpenShift cluster is behind a firewall, see [Deploy from Red Hat Marketplace (airgap installation)](https://cloud.ibm.com/docs/blockchain-sw-254?topic=blockchain-sw-254-deploy-ocp-rhm-fw).
11. Continue to [Step one: Apply the Security Context Constraint](https://cloud.ibm.com/docs/blockchain?topic=blockchain-deploy-ocp-rhmdeploy-ocp-rhm-scc).
If you are using the [public repository](https://github.com/IBM-Cloud/hpc-cluster-symphony) that is provided by IBM Cloud, then set this variable as template_repo_request_model['url'] = 'https://github.com/IBM-Cloud/hpc-cluster-symphony'; otherwise, set it to the private repository you are using.



4. Inside the schematics_service.create_workspace function, provide the following parameters:



* Provide an optional description.
* Provide a name to identify your Schematics workspace, for example, terraform-dev-workspace.
* Change the type parameter to the Terraform version that you are using to create IBM Cloud resources, for example, terraform_v0.14.
* Change the location to a region where your Schematics workspace needs to be created, for example, us-south.
* Change the resource group to the resource group where your resources should be grouped, for example, Default for a default resource group.
* If you are using a private GitHub repository, provide your personal GitHub access token that you set up in [Setting up the IBM Cloud Schematics API](https://cloud.ibm.com/docs/hpc-spectrum-symphony?topic=hpc-spectrum-symphony-setting-up-api&interface=api) prerequisites in the x_github_token= "<github-api-token>" parameter. If you are using the public repository that is provided by IBM Cloud, you do not need to specify this parameter.
* Optional: Provide the tags if you want to filter resources by using the tag.



5. Run the Python script by using python3 <python-file-name> to create a Schematics workspace in the IBM Cloud.
6. You get a successful response if the parameters passed as part of the request are valid and you should be able to see the Schematics workspace that you created in the IBM Cloud console. If you don’t get a successful response, the error response contains the errors that you need to resolve.