Disable the insecure read-only port on new Autopilot clusters

[zaphod72]

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 a user, that user is claiming responsibility for the issue.
• Customers working with a Google Technical Account Manager or Customer Engineer can ask them to reach out internally to expedite investigation and resolution of this issue.

Description

When creating a new GKE Autopilot cluster I want to disable the insecure read-only port as per https://cloud.google.com/kubernetes-engine/docs/how-to/disable-kubelet-readonly-port#disable-autopilot

The gcloud container clusters create-auto flag is --no-autoprovisioning-enable-insecure-kubelet-readonly-port
This setting does not appear to be available in the google_container_cluster Terraform resource.

New or Affected Resource(s)

google_container_cluster

Potential Terraform Configuration

No response

References

No response

b/362329176

[melinath]

Possibly a duplicate of #15208 & may be resolved by GoogleCloudPlatform/magic-modules#11272

[wyardley]

@melinath I had created #19236 to cover this (looks like you found it) -- see comments here and here, but assuming node_pool_auto_config.node_kublet_config is what's needed there, GoogleCloudPlatform/magic-modules#11272 won't cover it as currently stands.

However, it will be a bit of extra work, because it doesn't look like node_kublet_config is currently supported at all for node_pool_auto_config.

[melinath]

Closing as a duplicate of #19236 - please let me know if that seems incorrect!

[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.