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

Bigtable cluster parameter num_nodes misleading #20715

Open
robertb724 opened this issue Dec 17, 2024 · 0 comments
Open

Bigtable cluster parameter num_nodes misleading #20715

robertb724 opened this issue Dec 17, 2024 · 0 comments

Comments

@robertb724
Copy link

robertb724 commented Dec 17, 2024

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.

Terraform Version & Provider Version(s)

Terraform v1.9.5
on darwin_arm64

  • provider registry.terraform.io/hashicorp/google v6.14.0

Affected Resource(s)

google_bigtable_instance

Terraform Configuration

resource "google_bigtable_instance" "test_instance" {
  name                = "tf-test-bigtable-instance"
  project             = "var.project"
  deletion_protection = false

  cluster {
    cluster_id   = "tf-test-bigtable-cluster"
    zone         = "us-central1-a"
    storage_type = "HDD"
  }

  labels = {
    environment = "test"
    managed_by  = "terraform"
  }
}

provider "google" {
    project = "var.project"
    region  = "us-central1"

}

Debug Output

No response

Expected Behavior

The documentation states:

num_nodes - (Optional) The number of nodes in the cluster. If no value is set, Cloud Bigtable automatically allocates nodes based on your data footprint and optimized for 50% storage utilization.

This leads me to believe if I omit this value or set it to null the cluster will have a basic autoscaling configuration set.

Actual Behavior

The bigtable cluster is created with the property:

Node scaling mode Manually scale nodes

and there is 1 node.

This leads me to believe that the cluster will be 1 static node.

Steps to reproduce

  1. terraform apply

Important Factoids

No response

References

https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/bigtable_instance#num_nodes-1

b/385406295

@robertb724 robertb724 added the bug label Dec 17, 2024
@github-actions github-actions bot added forward/review In review; remove label to forward service/bigtableadmin labels Dec 17, 2024
@shuyama1 shuyama1 added documentation and removed bug forward/review In review; remove label to forward labels Dec 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants