XML

Word

Printable

Epic Name:
Stop-gap for Clair disconnected workflow
Blocked:
False
Blocked Reason:
None
Ready:
False
Color Status:
Not Selected
Epic Status:
To Do
Feature Link:
OCPSTRAT-1407 - Simplified disconnected experience for Clair-based products
Parent Link:
OCPSTRAT-1407Simplified disconnected experience for Clair-based products
Hierarchy Progress Bar:

67% To Do, 0% In Progress, 33% Done

Epic Goal

Ease the burden on the user when operating in a disconnected environment.
Give the operator the ability to deploy Clair disconnected supported by added functionality in the midstream and possible clairctl enhancements.

Why is this important?

Currently Quay users who work in an offline environment have some hurdles to get Clair working as expected, this reportedly leads to misconfigured environments and less-accurate reporting.

User want to deploy Quay in a disconnected environment, they shouldn't require making Clair unmanged, the correct data/configuration should be included/referenced by the operator.

CI - MUST be running successfully with tests automated
Release Technical Enablement - Provide necessary release enablement details and documents.
Users should be able to configure Clair for disconnected usage w/o needing to un-manage it.

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>

is related to

PROJQUAY-8320 Automate Clair disconnected updates