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
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.
A cluster should be created with node autoprovisioning enabled, where any new nodes spun up use our custom service account, and also have the full cloud-platform oauth scope so that they can access all GCP APIs and restrictions are done using fine-grained IAM on the service account itself.
Actual Behavior
An error is generated (from the Terraform provider, rather than the GCP API), saying that we are not allowed to specify both oauth_scopes and service_account:
Error: "cluster_autoscaling.0.auto_provisioning_defaults.0.oauth_scopes": only one of `cluster_autoscaling.0.auto_provisioning_defaults.0.oauth_scopes,cluster_autoscaling.0.auto_provisioning_defaults.0.service_account` can be specified, but `cluster_autoscaling.0.auto_provisioning_defaults.0.oauth_scopes,cluster_autoscaling.0.auto_provisioning_defaults.0.service_account` were specified.
on .terraform/modules/picozoa.kubernetes/main.tf line 73, in resource "google_container_cluster" "kubernetes":
73: resource "google_container_cluster" "kubernetes" {
If we remove oauth_scopes from the definition then when new nodes are autoprovisioned, if we do not use the default service account, the nodes do not even have enough access to pull container images from the container registry in the same project. This is because the default enabled scopes do not include one with that level of access. The default pool, using the same service account and the cloud-platform scope, works fine.
Either we should be able to specify both these options (which the gcloud CLI tool allows), or the cloud-platform 'all access' scope should be defaulted when a service account is provided.
Steps to Reproduce
terraform apply
Important Factoids
N/A
References
N/A
The text was updated successfully, but these errors were encountered:
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!
ghost
locked and limited conversation to collaborators
Mar 21, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
https://gist.github.com/dancmeyers/ed4fc39a005357279ccc42ead6ff898d
Panic Output
N/A
Expected Behavior
A cluster should be created with node autoprovisioning enabled, where any new nodes spun up use our custom service account, and also have the full cloud-platform oauth scope so that they can access all GCP APIs and restrictions are done using fine-grained IAM on the service account itself.
Actual Behavior
An error is generated (from the Terraform provider, rather than the GCP API), saying that we are not allowed to specify both
oauth_scopes
andservice_account
:If we remove
oauth_scopes
from the definition then when new nodes are autoprovisioned, if we do not use the default service account, the nodes do not even have enough access to pull container images from the container registry in the same project. This is because the default enabled scopes do not include one with that level of access. The default pool, using the same service account and the cloud-platform scope, works fine.Either we should be able to specify both these options (which the
gcloud
CLI tool allows), or the cloud-platform 'all access' scope should be defaulted when a service account is provided.Steps to Reproduce
terraform apply
Important Factoids
N/A
References
N/A
The text was updated successfully, but these errors were encountered: