Closed D3N14L closed 2 years ago
Hi @D3N14L,
Thank you for raising this issue!
I've tested this, with apiSubnetAllowList deactivated from my account, and I receive an error when trying to create a cluster with this argument set.
│ Error: error creating k8s cluster: 422 Unprocessable Entity {
│ "httpStatus" : 422,
│ "messages" : [ {
│ "errorCode" : "439",
│ "message" : "[(root).properties.apiSubnetAllowList] The usage of 'apiSubnetAllowList' is not supported in your contract. Please contact support."
│ } ]
│ }
Could you test it again, maybe it was a temporary problem within the API, and see if it is reproducing? If it is still reproducing we will investigate further within the API to see why this is happening for you account.
Description
I tried to set an apiSubnetAllowList via the Terraform provider and it is correctly set in my state, but not on the actual cluster.
But access to the cluster API is still granted from "0.0.0.0/0". If I try to set the apiSubnetAllowList I get an error message:
Expected behavior
I would have expected an error message during the terraform apply, if I try to set an unsupported setting.
Environment
Terraform version:
Provider version:
How to Reproduce
Create a cluster with apiSubnetAllowList set with terraform.
Error and Debug Output
Additional Notes
References