Unable To Create Clusters With AWS Cloud Provider's Existing VPC
PreviousNodes Fluctuating Between Ready and NotReady State Due to Kernel Memory Leak IssueNextHorizontal Pod Autoscaler Shows Targets
Last updated
Unable to create Platform9 Managed Kubernetes cluster with AWS cloud provider's existing Virtual Private Cloud(VPC) configuration. It fails with either of the below message in the UI:
Error: At least one public and one private subnet is required when deploying a private cluster to an existing VPCError: At least one subnet is required when deploying a public cluster to an existing VPCPlatform9 Managed Kubernetes - All Versions
AWS VPC
We are aware that the AWS native PMK cluster creation fails when an existing VPC is used with combination:
Using existing VPC (Public + Private)
Using existing VPC (Public)
The issue is tracked in internal Jira UX-1140.
Last updated
