Bug 1664753 - Service Catalog readiness probe should be split from liveness probe
Summary: Service Catalog readiness probe should be split from liveness probe
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Service Catalog
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.11.z
Assignee: Jay Boyd
QA Contact: Jian Zhang
URL:
Whiteboard:
Depends On:
Blocks: 1664799
TreeView+ depends on / blocked
 
Reported: 2019-01-09 15:20 UTC by Jay Boyd
Modified: 2019-02-20 14:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1664799 (view as bug list)
Environment:
Last Closed: 2019-02-20 14:11:02 UTC


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:0326 None None None 2019-02-20 14:11:09 UTC

Description Jay Boyd 2019-01-09 15:20:29 UTC
Description of problem:
There is a single health probe endpoint in both API Server and Controller Manager pods for Service Catalog that covers both readiness and liveness.  The readiness functionality should be split to a dedicated probe specific for readiness to avoid unnecessary pod restarts.

Example from the API Server health probes:
        readinessProbe:
          httpGet:
            port: 6443
            path: /healthz
   .....
        livenessProbe:
          httpGet:
            port: 6443
            path: /healthz


readiness should have its own url.

Comment 1 Jay Boyd 2019-01-09 17:03:04 UTC
PR in progress https://github.com/openshift/openshift-ansible/pull/10977

Comment 5 errata-xmlrpc 2019-02-20 14:11:02 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-2019:0326


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