Hey there 
We had an issue while trying to deploy our sandbox & staging clusters. We used the terraform provider with the current configuration:
resource "qovery_cluster" "cluster" {
organization_id = qovery_organization.organization.id
credentials_id = qovery_aws_credentials.aws_credentials.id
name = "Build Cluster"
cloud_provider = "AWS"
region = "eu-west-1"
instance_type = "t3a.medium"
kubernetes_mode = "K3S"
min_running_nodes = 1
max_running_nodes = 1
depends_on = [
qovery_organization.organization,
qovery_aws_credentials.aws_credentials
]
}
And later, tried to add a project associated with this cluster:
resource "qovery_environment" "qovery_sandbox_environment" {
project_id = qovery_project.project.id
name = "sandbox"
cluster_id = qovery_cluster.cluster.id
mode = "DEVELOPMENT"
depends_on = [
qovery_project.project
]
}
When planning the project creation, it seems like TF was trying to add a VPC Subnet even if it was not configured on our end:
And it did not worked:
Later on, I tried to recreate a cluster with the subnet configured but again, it failed with the same error message:
So… I guess there might be an issue with the terraform provider and the VPC subnet when the mode is K3S. Everything works well when the mode is MANAGED. For now, it’s OK but we would like to switch our sandbox & staging cluster to K3S as soon as possible.
Let me know if you need any more data.
Arthur