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: clarify language on libceph and kernel 5.8 in kubeproxy-free GSG #16969
Conversation
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.
Thanks!
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.
Thanks a lot! Could you please squash the two commits?
It was not clear if kernel v5.8 has problem with libceph or if 5.8 fixes the problem. Redo the sentence based on feedback to make it more clear and easy to read. Signed-off-by: Ville Ojamo <bluikko@users.noreply.github.com>
Done. |
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.
Thanks again
In kube-proxy free documentation limitations section it was not totally clear what libceph worked with. The current text could be interpreted kernel v5.8 provides the necessary functions but still does not work with libceph.
Make it clear that kernel 5.8 provides the necessary bits to make kubeproxy-free work with libceph. Based on Slack discussion this is what it was supposed to mean.
Signed-off-by: Ville Ojamo bluikko@users.noreply.github.com