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: non-existant group in Api-Check blocks deletion #59

Open
fluktuid opened this issue Feb 20, 2025 · 0 comments
Open

Bug: non-existant group in Api-Check blocks deletion #59

fluktuid opened this issue Feb 20, 2025 · 0 comments

Comments

@fluktuid
Copy link

When applying an api-check with a non-existant group, the check can't be deleted.
The deletion is blocked by the finalizer.

steps to reproduce:

  • apply api-check with non-existant group
    e.g.
    apiVersion: k8s.checklyhq.com/v1alpha1
    kind: ApiCheck
    metadata:
      name: operator-apicheck-sample
    spec:
      endpoint: "checklyhq.com"
      success: "200"
      muted: true # Default "false"
      group: non-existant-dummy-group
  • delete ApiCheck
    kubectl delete apicheck operator-apicheck-sample
  • look at operator logs and wait (potenially forever)

Workaround (bad practice):

  • patch operator for deletion
    this may result in a delta between checkly api and cluster-scope, so this may result in a delta between 'expected reality' and 'reality' when using gitops.
    kubectl patch apicheck operator-apicheck-sample --patch '{"metadata":{"finalizers":[]}}' --type='merge'
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