Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave +1 or me too comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
If an issue is assigned to a user, that user is claiming responsibility for the issue.
Customers working with a Google Technical Account Manager or Customer Engineer can ask them to reach out internally to expedite investigation and resolution of this issue.
Description
The control_plane_endpoints_config option was recently added to google_container_cluster. It would be nice if the examples showed how to use it! It's a bit confusing particularly for "endpoint - (Output) The cluster's DNS endpoint." as that doesn't seem like something that is actually set by the user but an output instead.
The control_plane_endpoints_config block supports:
dns_endpoint_config - (Optional) DNS endpoint configuration.
The control_plane_endpoints_config.dns_endpoint_config block supports:
endpoint - (Output) The cluster's DNS endpoint.
allow_external_traffic - (Optional) Controls whether user traffic is allowed over this endpoint. Note that GCP-managed services may still use the endpoint even if this is false.
Note: We may want more thorough GKE examples in general, the current ones mostly cover the opinions Terraform has on node pool attachment and nothing else but basic configuration
Community Note
Description
The
control_plane_endpoints_config
option was recently added togoogle_container_cluster
. It would be nice if the examples showed how to use it! It's a bit confusing particularly for "endpoint - (Output) The cluster's DNS endpoint." as that doesn't seem like something that is actually set by the user but an output instead.New or Affected Resource(s)
Potential Terraform Configuration
N/A
References
b/381887394