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
docs: Deprecate CNPStatusUpdates/K8sEventHandover #24464
docs: Deprecate CNPStatusUpdates/K8sEventHandover #24464
Conversation
Is there a larger issue or roadmap item for this deprecation? Anything with more context you can link to? |
762d5a5
to
6c98b7f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One last request (sorry) -- can you add something in upgrade.rst about the deprecation?
This pull request has been automatically marked as stale because it |
@marseel any updates on this? |
6c98b7f
to
62ab471
Compare
c90907f
to
3034500
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
/test |
2 similar comments
/test |
/test |
I would argue this change is trivial enough as to not require a full CI run. |
CNP Status Updates are known to cause scalability-related issues. Deprecate it in preparation to remove support in a future release, to minimize the maintenance burden of this code. Signed-off-by: Marcel Zieba <marcel.zieba@isovalent.com>
3034500
to
dff1622
Compare
Marking as ready-to-merge as all basic CI tests passed. |
CNP Node status updates are known to cause scalability-related issues. Deprecate it in preparation to remove support in a future release, to minimize the maintenance burden of this code.
Related #24503