-
Notifications
You must be signed in to change notification settings - Fork 22
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
[SURE-3099] Add ability to configure the Service Account for node pools in GKE clusters #262
Comments
Before updating https://github.com/rancher/terraform-provider-rancher2 we need to add a new release branch that tracks Rancher 2.9, see https://github.com/rancher/terraform-provider-rancher2/milestone/26. This is because the change to include the optional service account field are available in the 2.9 branch of Rancher. |
Validation passed on build |
Add ability to specify a service account for a node pool in a GKE cluster Issue: rancher/gke-operator#262
Add ability to specify a service account for a node pool in a GKE cluster Issue: rancher/gke-operator#262 Signed-off-by: Michal Jura <[email protected]>
Add ability to specify a service account for a node pool in a GKE cluster Issue: rancher/gke-operator#262 Signed-off-by: Michal Jura <[email protected]>
Add ability to specify a service account for a node pool in a GKE cluster Issue: rancher/gke-operator#262 Signed-off-by: Michal Jura <[email protected]>
Request description:
Best practice for GKE is to use a separate SA with minimal access for the node pools. This is not an option in GKEv2 today and should be added. List of existing SA in the project is available through the GCP API. https://cloud.google.com/kubernetes-engine/docs/how-to/hardening-your-cluster#use_least_privilege_sa https://avd.aquasec.com/cspm/google/kubernetes/default-service-account/
Actual behavior:
No ability to configure Service Account for node pools
Expected behavior:
Ability to configure Service Account for node pools
Tasks:
PR's:
The text was updated successfully, but these errors were encountered: