Bug 1805838 - [DeScheduler] Tracker bug for tacking the readiness of descheduler operator availability via operator hub
Summary: [DeScheduler] Tracker bug for tacking the readiness of descheduler operator a...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: kube-scheduler
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.4.0
Assignee: Jan Chaloupka
QA Contact: RamaKasturi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-21 16:01 UTC by Jan Chaloupka
Modified: 2020-02-21 16:02 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1798456
Environment:
Last Closed: 2020-02-21 16:02:56 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Jan Chaloupka 2020-02-21 16:01:37 UTC 
+++ This bug was initially created as a clone of Bug #1798456 +++

Description of problem:
Descheduler operator is not yet available via Operator Hub and this bug is to track the readiness of the same.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Note You need to log in before you can comment on or make changes to this bug.