Merge pull request #38353 from jboxman-rh/gh-38299

GH#38299: Use correct example for egress firewall

Author: jboxman

modules/nw-egressnetworkpolicy-about.adoc

@@ -6,10 +6,12 @@
 ifeval::["{context}" == "configuring-egress-firewall-ovn"]
 :ovn:
 :kind: EgressFirewall
+:api: k8s.ovn.org/v1
 endif::[]
 ifeval::["{context}" == "openshift-sdn-egress-firewall"]
 :openshift-sdn:
 :kind: EgressNetworkPolicy
+:api: network.openshift.io/v1
 endif::[]
 
 [id="nw-egressnetworkpolicy-about_{context}"]
@@ -42,10 +44,10 @@ endif::ovn[]
 If your egress firewall includes a deny rule for `0.0.0.0/0`, access to your {product-title} API servers is blocked.
 To ensure that pods can continue to access the {product-title} API servers, you must include the IP address range that the API servers listen on in your egress firewall rules, as in the following example:
 
-[source,yaml]
+[source,yaml,subs="attributes+"]
 ----
-apiVersion: k8s.ovn.org/v1
-kind: EgressFirewall
+apiVersion: {api}
+kind: {kind}
 metadata:
   name: default
   namespace: <namespace> <1>
@@ -143,3 +145,6 @@ endif::[]
 ifdef::kind[]
 :!kind:
 endif::[]
+ifdef::api[]
+:!api:
+endif::[]