Allow distinction between possibly disruptive and non-disruptive UpgradeJobHooks

[bastjan]

Summary

As cluster operator
I want to mark UpgradeJobHooks as possibly disruptive
So that I can decide if i should set up any alert silences

As cluster operator
I want to mark UpgradeJobHooks as possibly disruptive
So that I can have metrics and mark the jobs in dashboards

Context

At VSHN we use UpgradeJobHooks to set silences and to do various disruptive and non-disruptive tasks.

We only want to set silences if there is a possibly disruptive job or an upgrade.
We want to distinguished "risky" upgrades from "noop" upgrades on our dashboards.

Out of Scope

No response

Further links

• https://github.com/appuio/component-openshift-upgrade-controller/blob/master/component/scripts/silence.sh
• https://insights.appuio.net/d/bfdba027-3b4b-4b24-8ca4-6522130b3545/openshift-upgrades?orgId=1

Acceptance Criteria

• UpgradeJobHook CRD has a new field allowing to mark jobs as disruptive.
• UpgradeJob has a metric if it matches any disruptive UpgradeJobHook
• UpgradeJobHook pods have an environment variable passed in with the disruptive status of the current hook and of the disruptive status of all matching hooks.

Implementation Ideas

No response