openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

OSDOCS-8649: Removing Networking Operators overview page

Browse Source
This commit is contained in:
Ashley Hardin
2024-05-16 15:01:53 -04:00
committed by openshift-cherrypick-robot
parent c2be88a561
commit 80768ffac6
2 changed files with 0 additions and 35 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
_topic_maps/_topic_map.yml
View File

@@ -1268,8 +1268,6 @@ Topics:
File: zero-trust-networking
- Name: Accessing hosts
File: accessing-hosts
- Name: Networking Operators overview
File: networking-operators-overview
- Name: Networking dashboards
File: networking-dashboards
- Name: OpenShift network security

33
networking/networking-operators-overview.adoc
View File

@@ -1,33 +0,0 @@
:_mod-docs-content-type: ASSEMBLY
[id="networking-operators-overview"]
= Networking Operators overview
include::_attributes/common-attributes.adoc[]
:context: networking-operators-overview
toc::[]
{product-title} supports multiple types of networking Operators. You can manage the cluster networking using these networking Operators.
[id="networking-operators-overview-cluster-network-operator"]
== Cluster Network Operator
The Cluster Network Operator (CNO) deploys and manages the cluster network components in an {product-title} cluster. This includes deployment of the Container Network Interface (CNI) network plugin selected for the cluster during installation. For more information, see xref:../networking/cluster-network-operator.adoc#cluster-network-operator[Cluster Network Operator in {product-title}].
[id="networking-operators-overview-dns-operator"]
== DNS Operator
The DNS Operator deploys and manages CoreDNS to provide a name resolution service to pods. This enables DNS-based Kubernetes Service discovery in {product-title}. For more information, see xref:../networking/dns-operator.adoc#dns-operator[DNS Operator in {product-title}].
[id="networking-operators-overview-ingress-operator"]
== Ingress Operator
When you create your {product-title} cluster, pods and services running on the cluster are each allocated IP addresses. The IP addresses are accessible to other pods and services running nearby but are not accessible to external clients. The Ingress Operator implements the Ingress Controller API and is responsible for enabling external access to {product-title} cluster services. For more information, see xref:../networking/ingress-operator.adoc#configuring-ingress[Ingress Operator in {product-title}].
[id="networking-operators-overview-external-dns-operator"]
== External DNS Operator
The External DNS Operator deploys and manages ExternalDNS to provide the name resolution for services and routes from the external DNS provider to {product-title}. For more information, see xref:../networking/external_dns_operator/understanding-external-dns-operator.adoc#external-dns-operator[Understanding the External DNS Operator].
[id="ingress-node-firewall-operator-1"]
== Ingress Node Firewall Operator
The Ingress Node Firewall Operator uses an extended Berkley Packet Filter (eBPF) and eXpress Data Path (XDP) plugin to process node firewall rules, update statistics and generate events for dropped traffic. The operator manages ingress node firewall resources, verifies firewall configuration, does not allow incorrectly configured rules that can prevent cluster access, and loads ingress node firewall XDP programs to the selected interfaces in the rule's object(s). For more information, see xref:../networking/openshift_network_security/ingress-node-firewall-operator.adoc#ingress-node-firewall-operator[Understanding the Ingress Node Firewall Operator].
[id="network-observability-operator-overview-operator"]
== Network Observability Operator
The Network Observability Operator is an optional Operator that allows cluster administrators to observe the network traffic for {product-title} clusters. The Network Observability Operator uses the eBPF technology to create network flows. The network flows are then enriched with {product-title} information and stored in Loki. You can view and analyze the stored network flows information in the {product-title} console for further insight and troubleshooting. For more information, see xref:../observability/network_observability/network-observability-overview.adoc#dependency-network-observability[About Network Observability Operator].