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

fix:edge node offline pod‘s status update #5556

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

luomengY
Copy link
Member

@luomengY luomengY commented Apr 22, 2024

What type of PR is this?
/kind bug

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #5504

Special notes for your reviewer:

Does this PR introduce a user-facing change?:


@kubeedge-bot kubeedge-bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 22, 2024
@kubeedge-bot kubeedge-bot added kind/feature Categorizes issue or PR as related to a new feature. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Apr 22, 2024
@kubeedge-bot kubeedge-bot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Apr 22, 2024
@luomengY luomengY force-pushed the offine_pod_status branch 3 times, most recently from ec0f452 to 286b0d6 Compare April 22, 2024 11:45
@luomengY luomengY changed the title [wip]Offine pod‘s status update edge node offline pod‘s status update Apr 22, 2024
@kubeedge-bot kubeedge-bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 22, 2024
@luomengY luomengY force-pushed the offine_pod_status branch 9 times, most recently from 2d47d2c to db3a580 Compare April 23, 2024 07:30
@fisherxu fisherxu added this to the v1.17 milestone Apr 23, 2024
@luomengY luomengY force-pushed the offine_pod_status branch 2 times, most recently from 7bf3c48 to 034916f Compare April 23, 2024 08:44
@kubeedge-bot kubeedge-bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Apr 23, 2024
@luomengY luomengY changed the title fix:edge node offline pod‘s status update [wip]fix:edge node offline pod‘s status update May 24, 2024
@kubeedge-bot kubeedge-bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label May 24, 2024
@luomengY luomengY force-pushed the offine_pod_status branch 22 times, most recently from de8d9c3 to 6211a74 Compare May 29, 2024 05:52
@luomengY luomengY changed the title [wip]fix:edge node offline pod‘s status update fix:edge node offline pod‘s status update May 29, 2024
@kubeedge-bot kubeedge-bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label May 29, 2024
@luomengY
Copy link
Member Author

luomengY commented Jun 3, 2024

PTAL @Shelley-BaoYue @WillardHu

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants