vania-janet/multiturn-rag-retrieval-data huggingface dataset:
alb](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/container_vpc_alb)<br> * [ibm_container_vpc_cluster](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/container_vpc_cluster)<br> * [ibm_container_vpc_cluster_worker](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/container_vpc_cluster_worker)<br> * [ibm_container_vpc_cluster_worker_pool](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/container_vpc_cluster_worker_pool)<br> * [ibm_container_worker_pool](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/container_worker_pool)<br><br><br> 







 Object Storage 



 Resources Data sources
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
VPC myvpc(36c8f522-4f0d-400c-8226-299f0b8198cf)
5. Use the subnet to [create a cluster](https://cloud.ibm.com/docs/containers?topic=containers-cluster-create-vpc-gen2&interface=ui), [create a new worker pool](https://cloud.ibm.com/docs/containers?topic=containers-add_workersvpc_add_pool), or [add the subnet to an existing worker pool](https://cloud.ibm.com/docs/containers?topic=containers-add_workersvpc_add_zone). Do not delete the subnets that you attach to your cluster during cluster creation or when you add worker nodes in a zone. If you delete a VPC subnet that your cluster used, any load balancers that use IP addresses from the subnet might experience issues, and you might be unable to create new load balancers.









 Creating VPC subnets for classic access 

If you enable classic access when you create your VPC, [classic access default address prefixes](https://cloud.ibm.com/docs/vpc?topic=vpc-setting-up-access-to-classic-infrastructureclassic-access-default-address-prefixes) automatically determine the IP ranges of any subnets that you create. However, the default IP ranges for classic access VPC subnets conflict with the subnets for the IBM Cloud Kubernetes Service control plane.
* [Setting up block storage for your apps](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-block)
* [Backing up your internal image registry to IBM Cloud Object Storage](https://cloud.ibm.com/docs/openshift?topic=openshift-registrycos_image_registry)
* [Overview of the differences between classic and VPC clusters](https://cloud.ibm.com/docs/openshift?topic=openshift-infrastructure_providers)
* [VPC cluster limitations](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_limitationsks_vpc_gen2_limits)
* [About the v2 API](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_api_installapi_about)



Need help, have questions, or want to give feedback on VPC clusters? Try posting in the [Slack channel](https://cloud.ibm.com/kubernetes/slack).
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
VPC myvpc(36c8f522-4f0d-400c-8226-299f0b8198cf)
5. Use the subnet to [create a cluster](https://cloud.ibm.com/docs/containers?topic=containers-cluster-create-vpc-gen2&interface=ui), [create a new worker pool](https://cloud.ibm.com/docs/openshift?topic=openshift-add_workersvpc_add_pool), or [add the subnet to an existing worker pool](https://cloud.ibm.com/docs/openshift?topic=openshift-add_workersvpc_add_zone). Do not delete the subnets that you attach to your cluster during cluster creation or when you add worker nodes in a zone. If you delete a VPC subnet that your cluster used, any load balancers that use IP addresses from the subnet might experience issues, and you might be unable to create new load balancers.









 Creating VPC subnets for classic access 

If you enable classic access when you create your VPC, [classic access default address prefixes](https://cloud.ibm.com/docs/vpc?topic=vpc-setting-up-access-to-classic-infrastructureclassic-access-default-address-prefixes) automatically determine the IP ranges of any subnets that you create. However, the default IP ranges for classic access VPC subnets conflict with the subnets for the Red Hat OpenShift on IBM Cloud control plane. Instead, you must create the VPC without the automatic default address prefixes, and create your own address prefixes. Then, whenever you create subnets for your cluster, you create the subnets within the address prefix ranges that you created.



 Creating VPC subnets for classic access in the console
This release resolves various issues, includes several deprecations, and introduces new features, such as API tokens and edge static routes. For more information, see [VMware Cloud Director 10.4.1 release notes](https://docs.vmware.com/en/VMware-Cloud-Director/10.4.1/rn/vmware-cloud-director-1041-release-notes/index.html).

Multiple clusters support
: The limitation of one cluster per provider virtual data center (PVDC) is removed. For more information, see [Adding and deleting clusters](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-cluster-adding-deleting).

Virtual data centers without edge
: You can deploy virtual data centers (VDCs) without a network edge, which can help you save resources and costs by sharing an existing edge across multiple VDCs. This option is suitable for centralized networking administration and control over many VDCs. For more information, see [Adding virtual data centers](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-vdc-adding).





 18 January 2023 

Multizone support
: You can now create PVDCs across three data centers in the region. For more information, see [Ordering VMware as a Service instances](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-tenant-ordering) and [Adding and deleting PVDCs](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-pvdc-adding-deleting).

Add PVDC with new cluster
: Adding multiple PVDCs with new clusters is now supported, with a limitation of one cluster per PVDC. For more information, see [Adding and deleting PVDCs](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-pvdc-adding-deleting).

IAM enablement
Version 1.0.84 of the CLI was released on 26 May 2020.



* Fixes bugs for credentials in Kubernetes configuration contexts:



* When you download the contexts for clusters that run Kubernetes version 1.17 or later, those contexts are merged into your kubeconfig file. The tokens from the version 1.17 or later contexts now don't overwrite tokens for any version 1.16 or later contexts.
* Credentials are now correctly added to your kubeconfig file when you download the context for a cluster.
* Fixes credential issues for CLI plug-in installations on macOS that don't use cgo.



* Adds commands for creating and managing VPC clusters.



* [alb configure vpc-gen2](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clicli_alb_configure_vpc_gen2)
* [alb create vpc-gen2](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clicli_alb-create-vpc-gen2)
* [cluster create vpc-gen2](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clicli_cluster-create-vpc-gen2)
* [nlb-dns create vpc-gen2](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_nlb-dns-create-vpc-gen2)
* [nlb-dns rm vpc-gen2](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_nlb-dns-rm-vpc-gen2)
For more ideas of what to do with your cluster, review the [Next steps](https://cloud.ibm.com/docs/openshift?topic=openshift-clustersnext_steps).





 Example commands to create VPC clusters 

VPC Gen 2 cluster flavors with instance storage are available for allowlisted accounts. To get added to the allowlist, [open a case](https://cloud.ibm.com/unifiedsupport/cases/form) with support.

ibmcloud oc cluster create vpc-gen2 --name my_cluster --version 4.11_openshift --zone us-east-1 --vpc-id <VPC_ID> --subnet-id <VPC_SUBNET_ID> --cos-instance <COS_CRN>--flavor bx2.4x16 --workers 3

For a VPC multizone cluster, after you created the cluster in a [multizone metro](https://cloud.ibm.com/docs/openshift?topic=openshift-regions-and-zoneszones-vpc), [add zones](https://cloud.ibm.com/docs/openshift?topic=openshift-add_workersvpc_add_zone).

ibmcloud oc zone add vpc-gen2 --zone <zone> --cluster <cluster_name_or_ID> --worker-pool <pool_name> --subnet-id <VPC_SUBNET_ID>

VPC cluster provisioned at version 4.9 with worker nodes that run the RHEL 8 operating system. For a complete list of available RHEL versions and which cluster versions they are compatible with, see [Available Red Hat OpenShift versions](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_versionsopenshift_versions_available).
To get the CRN of an instance, run ibmcloud ks ingress instance ls --cluster CLUSTER. Include this option if you want to register a Secrets Manager instance to the cluster.

--pod-subnet
: In the first cluster that you create in a VPC, the default pod subnet is 172.17.0.0/18. In the second cluster that you create in that VPC, the default pod subnet is 172.17.64.0/18. In each subsequent cluster, the pod subnet range is the next available, non-overlapping /18 subnet. If you plan to connect your cluster to on-premises networks through IBM Cloud® Direct Link or a VPN service, you can avoid subnet conflicts by specifying a custom subnet CIDR that provides the private IP addresses for your pods. When you choose a subnet size, consider the size of the cluster that you plan to create and the number of worker nodes that you might add in the future. The subnet must have a CIDR of at least /23, which provides enough pod IP addresses for a maximum of four worker nodes in a cluster. For larger clusters, use /22 to have enough pod IP addresses for eight worker nodes, /21 to have enough pod IP addresses for 16 worker nodes, and so on. Note that the pod and service subnets can't overlap. If you use custom-range subnets for your worker nodes, [you must ensure that your worker node subnets don't overlap with your cluster's pod subnet](https://cloud.ibm.com/docs/containers?topic=containers-vpc-subnetsvpc-ip-range). The subnet that you choose must be within one of the following ranges:



* 172.17.0.0 - 172.17.255.255
* 172.21.0.0 - 172.31.255.255
* 192.168.0.0 - 192.168.254.255
* 198.18.0.0 - 198.19.255.255



--service-subnet
: All services that are deployed to the cluster are assigned a private IP address in the 172.21.0.0/16 range by default.
Notice the CIDR blocks do not overlap and VPCs all consume a CIDR block in each zone:



* The on-premises CIDR is 192.168.0.0/16.
* The zones in this [multi-zone region](https://cloud.ibm.com/docs/overview?topic=overview-locations) are 10.*.0.0/16. The second digit: 1, 2, 3 is the zone number (shown for Dallas/us-south):



* 10.1.0.0/16, zone 1, Dallas 1, us-south-1.
* 10.2.0.0/16, zone 2, Dallas 2, us-south-2.
* 10.3.0.0/16, zone 3, Dallas 3, us-south-3.



* The transit VPC consumes CIDRs 10.*.0.0/24:



* 10.1.0.0/24, zone 1.
* 10.2.0.0/24, zone 2.
* 10.3.0.0/24, zone 3.



* Spoke 0 consumes 10.*.1.0/24 or CIDRs:



* 10.1.1.0/24, zone 1.
* 10.2.1.0/24, zone 2.
* 10.3.1.0/24, zone 3.



* The zone box within a VPC shows the Address Prefix. In the transit for zone 1 this is 10.1.0.0/16 overlaps with the spokes and seems incorrect. CIDR 10.1.0.0/24 more accurately describes the transit VPC zone. This is a routing requirement that will be discussed in a later section.
* The subnet CIDRs further divide the /24 into /26.



The subnets in the transit and spoke are for the different resources:



* worker - network accessible compute resources VPC instances, load balancers, [Red Hat OpenShift](https://www.ibm.com/cloud/openshift), etc. VPC instances are demonstrated in this tutorial.
* dns - DNS Services location appliances used in part two.
Follow the steps in [Creating VPC subnets for classic access](https://cloud.ibm.com/docs/containers?topic=containers-vpc-subnetsca_subnet_cli) to create a classic-enabled VPC and VPC subnets without the automatic default address prefixes.
3. [Create a subnet for your VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-vpc-resources-with-cli-and-api&interface=clicreate-a-subnet-cli).



* If you want to create a [multizone cluster](https://cloud.ibm.com/docs/containers?topic=containers-ha_clustersmz-clusters), repeat this step to create additional subnets in all the zones that you want to include in your cluster.
* VPC subnets provide IP addresses for your worker nodes and load balancer services in the cluster, so [create a VPC subnet with enough IP addresses](https://cloud.ibm.com/docs/containers?topic=containers-vpc-subnetsvpc_basics_subnets), such as 256. You can't change the number of IPs that a VPC subnet has later.
* Do not use the following reserved ranges: 172.16.0.0/16, 172.18.0.0/16, 172.19.0.0/16, and 172.20.0.0/16.
* If worker nodes must access public endpoints, [attach a public gateway](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-vpc-resources-with-cli-and-api&interface=cliattach-public-gateway-cli) to each subnet.
* Important: Do not delete the subnets that you attach to your cluster during cluster creation or when you add worker nodes in a zone. If you delete a VPC subnet that your cluster used, any load balancers that use IP addresses from the subnet might experience issues, and you might be unable to create new load balancers.
: Added information about [health reporting for your Ingress components](https://cloud.ibm.com/docs/containers?topic=containers-ingress-status).

NodeLocal DNS cache
: Added how to customize the [NodeLocal DNS cache](https://cloud.ibm.com/docs/containers?topic=containers-cluster_dnsdns_nodelocal_customize).

Version change logs
: Master and worker node change log documentation is available.
: Kubernetes [1.18.3_1514](https://cloud.ibm.com/docs/containers?topic=containers-118_changelog1183_1514), [1.17.6_1526](https://cloud.ibm.com/docs/containers?topic=containers-117_changelog1176_1526), [1.16.10_1533](https://cloud.ibm.com/docs/containers?topic=containers-116_changelog11610_1533), [1.15.12_1540](https://cloud.ibm.com/docs/containers?topic=containers-115_changelog11512_1540), and [1.14.10_1555](https://cloud.ibm.com/docs/containers?topic=containers-114_changelog11410_1555).





 20 May 2020 

New! Virtual Private Cloud Generation 2
: You can now create standard Kubernetes clusters in your [Gen 2 Virtual Private Cloud (VPC)](https://cloud.ibm.com/docs/vpc?topic=vpc-getting-started). VPC gives you the security of a private cloud environment with the dynamic scalability of a public cloud.
: For more information, check out the following links.



* [Overview of Classic and VPC infrastructure providers](https://cloud.ibm.com/docs/containers?topic=containers-infrastructure_providers)
: For more information, see [the change log](https://cloud.ibm.com/docs/openshift?topic=openshift-versions-vpc-file-addon).

Block Storage for VPC add-on versions 5.0.12_1963 and 5.1.8_1970.
: For more information, see [the change log](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc_bs_changelog).





 10 May 2023 

Create Classic and VPC clusters with Terraform
: For more information, see [Creating a single-zone classic cluster with Terraform](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster-create-classic&interface=terraformcluster_classic_tf) and [Creating a VPC cluster with Terraform](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster-create-vpc-gen2&interface=terraformcluster_vpcg2_tf).





 9 May 2023 

Worker node fix packs 4.9.59_1588_openshift, 4.10.59_1566_openshift, 4.11.39_1554_openshift, and 4.12.15_1542_openshift.
: For more information, see the change logs: [4.9](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_49), [4.10](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_410), [4.11](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_411), and [4.12](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_412).





 5 May 2023 

New!
Asia Pacific Singapore Singapore sng-mtr sng01 AP North (ap-north, jp-tok) 
 Europe Italy Milan it-mil mil01 EU Central (eu-central, eu-de) 
 Europe Netherlands Amsterdam nl-ams ams03 EU Central (eu-central, eu-de) 
 North America Canada Montreal ca-mon mon01 US East (us-east) 
 North America Canada Toronto ca-tor tor01 US East (us-east) 
 North America United States San Jose us-sjc sjc03, sjc04 US South (us-south) 
 South America Brazil Sao Paulo br-sao sao01 US South (us-south) 







 VPC multizone regions 

VPC resources are provisioned in a region, which is a separate group of zones within a metro. The zones are mapped to separate data centers to ensure that resources are distributed evenly across zones in a multizone architecture. In the API and CLI, zones use the regional zone name in the API and command line (us-south-1), but in the console, zones use by the data center location (Dallas 1). For the data center code that the VPC zone and location corresponds to, such as us-south-1 and DAL10, see [Multizone regions](https://cloud.ibm.com/docs/overview?topic=overview-locationstable-mzr).



Available multizone metro locations for VPC clusters in Red Hat OpenShift on IBM Cloud.

 Geography Country Metro Region Zones 

 Asia Pacific Australia Sydney au-syd au-syd-1, au-syd-2, au-syd-3 
 Asia Pacific Japan Osaka jp-osa jp-osa-1, jp-osa-2, jp-osa-3 
 Asia Pacific Japan Tokyo jp-tok jp-tok-1, jp-tok-2, jp-tok-3 
 Europe Germany Frankfurt eu-de eu-de-1, eu-de-2, eu-de-3 
 Europe United Kingdom London eu-gb eu-gb-1, eu-gb-2, eu-gb-3
Public Service Endpoint URL: https://c2.us-south.containers.cloud.ibm.com:20267
Private Service Endpoint URL: https://c2.private.us-south.containers.cloud.ibm.com:20267
Pull Secrets: enabled in the default namespace
VPCs: ff537d43-a5a4-4b65-9627-17eddfa5237b
...
2. For the worker zones and VPC that you found, ensure that you [enabled a public gateway on the VPC subnets in each worker zone](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-vpc-resources-with-cli-and-api&interface=cliattach-public-gateway-cli).
3. List the public gateways for the subnets. In the output, for the zones and VPC that your cluster is in, note the gateway Floating IP addresses for the subnets.

ibmcloud is public-gateways

Example output

ID Name Status Floating IP VPC Zone
5d308ea5-9f32-43b3-aaae-194d5723a3e5 pgw-b9d45630-c053-11e9-b2f8-79328ce05e7e available 169.XX.XXX.XX test-vpc us-south-1
f8b95e43-a408-4dc8-a489-ed649fc4cfec pgw-18a3ebb0-b539-11e9-9838-f3f4efa02374 available 169.XX.XXX.XX prod us-south-1
2ba9a280-fffa-4b0c-bdca-7970f09f9b8a pgw-73b62bc0-b53a-11e9-9838-f3f4efa02374 available 169.XX.XXX.XX prod us-south-2
To find the CRN of an instance, run [ibmcloud oc ingress instance ls --cluster CLUSTER](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_ingress_instance_ls).

--secondary-storage STORAGE
: Optional: The storage option for the flavor. For example, 900gb.5iops-tier. When you add a secondary disk, that disk is used for the container runtime, while the primary disk is used for the operating system. To view the storage options for a flavor, run the ibmcloud oc flavor get --flavor FLAVOR --zone ZONE --provider vpc-gen2 command.

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



 Example cluster create vpc-gen2 command 

ibmcloud oc cluster create vpc-gen2 --name mycluster --version 4.11_openshift --zone us-south-1 --vpc-id a0123456-78b9-0c1d-23d4-567890123ef4 --subnet-id 1ab23c45-6789-0123-456d-789ef01gh234 --flavor bx2.4x16 --workers 3







 ibmcloud oc cluster get 

Virtual Private Cloud

Classic infrastructure

View the details of a cluster.

ibmcloud oc cluster get --cluster CLUSTER [--show-resources] [--output json] [-q]

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

Command options:

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

--show-resources
: Show more cluster resources such as add-ons, VLANs, subnets, and storage.

--output json
: Optional: Prints the command output in JSON format.

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



 Example cluster get command
: With the latest version of the cluster autoscaler, you can [enable autoscaling for worker pools during the Helm chart installation](https://cloud.ibm.com/docs/containers?topic=containers-cluster-scaling-helm) instead of modifying the config map after installation.

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





 23 August 2019 

App networking in VPC
: Updated the [Planning in-cluster and external networking for apps](https://cloud.ibm.com/docs/containers?topic=containers-cs_network_planning) topic with information for planning app networking in a VPC cluster.

Istio in VPC
: Updated the [managed Istio add-on](https://cloud.ibm.com/docs/containers?topic=containers-istio) topic with information for using Istio in a VPC cluster.

Remove bound services from cluster
: Added instructions for how to remove an IBM Cloud service that you added to a cluster by using service binding. For more information, see [Removing a service from a cluster](https://cloud.ibm.com/docs/containers?topic=containers-service-bindingunbind-service).





 20 August 2019 

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





 19 August 2019 

New! Virtual Private Cloud
: You can create standard Kubernetes clusters on classic infrastructure in the next generation of the IBM Cloud platform, in your Virtual Private Cloud. VPC gives you the security of a private cloud environment with the dynamic scalability of a public cloud.
Specify the zone, dedicated host pool, and flavor.

ibmcloud ks dedicated host create --zone us-south --pool a1a1a1a1a --flavor bx2d.host.16x64
5. Verify that the dedicated host was created. If the dedicated host is in the create_pending state, wait a few minutes for it to reach the created state.

ibmcloud ks dedicated host ls --pool a1a1a1a1a

Example output.

ID Zone Flavor State
aaaaa-aa-a1aaa1111aaa1aaa1a11-aaaaaaa1-a1aaaa1a us-south bx2d.host.16x64 created
6. Gather the details required to create a cluster.



1. List available subnets and note which one you want to use for the cluster.

ibmcloud is subnets

Example output.

ID Name Status Subnet CIDR Addresses ACL Public Gateway VPC Zone Resource group
1111-a11aaaa1-1a11-1111-1a1a-aaaaa1111111 a1a1a1a1 available xx.xxx.x.x/xx xxx/xxx xxxx-xxxx-xxxx-xxxx pgw-a1a1a1a1a1a1a my_vpc us-east-1 default
2. List available VPCs and note which one you want to use to create the cluster.

ibmcloud ks vpcs

Example output.

Name ID Provider
my_vpc a111-11a111a1-11a1-1a11-11a1-a1a1111a11a1 vpc-gen2
3. List available zones and note which one you want to create the cluster in.

ibmcloud ks zones --provider vpc-gen2

Example output.

ID Name Metro Flavors
us-east-1 us-east-1 Washington D.C. -
us-east-2 us-east-2 Washington D.C. -
us-east-3 us-east-3 Washington D.C. -
us-south-1 us-south-1 Dallas -