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

Handle wavefrontalert deletion when it associated with alertsconfig #22

Open
lilwan opened this issue Sep 9, 2021 · 0 comments
Open
Labels
enhancement New feature or request

Comments

@lilwan
Copy link
Collaborator

lilwan commented Sep 9, 2021

Is this a BUG REPORT or FEATURE REQUEST?:
feature

What happened:
We can have a wavefrontalert with exported params and associated with multiple alertsconfig, and then if we delete this wavefrontalert, the current code deletes the individual alert in wavefront but does not update the alertsconfig

What you expected to happen:
When the wavefrontalert template got deleted, we should update alertsconfig as well

How to reproduce it (as minimally and precisely as possible):

  1. Create a wavefrontalert template with exported params and associated with a alertsconfig.
  2. Delete this wavefrontalert
  3. wavefront alert is deleted from wavefront
  4. alertsconfig still has it in the status

Anything else we need to know?:

Environment:

  • alert-manager version
  • Kubernetes version :
$ kubectl version -o yaml

Other debugging information (if applicable):

- controller logs:

$ kubectl logs

@lilwan lilwan added the enhancement New feature or request label Sep 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant