---
name: containers-ts-cluster-no-vpc
title: 'VPC: Why is no VPC available when I create a cluster in the console?'
description: '**Infrastructure provider**: VPC'
last-updated: 2025-09-26
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/containers?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# VPC: Why is no VPC available when I create a cluster in the console?
{: #ts_no_vpc}
{: support}

**Infrastructure provider**: VPC

You try to create a VPC cluster by using the [IBM Cloud Kubernetes Service console](https://cloud.ibm.com/containers/cluster-management/catalog/create){: external}.
{: tsSymptoms} 

You have an existing [VPC](https://cloud.ibm.com/vpc){: external} 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:
```sh
No VPC is available. Create a VPC.
```
{: screen}

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.
{: tsCauses}

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.
{: tsResolve}

1. 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 Administrator platform role in IBM Cloud Kubernetes Service and, if using a service ID, has the Operator platform role in the IAM Identity Service](https://cloud.ibm.com/docs/containers?topic=containers-iam-platform-access-roles&format=markdown).
    ```sh
    ibmcloud login [--sso]
    ```
    {: pre}

2. Target the `default` resource group.
    ```sh
    ibmcloud target -g default
    ```
    {: pre}

3. Set the API key for the region and resource group.
    ```sh
    ibmcloud ks api-key reset --region <region>
    ```
    {: pre}

4. In the [IBM Cloud Kubernetes Service console](https://cloud.ibm.com/containers/cluster-management/catalog/create){: external}, click **Refresh VPCs**. Your available VPCs are now listed in a drop-down menu.