You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The value makes it hard to use the cluster in the Anthos or GKE UI to configure ACM or even delete the membership later.
Community Note
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 the 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 to hashibot, a community member has claimed the issue already.
Terraform Version
Affected Resource(s)
google_gke_hub_membership
Terraform Configuration Files
## content from the example in the markdown fileresource"google_gke_hub_membership""membership" {
membership_id="basic"endpoint {
gke_cluster {
resource_link="//container.googleapis.com/${google_container_cluster.primary.id}"
}
}
description="test resource."### THIS IS PROBLEMATICprovider=google-beta
}
Debug Output
It actually "works" ok, you just cant use the resulting cluster for ACM or similar.
Expected Behavior
Just change to have a name that can be part of a resource and make docs to this effect and/or have validation, ideally.
Actual Behavior
Steps to Reproduce
follow the instructions, then try to configure a feature like ACM in the UI.
@linde I am not clear what is wrong. After running below plan, I can verify the cluster has been registered by executing gcloud beta container hub memberships describe basic Can you provide the details specifying the problem?
hey, thanks for the follow-up! the problem might be on the google cloud console side, that a cluster with spaces or . in the description field causes problems with other hub feature setup. i think it is ok to reolve this item and we can follow-up interally.
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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
The value makes it hard to use the cluster in the Anthos or GKE UI to configure ACM or even delete the membership later.
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
Affected Resource(s)
Terraform Configuration Files
Debug Output
It actually "works" ok, you just cant use the resulting cluster for ACM or similar.
Expected Behavior
Just change to have a name that can be part of a resource and make docs to this effect and/or have validation, ideally.
Actual Behavior
Steps to Reproduce
follow the instructions, then try to configure a feature like ACM in the UI.
Important Factoids
References
https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/gke_hub_membership
The text was updated successfully, but these errors were encountered: