Epic Goal

• As Red Hat’s PnT teams or OpenShift product owner, we need insights on the installer usage, health, install success and failure rate, performance and other metrics.
• As an OpenShift infrastructure owner, I need to be able to disable Telemetry.

Why is this important?

• Health, success rate, performance and other usage data helps Red Hat to improve the product and understand its adoption.
• For disconnected and air-gapped environments, we currently have no visibility into success and failure rates of cluster installations.

Scenarios

1. Customers/partners should have the option to opt-in/opt-out of sharing usage and diagnostics information with RH, such that when connectivity is present, this data can be sent to RH.

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. https://github.com/openshift/assisted-service

Open questions::

1. Can we have a metric to know when users plan to create a disconnected cluster?

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>

References

• Bootable Ephemeral Installer Image for Disconnected Cluster 0 Deployments