Bug 2042829 - Topology performance: HPA was fetched for each Deployment (Pod Ring)
Summary: Topology performance: HPA was fetched for each Deployment (Pod Ring)
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.7
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.0
Assignee: Christoph Jerolimov
QA Contact: spathak@redhat.com
Depends On:
Blocks: 2044259
TreeView+ depends on / blocked
Reported: 2022-01-20 08:33 UTC by Christoph Jerolimov
Modified: 2022-03-10 16:41 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-03-10 16:40:58 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift console pull 10894 0 None open Bug 2042829: Topology performance: Do not fetch HPA for each Deployment (Pod Ring) 2022-01-20 08:40:35 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:41:09 UTC

Description Christoph Jerolimov 2022-01-20 08:33:46 UTC
Description of problem:
The topology loads the complete HorizontalPodAutoscalers (HPA) resource list for each Deployment which is shown on the topology. This happens because the HPA resource reference the Deployment within the spec only. But the topology should avoid fetching the same list again and again anyway.

Version-Release number of selected component (if applicable):
Reproducible on 4.8+
4.6/4.7 not tested yet.

How reproducible:
Always with Topologies with at least two Deployments.

Steps to Reproduce:
1. Import two Deployments
2. Open the network inspector of your browser and navigate to the topology
3. Reload the browser tab

Actual results:
See multiple API calls fetching HPAs, one per Deployment


Expected results:
Should not fetch the same resource more then once.

Additional info:

Comment 3 Christoph Jerolimov 2022-01-24 19:48:32 UTC
Verified on 4.10.0-0.nightly-2022-01-24-181700

See only 1 api call for HPA

Comment 6 errata-xmlrpc 2022-03-10 16:40:58 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 (Moderate: OpenShift Container Platform 4.10.3 security update), and where to find the updated
files, follow the link below.

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


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