Alerts via a Custom Resource

[mmurph3]

What problem are you trying to solve? Alerts can only be configured via helm/UI and this causes the need for redeployment

Describe the solution you'd like Create a budget for each tenant (new or existing) and deploy it together with the tenant. E.g. yaml file with budget associated with namespace and deploy it.

Describe alternatives you've considered Right now this is done via the UI and needs to be done for each namespace.

How would users interact with this feature? Users can deploy custom alerts mapped to tenants (namespaces) via preferred git ops tool and not have to change any configurations via helm and not have to do a helm upgrade

┆Issue is synchronized with this Jira Task by Unito

[dwbrown2]

Really interesting, have an example of how this would work?

One caveat: when adding a new alert with the Kubecost UI/APIs it shouldn't require restarting the pod.

[jessegoodier]

One note on this: please consider how it would work on multi-cluster.

[mmurph3]

@kwombach12 can we get a commitment from Engineering on this? We have a few enterprise customers wanting this feature.

[kwombach12]

We are integrating alerts into our budgets page in 103! @mmurph3 Does that resolve this FR?

[mmurph3]

Customers want a custom resource (defined via a custom resource definition) that manages custom alerts for them. So for example, a new tenant (ns) gets onboarded to the cluster. The custom resource would then update that namespace with a custom notifications. They don't want the custom notifications configured the same globally/manually. Let me know if it doesn't make sense and I'll get more context.

[kwombach12]

@mmurph3 Trying to understand this - is the request basically to have the ability to create alerts which work with Kubernetes allocations which are created after the fact? Do you have an example use case for this?

[chipzoller]

Still seems relevant. Transferred to features-bugs.