This is a cache of https://docs.openshift.com/container-platform/4.16/networking/network_security/egress_firewall/viewing-egress-firewall-ovn.html. It is a snapshot of the page at 2024-11-21T09:28:57.439+0000.
Viewing an <strong>egress</strong> firewall for a project - Network security | Networking | OpenShift Container Platform 4.16
    Soon, all Red Hat OpenShift documentation will only be available on docs.redhat.com, the official location of all Red Hat product documentation. Get familiar with the updated experience today!
  1. Documentation
    2. history bug_report picture_as_pdf
×

Viewing an egress firewall for a project

As a cluster administrator, you can list the names of any existing egress firewalls and view the traffic rules for a specific egress firewall.

OpenShift SDN CNI is deprecated as of OpenShift Container Platform 4.14. As of OpenShift Container Platform 4.15, the network plugin is not an option for new installations. In a subsequent future release, the OpenShift SDN network plugin is planned to be removed and no longer supported. Red Hat will provide bug fixes and support for this feature until it is removed, but this feature will no longer receive enhancements. As an alternative to OpenShift SDN CNI, you can use OVN Kubernetes CNI instead. For more information, see OpenShift SDN CNI removal.

Viewing an egressFirewall object

You can view an egressFirewall object in your cluster.

Prerequisites

  • A cluster using the OVN-Kubernetes network plugin.

  • Install the OpenShift Command-line Interface (CLI), commonly known as oc.

  • You must log in to the cluster.

Procedure

  1. Optional: To view the names of the egressFirewall objects defined in your cluster, enter the following command:

    $ oc get egressfirewall --all-namespaces

  2. To inspect a policy, enter the following command. Replace <policy_name> with the name of the policy to inspect.

    $ oc describe egressfirewall <policy_name>
    Example output
    Name:		default
Namespace:	project1
Created:	20 minutes ago
Labels:		<none>
Annotations:	<none>
Rule:		Allow to 1.2.3.0/24
Rule:		Allow to www.example.com
Rule:		Deny to 0.0.0.0/0