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

google_container_cluster: unable to use managed Prometheus with logging & metrics disabled #12385

Assignees
Labels

Comments

@renescheepers
Copy link

renescheepers commented Aug 25, 2022

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 v1.2.8
on darwin_arm64
+ provider registry.terraform.io/hashicorp/google v4.33.0
+ provider registry.terraform.io/hashicorp/google-beta v4.33.0

Affected Resource(s)

  • google_container_cluster

Terraform Configuration Files

resource "google_container_cluster" "primary" {
  provider = google-beta

  name     = local.cluster_name
  location = local.location

  remove_default_node_pool = true
  initial_node_count       = 1
  
  monitoring_config {
    enable_components = []

    managed_prometheus {
      enabled = true
    }
  }
  
  logging_config {
    enable_components = []
  }
}

Expected Behavior

expected

  • Logging disabled
  • Monitoring disabled
  • Managed Prometheus enabled

Actual Behavior

  • On the first apply:
    image
  • After the second apply (exactly the same TF used):
    image
  • Each consecutive apply reports this in the plan, but it doesn't seem to change anything:
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  ~ update in-place

Terraform will perform the following actions:

  # google_container_cluster.primary will be updated in-place
  ~ resource "google_container_cluster" "primary" {
        id                          = "projects/shopify-codelab-and-demos/locations/us-east1/clusters/cluster-3"
        name                        = "cluster-3"
        # (26 unchanged attributes hidden)

      ~ monitoring_config {
          ~ enable_components = [
              - "SYSTEM_COMPONENTS",
            ]

            # (1 unchanged block hidden)
        }

        # (11 unchanged blocks hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.

Steps to Reproduce

  1. terraform apply

References

@github-actions
Copy link

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 Oct 21, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.