Open sluetze opened 11 months ago
@sluetze Not sure about which existing rules are you talking. (CPU and RAM)?
As far as I know egress traffic control is only possible with OVN. There is no option with SDN. Can we please discuss both topics?
@sluetze Not sure about which existing rules are you talking. (CPU and RAM)?
imho existing rules for the quota / limits / requests could be:
rules:
- project_config_and_template_resource_quota
- project_template_resource_quota
- resource_requests_limits_in_daemonset
- resource_requests_limits_in_deployment
- resource_requests_limits_in_statefulset
- resource_requests_quota
- resource_requests_quota_cluster
- resource_requests_quota_per_project
As far as I know egress traffic control is only possible with OVN. There is no option with SDN. Can we please discuss both topics?
What do you mean with SDN? OpenShiftSDN? because that is deprecated. Or do you mean other SDNs?
But there is no existing rule for checking the KubernetesOVN Annotation (see https://access.redhat.com/solutions/5018951 )
I am also not sure if this would be a good automatic check, since I believe not many will use this limitation as it has operational impacts. We could make it a manual rule with example of KubernetesOVN which would make it apply to a broader set of Network Plugins.