Details
-
Story
-
Resolution: Done
-
Critical
-
None
Description
Story: As a Quay admin I need to able to see the status of each of the managed components of my Quay installation provided by the Operator so that I can reason about the progress of the deployment / update.
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
Attachments
Issue Links
- is blocked by
-
PROJQUAY-2438 Quay operator does not show unhealthy status for managed route component
-
- Closed
-
-
PROJQUAY-2439 Quay operator does not show unhealthy status for managed redis 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
-
-
PROJQUAY-2447 Quay operator does not show unhealthy status for base component
-
- Closed
-
- is cloned by
-
PROJQUAY-2636 Operator communicates healthy status per managed component
-
- Closed
-
- is related to
-
PROJQUAY-1389 Quay TNG Operator should be improved to be fault tolerant
-
- Closed
-
- relates to
-
PROJQUAY-2530 Document operator reporting individual conditions per component
-
- Closed
-