authenticator_groups_config block conflicts with enable_autopilot

[soerenmartius]

When deploying a GKE cluster with autopilot enabled using the google_container_cluster resource, the authenticator_groups_config causes a conflict. According to the docs, autopilot supports group-based RBAC.

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

Terraform version: v1.1.8
Provider version: v4.10.0

Affected Resource(s)

• google_container_cluster

Debug Output

Expected Behavior

The provider should not ocnfl

Actual Behavior

Steps to Reproduce

1. terraform apply

Important Factoids

References

• https://github.com/mineiros-io/terraform-google-gke-autopilot-cluster/runs/5973604865?check_suite_focus=true

[melinath]

It looks like autopilot added support for RBAC. I'm marking this as an enhancement request to add support for allowing autopilot to work with authenticator_groups_config. It might be as simple as making the fields not conflict, but there's no API example in the docs so I'm hesitant to say that would definitely work.

[soerenmartius]

It looks like autopilot added support for RBAC. I'm marking this as an enhancement request to add support for allowing autopilot to work with authenticator_groups_config. It might be as simple as making the fields not conflict, but there's no API example in the docs so I'm hesitant to say that would definitely work.

Thanks @melinath - please keep us posted

[soerenmartius]

Seems like this has been fixed in version 4.16.0

[github-actions]

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.