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

[BUG] rancher2_pod_security_admission_configuration_template changes on annotations #1424

Open
sass1997 opened this issue Oct 17, 2024 · 0 comments
Labels

Comments

@sass1997
Copy link

Rancher Server Setup

  • Rancher version: 2.8.3

Information about the Cluster

  • Kubernetes version: 1.28
  • Cluster Type (Local/Downstream): local

User Information

  • What is the role of the user logged in? Admin

Provider Information

  • What is the version of the Rancher v2 Terraform Provider in use? v4.4.0
  • What is the version of Terraform in use? 1.9

Describe the bug

After applying the resource rancher2_pod_security_admission_configuration_template for the first after each run there are changes in the annotations field. Even with the option to put annotations in the lifecycle ignore still it shows update

To Reproduce

resource "rancher2_pod_security_admission_configuration_template" "privileged_psact" {
  provider          = rancher2.admin
  name              = "privileged-psact"
  description       = "privileged Pod Security Admission Configuration Template"
  defaults {
    audit           = "restricted"
    audit_version   = "latest"
    enforce         = "privileged"
    enforce_version = "latest"
    warn            = "restricted"
    warn_version    = "latest"
  }
  lifecycle {
    ignore_changes = [
      annotations,
      labels
    ]
  }
}

Actual Result

  ~ resource "rancher2_pod_security_admission_configuration_template" "baseline_psact" {
      + annotations = (known after apply)
        id          = "baseline-psact"
        name        = "baseline-psact"
        # (2 unchanged attributes hidden)
        # (2 unchanged blocks hidden)
    }

Expected Result

No changes after rerun

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant