I logged in, they don’t explain why there either. Nor even the bugzilla for it. It still exists in 9 though, but will disappear in RHEL10 apparently. I expect they are just wanting to get everyone to start moving away from it. But weird that they deprecate and don’t explain their reason for it.
One big reason for using bonding because it’s in the kernel rather than user-space which could be slower. An explanation between the two:
I would prefer to use in kernel space, I remember some things like zfs suffering in user-space, there was also something else that a few years back I used in user-space which wasn’t so good either - could have been ntfs-3g.
Could it be that since the upstream does not have much activity, Red Hat does not want to commit maintaining untold years (beyond 2032)? Surely, if there were no alternatives, then the cost analysis could be different.
@iwalker Thanks for peeking into KB. IME, we do often wonder RH’s reasons.
Also some information in this document (Chapter 11.2):
Red Hat focuses its efforts on kernel-based bonding to avoid maintaining two features, bonds and teams, that have similar functions. The bonding code has a high customer adoption, is robust, and has an active community development. As a result, the bonding code receives enhancements and updates.
My guess is with the proliferation of 10/25/100GB ethernet, there aren’t as many people doing teaming anymore. I guess there is still the redundancy issue, but a lot of that is being handled by hardware type solutions on the back end of VM’s in the data centers these days. I guessing there just isn’t as much of a call for it these days.