Skip to content
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

Add support for the rest of the AutoprovisioningNodePoolDefaults settings in google_container_cluster #9180

Closed
pib opened this issue May 19, 2021 · 5 comments

Comments

@pib
Copy link

pib commented May 19, 2021

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 the 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 the issue is assigned to a user, that user is claiming responsibility for the issue. If the issue is assigned to "hashibot", a community member has claimed the issue already.

Description

AutoprovisioningNodePoolDefaults in the v1 API has support for several more fields than those currently supported by the auto_provisioning_defaults block.

Currently only min_cpu_platform, oauth_scopes, and service_account are supported.

Options currently missing are

  • upgradeSettings
  • management
  • diskSizeGb
  • diskType
  • shieldedInstanceConfig
  • bootDiskKmsKey

It might makes sense for these to be implemented in separate PRs. There are already a couple of existing PRs that add upgrade_settings and management (linked in the references section below).

New or Affected Resource(s)

  • google_container_cluster

Potential Terraform Configuration

resource "google_container_cluster" "example" {
  name = "example"

  cluster_autoscaling {
    enabled = true

    auto_provisioning_defaults {
      service_account  = google_service_account.cluster_nodes_service_account.email
      min_cpu_platform = "Intel Haswell"
      oauth_scopes     = []

      # New options
      upgrade_settings {
        max_surge       = "25%"
        max_unavailable = "0"
      }

      management {
        auto_repair  = true
        auto_upgrade = true
      }

      disk_size_gb      = 12
      disk_type         = "pd-ssd"
      boot_disk_kms_key = google_kms_crypto_key.example.id

      shielded_instance_config {
        enable_secure_boot          = true
        enable_integrity_monitoring = false
      }
    }
  }
}

References

@slevenick slevenick added this to the Goals milestone May 24, 2021
@rileykarson rileykarson removed this from the Goals milestone May 25, 2021
@rileykarson rileykarson added this to the Near-Term Goals milestone Jun 1, 2021
@dippynark
Copy link

Should default node image type be included in this list? https://cloud.google.com/kubernetes-engine/docs/how-to/node-auto-provisioning#default-image-type

@YpNo
Copy link

YpNo commented Nov 15, 2021

Hi,
I need the missing options as well with a focus on image_type.

Regards.

@rafaeljesus
Copy link

Any idea when these features will be available? I can't enable NAP due to this limitation as well

@mitj04
Copy link

mitj04 commented Dec 8, 2022

All the PRs have been merged for requested attributes. Hence, we can close this issue. Feel free to reach out if there are any remaining attributes. Thanks!

Below are the PRs for the requested attributes:

b/189224778

@github-actions
Copy link

github-actions bot commented Jan 8, 2023

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 8, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.