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

Only add new conditions to a VC's .status.conditions #349

Merged
merged 1 commit into from
Aug 9, 2023

Conversation

yuanchen8911
Copy link
Member

@yuanchen8911 yuanchen8911 commented Aug 8, 2023

What this PR does / why we need it:

In the current implementation, there can be a large number of redundant conditions with the identical Reason, Message and Status in a VC's .Status.Conditions. A large number of duplicated conditions can cause potential performance issues. It's hard to read too.

This PR makes a change on how to add a VC's condition to .Status.Conditions. It checks whether a new condition exits by Reasonand Status and adds the condition only when it does not exist. if the condition already exists, it will only update the condition's lastTransitionTime. It sets .Conditions.Status value too.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Aug 8, 2023
@yuanchen8911 yuanchen8911 changed the title Only add a new condition to vc.status.conditions Only add a new condition to a VC's .status.conditions Aug 8, 2023
@yuanchen8911
Copy link
Member Author

/assign @christopherhein

@yuanchen8911 yuanchen8911 changed the title Only add a new condition to a VC's .status.conditions Only add new conditions to a VC's .status.conditions Aug 9, 2023
Copy link
Member

@christopherhein christopherhein left a comment

Choose a reason for hiding this comment

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

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Aug 9, 2023
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: christopherhein, yuanchen8911

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

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 9, 2023
@k8s-ci-robot k8s-ci-robot merged commit ba5a6e8 into kubernetes-sigs:main Aug 9, 2023
13 checks passed
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. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants