-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
[1.13] Add documentation about bpf-clock breakage #27048
Conversation
53c0f77
to
63209c7
Compare
63209c7
to
099c150
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.
Looks good, thanks
Documentation/operations/upgrade.rst
Outdated
* ``bpfClockProbe`` has been set to ``false`` everywhere to avoid interrupting | ||
existing connections. It can still be manually set to ``true`` if the | ||
``bpf-clock-probe`` behavior is desired. |
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.
I'm confused about this. bpfClockProbe
is the helm option, shouldn't it be "bpfClockProbe
behavior is desired."?
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.
I think it should actually be "if the BPF clock probe behavior is desired" (i.e. no code text, this is talking about the underlying behavior), what do you think?
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.
Reworded as mentioned. PTAL
099c150
to
5c81e06
Compare
5c81e06
to
9eb76a1
Compare
We've disabled bpfClockProbe everywhere with cilium#26981 and backports. Document that existing connections may be interrupted when upgrading to 1.13.4, the only release to ship with this enabled. On the other hand, they may linger for too long if upgrading from that release to one where bpf-clock-probe is no longer enabled. Signed-off-by: Margarita Manterola <marga@isovalent.com>
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.
LGTM, thanks.
9eb76a1
to
52e580e
Compare
We've disabled bpfClockProbe everywhere with #26981 and backports. Document that long lived connections will be interrupted when upgrading to and from 1.13.4, the only release to ship with this enabled.