Cannot add VPC Peer to Qovery Cluster

INFORMATION

Relevant information to this issue:

ISSUE
Error: creating Route in Route Table (rtb-0281b21363d280037) with destination (10.17.0.0/16): InvalidParameterValue: The destination CIDR block 10.17.0.0/16 is equal to or more specific than one of this VPC’s CIDR blocks. This route can target only an interface or an instance.
status code: 400, request id: 553d2eec-2a77-4a3f-af78-de8db410b025

Describe your issue here
I’m attempting to add a peered connection to the Dev-Cluster per your docs here. After two attempted cluster updates qovery keeps telling me the CIDR block is “bigger” than my existing VPC’s CIDR Block… However, this is the CIDR block for my qovery-eks-workers VPC per this screenshot:

HOW TO REPRODUCE
Follow the steps in:

Hello,
the link you sent for the console is the root one. Could send me the one to your cluster page ?

Here is a link to the cluster page and link to the logs:
https://new.console.qovery.com/organization/e2b8fe3c-e171-4c81-8392-563e08c8270b/clusters/general

https://new.console.qovery.com/organization/e2b8fe3c-e171-4c81-8392-563e08c8270b/cluster/3b6f618e-0638-463e-92bd-791371847c06/logs

Hi @pantera-travis ,

From your cluster logs, The returned AWS message is:

creating Route in Route Table (rtb-0281b21363d280037) with destination (10.17.0.0/16): 
InvalidParameterValue: The destination CIDR block 10.17.0.0/16 is equal to or more specific
than one of this VPC's CIDR blocks. This route can target only an interface or an instance.

This is because your cluster subnet is 10.17.0.0/16, whereas the VPC peering route is 10.17.0.0/16 the same. The VPC route should point to the destination route and not its route range.

Update the route with the destination one, apply your changes with a redeployment, and all should be good :slight_smile:

Pierre

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.