Loading...

XML

Word

Printable

Type: Story
Resolution: Done
Priority: Critical
Fix Version/s: quay-v3.6.1
Affects Version/s: None
Component/s: quay-operator
Labels:

Blocked:
False
Ready:
False
Epic Link:
Operator betterment
Release Note Text:
Undefined
Git Pull Request:
https://github.com/quay/quay-operator/pull/564
Market:

SFDC Cases Links:
SFDC Cases Counter:
SFDC Cases Open:

This is a continuation of ~~PROJQUAY-1609~~ which was only partially completed with 3.6.0- need to rework to provide status for all circumstances around managed components.

Acceptance criteria:

each managed component has a status condition
the status condition for each components exposes the state of the deployment / update progress and basic health
in particular there should be wait states being communicated when a certain managed component (e.g. Quay) is waiting for another managed component (e.g. database) to finish deploying

clones

PROJQUAY-1609 Operator communicates status per managed component

Closed

relates to

PROJQUAY-2438 Quay operator does not show unhealthy status for managed route component

Closed

PROJQUAY-2440 Quay operator does not show unhealthy status for managed objectstorage component

Closed

PROJQUAY-2441 Quay operator does not show unhealthy status for managed monitoring component

Closed

PROJQUAY-2442 Quay operator does not show unhealthy status for managed HPA component

Closed

PROJQUAY-2445 Quay operator does not show unhealthy status for managed clair component

Closed

(1 relates to)

Assignee:: Ricardo Maraschini

Reporter:: Daniel Messer

QA Contact:: Dongbo Yan

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Created:: 2021/10/05 8:05 PM

Updated:: 2022/03/15 7:11 PM

Resolved:: 2021/10/20 11:59 AM

Details

Description

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates