Skip to content

Commit 4aa192c

Browse files
committed
OSDOCS3082: Networking Operators overview
1 parent 62d0789 commit 4aa192c

File tree

2 files changed

+23
-0
lines changed

2 files changed

+23
-0
lines changed

_topic_maps/_topic_map.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -959,6 +959,8 @@ Topics:
959959
File: understanding-networking
960960
- Name: Accessing hosts
961961
File: accessing-hosts
962+
- Name: Networking Operators overview
963+
File: networking-operators-overview
962964
- Name: Understanding the Cluster Network Operator
963965
File: cluster-network-operator
964966
Distros: openshift-enterprise,openshift-origin
Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
:_content-type: ASSEMBLY
2+
[id="networking-operators-overview"]
3+
= Networking Operators overview
4+
include::_attributes/common-attributes.adoc[]
5+
:context: networking-operators-overview
6+
7+
toc::[]
8+
9+
{product-title} supports multiple types of networking Operators. You can manage the cluster networking using these networking Operators.
10+
11+
[id="networking-operators-overview-cluster-network-operator"]
12+
== Cluster Network Operator
13+
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) default network provider plug-in 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}].
14+
15+
[id="networking-operators-overview-dns-operator"]
16+
== DNS Operator
17+
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}].
18+
19+
[id="networking-operators-overview-ingress-operator"]
20+
== Ingress Operator
21+
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}].

0 commit comments

Comments
 (0)