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

Ignore or better handle rke_config enable_cri_dockerd #4

Open
manning-ncsa opened this issue Oct 25, 2022 · 0 comments
Open

Ignore or better handle rke_config enable_cri_dockerd #4

manning-ncsa opened this issue Oct 25, 2022 · 0 comments

Comments

@manning-ncsa
Copy link
Member

When I run terraform apply on an otherwise synchronized infrastructure, I always see this:

Terraform will perform the following actions:

  # module.cluster.rancher2_cluster.kube will be updated in-place
  ~ resource "rancher2_cluster" "kube" {
        id                         = "c-x9xrd"
        name                       = "nsf-muses"
        # (16 unchanged attributes hidden)

      ~ rke_config {
          ~ enable_cri_dockerd    = true -> false
            # (5 unchanged attributes hidden)

            # (9 unchanged blocks hidden)
        }

        # (1 unchanged block hidden)
    }

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

Let's find a way to account for this so it does not appear as a proposed change.

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

No branches or pull requests

1 participant