docs: Add IP fragmentation tracking section#12162
Conversation
|
PTAL, my understanding is that we're auto-enabling this so I'm not sure if we should be calling this "beta". However Quentin had mentioned in other contexts that this feature in conjunction with kube-proxy-free was "experimental" in some sense. |
|
Coverage decreased (-0.001%) to 37.122% when pulling 42248d104b0c2cba4bf0715f25e5c12aadc61828 on joestringer:submit/ip-frag-docs into d2beddb on cilium:master. |
michi-covalent
left a comment
There was a problem hiding this comment.
lgtm but i don't know enough to approve :)
There was a problem hiding this comment.
maybe
| to allow protocols that do not support segmentation (such as UDP) to | |
| to allow protocols that do not support fragmentation (such as UDP) to |
There was a problem hiding this comment.
This one was deliberate, although they're synonyms I've tended to see segmentation used to talk about breaking up messages into datagrams at layer 4 while people seem to use fragmentation to refer to layer 3 message partitioning. (Reviewers, I'd be interested to hear if you disagree)
42248d1 to
77a49d4
Compare
Rework a couple of the existing instances to reuse this. Signed-off-by: Joe Stringer <joe@cilium.io>
Based partially on prior wording from Quentin Monnet. Signed-off-by: Joe Stringer <joe@cilium.io>
77a49d4 to
4b0b093
Compare
Based partially on prior wording from Quentin Monnet.