Support other kinds of traffic qos

[mlycore]

Feature Request

Is your feature request related to a problem? Please describe:

In the production clusters, different kinds of business unit Pod will share the same NAT gateway or router. The need of traffic QoS from applications varies.

As Waterline is playing a important role in SQL traffic QoS, so why doesn't it support more traffic QoS features in a more extensible way ? Like HTTP or gRPC protocol ? Or support traffic QoS according to different application priorities.

Describe the feature you'd like:

• Adding a way for other protocol integration.
• Providing different policy for traffic QoS, like Guaranteed, Burstable and Besteffort.
• Each rule could be applied to either Ingress and Egress of the Pod or Node.

Describe alternatives you've considered:

• Maybe it could be done by CNI plugins

Teachability, Documentation, Adoption, Migration Strategy:

[mlycore]

Currently introducing a new CRD TrafficQoS for general traffic controlling purpose. Users need to divide their kubernetes cluster bandwidth into different kinds of traffic qos logically. That means TrafficQoS will only decide the control pattern of a specific traffic qos, but won't seperate the traffic.

We introduce CRD VirtualDatabase in Database Mesh scene, so users need to choose a TrafficQoS pattern and set how much bandwidth would like to be applied in this pattern.