New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
creating google_container_cluster with resource_usage_export_config fails #6814
creating google_container_cluster with resource_usage_export_config fails #6814
Comments
@rohitvyavahare I've just created a cluster using below code and it seems fine with me. Can you share your full debug log? resource "google_container_cluster" "primary" {
provider = google-beta
name = "issue6814-cluster"
location = "us-central1-a"
initial_node_count = 3
master_auth {
username = ""
password = ""
client_certificate_config {
issue_client_certificate = false
}
}
node_config {
oauth_scopes = [
"https://www.googleapis.com/auth/logging.write",
"https://www.googleapis.com/auth/monitoring",
]
metadata = {
disable-legacy-endpoints = "true"
}
labels = {
foo = "bar"
}
tags = ["foo", "bar"]
}
timeouts {
create = "30m"
update = "40m"
}
resource_usage_export_config {
enable_network_egress_metering = false
enable_resource_consumption_metering = true
bigquery_destination {
dataset_id = "cluster_resource_usage"
}
}
} |
@edwardmedia thank you for reply I tested again and found that if dataset_id is empty or "" in following config + resource_usage_export_config {
+ enable_network_egress_metering = true
+ enable_resource_consumption_metering = true
+ bigquery_destination {}
} |
@rohitvyavahare yes, by set |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks! |
Community Note
modular-magician
user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned tohashibot
, a community member has claimed the issue already.Terraform Version
Terraform v0.13.0-beta3
Affected Resource(s)
Terraform Configuration Files
Debug Output
Panic Output
https://gist.github.com/rohitvyavahare/c060deba2059de0105d92bd694a51499
Expected Behavior
Should create container cluster with resource_usage_export_config
Actual Behavior
Error: rpc error: code = Unavailable desc = transport is closing
Steps to Reproduce
Create container cluster with resource_usage_export_config
If we create a cluster without resource_usage_export_config , then it creates cluster and then if we add resource_usage_export_config then it successfully applies.
terraform apply
Important Factoids
References
The text was updated successfully, but these errors were encountered: