VPC: Why is no VPC available when I create a cluster in the console?

Infrastructure provider: VPC

You try to create a VPC cluster by using the IBM Cloud Kubernetes Service console.

You have an existing VPC in your account, but when you try to select an existing Virtual Private Cloud to create the cluster in, you see the following error message:

No VPC is available. Create a VPC.

During cluster creation, the IBM Cloud Kubernetes Service console uses the API key that is set for the default resource group to list the VPCs that are available in your IBM Cloud account.

If no API key is set for the default resource group, no VPCs are listed in the IBM Cloud Kubernetes Service console, even if your VPC exists in a different resource group and an API key is set for that resource group.

To set an API key for the default resource group, use the IBM Cloud Kubernetes Service CLI.

Log in to the command line as the account owner. If you want a different user than the account owner to set the API key, first ensure that the API key owner has the correct permissions.
```
ibmcloud login [--sso]
```
Target the default resource group.
```
ibmcloud target -g default
```
Set the API key for the region and resource group.
```
ibmcloud ks api-key reset --region <region>
```
In the IBM Cloud Kubernetes Service console, click Refresh VPCs. Your available VPCs are now listed in a drop-down menu.