Bug 1904957

Description of problem:
while Configuring an egress firewall and trying to create an egress firewall rule object, ports field does not work unless protocol is explicitly specified, even though documentation states it's optional.


Version-Release number of selected component (if applicable): OCP 4.7


How reproducible: Always


Steps to Reproduce:
1. Configure an egress firewall
2. create an egress firewall rule object
3. mention port, omit protocol field

Actual results:
ports field does not work unless protocol is explicitly specified

# oc create -f egress-firewall-power.yaml
The EgressFirewall "default" is invalid: spec.egress.ports.protocol: Required value
# cat egress-firewall-power.yaml
apiVersion: k8s.ovn.org/v1
kind: EgressFirewall
metadata:
  name: default
spec:
  egress:
  - type: Deny
    to:
      cidrSelector: 0.0.0.0
    ports:
    - port: 80
      #protocol: TCP
# cat egress-firewall-power.yaml
apiVersion: k8s.ovn.org/v1
kind: EgressFirewall
metadata:
  name: default
spec:
  egress:
  - type: Deny
    to:
      cidrSelector: 0.0.0.0
    ports:
    - port: 80
      protocol: TCP
# oc create -f egress-firewall-power.yaml
egressfirewall.k8s.ovn.org/default created

# oc get clusterversion
NAME      VERSION                                     AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.7.0-0.nightly-ppc64le-2020-11-13-081012   True        False         23d     Cluster version is 4.7.0-0.nightly-ppc64le-2020-11-13-081012



Expected results: Optional: A network protocol. If specified, the value must be either TCP, UDP, or SCTP. If not specified, the rule matches all TCP, UDP, and SCTP traffic


Additional info:
Ref-https://docs.openshift.com/container-platform/4.6/networking/ovn_kubernetes_network_provider/configuring-egress-firewall-ovn.html