diff --git a/404.html b/404.html index 6ccf7404..857b82f5 100644 --- a/404.html +++ b/404.html @@ -1,6 +1,6 @@ -404 Page not found | Layered Products SRE +404 Page not found | Layered Products SRE -

Not found

Oops! This page doesn't exist. Try going back to our home page.

+

Not found

Oops! This page doesn't exist. Try going back to our home page.

\ No newline at end of file diff --git a/categories/index.html b/categories/index.html index c8fab28b..d6701e02 100644 --- a/categories/index.html +++ b/categories/index.html @@ -1,6 +1,6 @@ -Categories | Layered Products SRE +Categories | Layered Products SRE -

Categories

+

Categories

\ No newline at end of file diff --git a/docs/_print/index.html b/docs/_print/index.html index 8ff7aef9..7556a076 100644 --- a/docs/_print/index.html +++ b/docs/_print/index.html @@ -1,6 +1,6 @@ -Documentation | Layered Products SRE +Documentation | Layered Products SRE -

This the multi-page printable view of this section. +

This the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

Documentation

1 - Internal Documentation

Internal Documentation for the SRE teams.

1.1 - Tutorials

1.1.1 - Adding ADO alerts

This guide describes how to add alerts for addon-operator in the OSD RHOBS tenant.

Background

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.

5.5 - SKU

How to request a SKU for your addon.

NOTE MT-SRE do not influence SKU creation/priorities. -You must work with SDB directly for this.

Requesting a SKU

To request a SKU, please complete the following steps:

  • Determine a unique quota ID for the addon. This should be +You must work with OCM directly for this.

    Requesting a SKU

    To request a SKU, please complete the following steps:

    • Determine a unique quota ID for the addon. This should be lowercase with dashes and of the format addon-<addon-name>. For example: -addon-prow-operator
    • Create a JIRA Request at Service Dev Team B +addon-prow-operator
    • Create a JIRA Request at Openshift Cluster Manager with the subject Request for new Add-On SKU in OCM and the following information:
      • Add-On name.
      • Add-On owner.
      • Requested Add-On unique quota ID.
      • Additional information that would help qualify the ask, including goals, timelines, etc., you might have in mind.
    • You will need at least your PM and the OCM PM’s to sign off before the SKU is created. We expect to resolve these requests within 7 working days.

    Requesting SKU Attributes Changes

    From time to time you may want to update some SKU fields like supported cloud providers, -quota cost, product support, etc. To do this:

    • Create a JIRA Request at Service Dev Team B
    • Ping the ticket in #service-development-b Slack channel (@sd-b-team is the handle)
    • This requires an update to be committed in-code in AMS, then deployed to stage and +quota cost, product support, etc. To do this:

      • Create a JIRA Request at Openshift Cluster Manager
      • Ping the ticket in #service-development-b Slack channel (@sd-b-team is the handle)
      • This requires an update to be committed in-code in AMS, then deployed to stage and eventually prod (allow up to 7 working days).

      Current Status

      To check current SKUs and attributes, see OCM Resource Cost Mappings.

diff --git a/docs/addons-flow/_print/index.html b/docs/addons-flow/_print/index.html index a8e1c521..8734851b 100644 --- a/docs/addons-flow/_print/index.html +++ b/docs/addons-flow/_print/index.html @@ -1,10 +1,10 @@ -Addons Flow | Layered Products SREAddons Flow | Layered Products SRE -

This the multi-page printable view of this section. +

This the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

Addons Flow

Addons Flow.

1 - Addons Flow Architecture

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 @@ -APIs | Layered Products SREAPIs | Layered Products SRE -