Bug 1798497 - kube descheduler operator does not report status
Summary: kube descheduler operator does not report status
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: kube-scheduler
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.4.0
Assignee: Mike Dame
QA Contact: RamaKasturi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-05 13:56 UTC by Mike Dame
Modified: 2020-05-04 11:34 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-04 11:33:47 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-kube-descheduler-operator pull 69 0 None open Bug 1798497: Update deployment generation statuses 2020-02-05 13:58:28 UTC
Red Hat Product Errata RHBA-2020:0581 0 None None None 2020-05-04 11:34:00 UTC

Description Mike Dame 2020-02-05 13:56:47 UTC
Currently, the kube-descheduler-operator does not report any status in it's CR:

$ oc get -o yaml kubedeschedulers/cluster
apiVersion: operator.openshift.io/v1beta1
kind: KubeDescheduler
metadata:
  creationTimestamp: "2020-02-05T13:45:19Z"
  generation: 1
  name: cluster
  namespace: openshift-kube-descheduler-operator
  resourceVersion: "221440"
  selfLink: /apis/operator.openshift.io/v1beta1/namespaces/openshift-kube-descheduler-operator/kubedeschedulers/cluster
  uid: 4a0a1873-b48f-470c-b4be-3df30cd59f9b
spec:
  deschedulingIntervalSeconds: 3600
  image: gcr.io/k8s-staging-descheduler/descheduler:0.9.0-79-gd845040d7

But it should output a status field, such as:

$ oc get -o yaml kubedeschedulers/cluster
apiVersion: operator.openshift.io/v1beta1
kind: KubeDescheduler
metadata:
  creationTimestamp: "2020-02-05T13:55:44Z"
  generation: 2
  name: cluster
  namespace: openshift-kube-descheduler-operator
  resourceVersion: "224957"
  selfLink: /apis/operator.openshift.io/v1beta1/namespaces/openshift-kube-descheduler-operator/kubedeschedulers/cluster
  uid: ea6e8aa3-6be4-4ce0-abb5-cec4c853d6c2
spec:
  deschedulingIntervalSeconds: 3600
  image: gcr.io/k8s-staging-descheduler/descheduler:0.9.0-79-gd845040d7
  strategies:
  - name: duplicates
status:
  generations:
  - group: apps
    hash: ""
    lastGeneration: 1
    name: cluster
    namespace: openshift-kube-descheduler-operator
    resource: deployments
  readyReplicas: 0

Comment 5 errata-xmlrpc 2020-05-04 11:33:47 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:0581


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