Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[release-4.7] Bug 2049313: Topology performance: Do not fetch HPA for each Deployment (Pod Ring) #10991

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #10931

/assign jerolimov

to not refetch HPA resource list again and again in topology
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 1, 2022

@openshift-cherrypick-robot: Bugzilla bug 2046043 has been cloned as Bugzilla bug 2049313. Retitling PR to link against new bug.
/retitle [release-4.7] [release-4.8] Bug 2049313: Topology performance: Do not fetch HPA for each Deployment (Pod Ring)

In response to this:

[release-4.7] [release-4.8] Bug 2046043: Topology performance: Do not fetch HPA for each Deployment (Pod Ring)

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-ci openshift-ci bot changed the title [release-4.7] [release-4.8] Bug 2046043: Topology performance: Do not fetch HPA for each Deployment (Pod Ring) [release-4.7] [release-4.8] Bug 2049313: Topology performance: Do not fetch HPA for each Deployment (Pod Ring) Feb 1, 2022
@openshift-ci openshift-ci bot added bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Feb 1, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 1, 2022

@openshift-cherrypick-robot: This pull request references Bugzilla bug 2049313, which is invalid:

  • expected dependent Bugzilla bug 2046043 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

[release-4.7] [release-4.8] Bug 2049313: Topology performance: Do not fetch HPA for each Deployment (Pod Ring)

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-ci openshift-ci bot requested review from jhadvig and kyoto February 1, 2022 22:17
@openshift-ci openshift-ci bot added the component/shared Related to console-shared label Feb 1, 2022
@jerolimov
Copy link
Member

/retitle [release-4.7] Bug 2049313: Topology performance: Do not fetch HPA for each Deployment (Pod Ring)
/label backport-risk-assessed
/cc @jerolimov @rottencandy @sanketpathak

@openshift-ci openshift-ci bot changed the title [release-4.7] [release-4.8] Bug 2049313: Topology performance: Do not fetch HPA for each Deployment (Pod Ring) [release-4.7] Bug 2049313: Topology performance: Do not fetch HPA for each Deployment (Pod Ring) Feb 1, 2022
@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Feb 1, 2022
Copy link
Contributor

@rottencandy rottencandy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested using cluster-bot.
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 3, 2022
@jerolimov
Copy link
Member

Looks like this change is not enough for 4.7. I will take a look next week how we can improve and backport this for 4.7.

image

/wip
/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 3, 2022
@jerolimov
Copy link
Member

Hey @rottencandy, I tried this now locally and now again on a cluster bot, and yeah, it looks like it works fine. I don't know why I saw this HPA the last time... 🤷‍♂️

A 4.7 cluster without this change:

before.mp4

On localhost:

localhost.mp4

And finally the fix with this PR (started via cluster bot):

with-pr.mp4

/unhold
/approve
/cc @sanketpathak @jrichter1

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 15, 2022
@jerolimov
Copy link
Member

/bugzilla refresh

@openshift-ci openshift-ci bot added the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Feb 15, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 15, 2022

@jerolimov: This pull request references Bugzilla bug 2049313, which is valid.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.7.z) matches configured target release for branch (4.7.z)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
  • dependent bug Bugzilla bug 2046043 is in the state RELEASE_PENDING, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
  • dependent Bugzilla bug 2046043 targets the "4.8.z" release, which is one of the valid target releases: 4.8.0, 4.8.z
  • bug has dependents

Requesting review from QA contact:
/cc @sanketpathak

In response to this:

/bugzilla refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-ci openshift-ci bot removed the bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. label Feb 15, 2022
@jerolimov
Copy link
Member

/assign @christianvogt

@christianvogt
Copy link
Contributor

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 16, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: christianvogt, jerolimov, openshift-cherrypick-robot, rottencandy

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 16, 2022
@sanketpathak
Copy link
Contributor

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Mar 2, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 2, 2022

@openshift-cherrypick-robot: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@openshift-merge-robot openshift-merge-robot merged commit e26b21a into openshift:release-4.7 Mar 2, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 2, 2022

@openshift-cherrypick-robot: All pull requests linked via external trackers have merged:

Bugzilla bug 2049313 has been moved to the MODIFIED state.

In response to this:

[release-4.7] Bug 2049313: Topology performance: Do not fetch HPA for each Deployment (Pod Ring)

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. component/shared Related to console-shared lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants