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

v1.14 deleting terraform-provider secret #5043

Closed
headyj opened this issue Nov 20, 2023 · 2 comments
Closed

v1.14 deleting terraform-provider secret #5043

headyj opened this issue Nov 20, 2023 · 2 comments
Labels
bug Something isn't working

Comments

@headyj
Copy link

headyj commented Nov 20, 2023

I know it's a weird one, but Crossplane v1.14 seems to be deleting our terraform-provider secret (itself managed by Terraform) automatically every 10 minutes or so, forcing us to re-apply it:

# kubernetes_secret.terraform_provider[0] will be created
  + resource "kubernetes_secret" "terraform_provider" {
      + data                           = (sensitive value)
      + id                             = (known after apply)
      + type                           = "kubernetes.io/service-account-token"
      + wait_for_service_account_token = true

      + metadata {
          + annotations      = {
              + "kubernetes.io/service-account.name" = "terraform-provider"
            }
          + generation       = (known after apply)
          + name             = "terraform-provider"
          + namespace        = "crossplane-system"
          + resource_version = (known after apply)
          + uid              = (known after apply)
        }
    }

Reverting to v1.13 solves the issue. I also tried to apply it manually with kubectl and the same thing is happening so I guess this is an easy way to reproduce it without the need of Terraform.

  • Crossplane version: v1.14.0, v1.14.1
  • Kubernetes version: v1.27
  • Kubernetes distribution: AWS EKS
  • OS: Linux 5.10.197-186.748.amzn2.x86_64
@headyj headyj added the bug Something isn't working label Nov 20, 2023
@phisco
Copy link
Contributor

phisco commented Nov 20, 2023

Will be fixed soon by #5039 in 1.14.2 as per #5041

@turkenh
Copy link
Member

turkenh commented Nov 27, 2023

v1.14.2 (and even v1.14.3) is out, so closing as fixed!

@headyj it would be great if you could confirm that the issue is fixed (or feel free to reopen if this is not the case).

@turkenh turkenh closed this as completed Nov 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants