Not found
Oops! This page doesn't exist. Try going back to our home page.
diff --git a/404.html b/404.html index 6ccf7404..857b82f5 100644 --- a/404.html +++ b/404.html @@ -1,6 +1,6 @@ -
Oops! This page doesn't exist. Try going back to our home page.
Oops! This page doesn't exist. Try going back to our home page.
This the multi-page printable view of this section. +
This the multi-page printable view of this section. Click here to print.
This guide describes how to add alerts for addon-operator in the OSD RHOBS tenant.
Since the addon-operator doesn’t have a specific tenant in RHOBS with a service account, the addon-operator metrics are scraped to the OSD tenant with its own service account, so instead of adding rules using obsctl cli and @@ -1051,13 +1051,13 @@ . See the create an addon documentation page for a good starting point.
NOTE MT-SRE do not influence SKU creation/priorities. -You must work with SDB directly for this.
To request a SKU, please complete the following steps:
To request a SKU, please complete the following steps:
addon-<addon-name>
. For example:
-addon-prow-operator
addon-prow-operator
Request for new Add-On SKU in OCM
and the following information:From time to time you may want to update some SKU fields like supported cloud providers, -quota cost, product support, etc. To do this:
To check current SKUs and attributes, see OCM Resource Cost Mappings.
This the multi-page printable view of this section. +
This the multi-page printable view of this section. Click here to print.
Add-Ons are Operators. As such, Add-Ons are installed using typical Operator
objects, like Subscription
, OperatorGroup
and CatalogSource
.
To get those objects into the OpenShift clusters, we rely on OCM and diff --git a/docs/addons-flow/apis/index.html b/docs/addons-flow/apis/index.html index ae273597..5889c880 100644 --- a/docs/addons-flow/apis/index.html +++ b/docs/addons-flow/apis/index.html @@ -1,8 +1,8 @@ -