Add alert for failing helmreleases deploying aws components

[fiunchinho]

Towards https://github.com/giantswarm/giantswarm/issues/32121

We want to get alerted whenever one of the HelmReleases fore core components like the aws cloud-controller or the aws-ebs-csi-driver are in failed state. Currently, on alba there are some in this state, and we'd get paged by these

Checklist

• Update CHANGELOG.md
• Add Unit tests
• Follow Alert structure
• Consider creating a dashboard (guidelines) (if it does not exist already) to help oncallers monitor the status of the issue.
• Request review from oncall area, as well as team (e.g: oncall-kaas-cloud GitHub group).

[fiunchinho]

@giantswarm/team-atlas could you give me a bit of guidance regarding CI? It's failing.

[AndiDog]

Maybe extend these to all critical ones i.e. add cilium, coredns, network-policies suffixes as well? And do it for every CAPI-based provider, not just CAPA, so we have an easy list that we can extend for the other providers?

[hervenicol]

@giantswarm/team-atlas could you give me a bit of guidance regarding CI? It's failing.

Oh, I guess that's an error that's happening earlier in the tests and that's not properly caught:

Templating chart for provider: capi/capa
Error: YAML parse error on prometheus-rules/templates/kaas/phoenix/alerting-rules/aws-cloud-components.rules.yml: error converting YAML to JSON: yaml: line 24: could not find expected ':'

I think it's due to the indentation for the yaml multiline blocks description and namespace. You need an extra indentation for the content block.

Also, the tests will probably fail later (hopefully with a more meaningful error) because you did not write any unit tests.

[QuentinBisson]

LGTM. If you want to add rocket ones, you could do that without issues :)