The existing implementation of the AlertsChannel controller forces users to keep all AlertPolicies in the New Relic Kubernetes operator and will actively remove any policies not listed in the AlertsChannel configuration. This PR extends the AlertPolicy controller to enable users to control Alert Channels on a per Policies basis, which will work much better in a mixed use environment since it allows policies to self-sign up for Alert Channels but also requires the ID of Alerts channels to be known ahead of time.
The existing implementation of the AlertsChannel controller forces users to keep all AlertPolicies in the New Relic Kubernetes operator and will actively remove any policies not listed in the AlertsChannel configuration. This PR extends the AlertPolicy controller to enable users to control Alert Channels on a per Policies basis, which will work much better in a mixed use environment since it allows policies to self-sign up for Alert Channels but also requires the ID of Alerts channels to be known ahead of time.