Skip to content

Commit 4916184

Browse files
authored
Merge pull request #110716 from openshift-cherrypick-robot/cherry-pick-109482-to-enterprise-4.22
[enterprise-4.22] OSDOCS-18645-abstracts
2 parents eb3e6dd + 1582f37 commit 4916184

5 files changed

Lines changed: 6 additions & 6 deletions

modules/configuring-egress-proxy-edns-operator.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@
77
= Trusting the certificate authority of the cluster-wide proxy
88

99
[role="_abstract"]
10-
To enable the External DNS Operator to authenticate with the cluster-wide proxy, configure the Operator to trust the certificate authority (CA) of the proxy. This ensures secure communication when routing DNS traffic through the proxy.
10+
You can configure the External DNS Operator to trust the certificate authority of the cluster-wide proxy.
1111

1212
.Procedure
1313

modules/nw-control-dns-records-public-aws-with-VPC.adoc

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,9 @@
77
= Creating DNS records in a different AWS account by using a shared VPC
88

99
[role="_abstract"]
10-
To create DNS records in a different AWS account, configure the ExternalDNS Operator to use a shared Virtual Private Cloud (VPC). Your organization can then use a single Route 53 instance for name resolution across multiple accounts and projects.
10+
You can use the ExternalDNS Operator to create DNS records in a different AWS account using a shared Virtual Private Cloud (VPC).
11+
12+
By using a shared VPC, an organization can connect resources from multiple projects to a common VPC network. Organizations can then use VPC sharing to use a single Route 53 instance across multiple AWS accounts.
1113

1214
.Prerequisites
1315

modules/nw-external-dns-operator-configuration-parameters.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@
77
= External DNS Operator configuration parameters
88

99
[role="_abstract"]
10-
To customize the behavior of the External DNS Operator, configure the available parameters in the `ExternalDNS` custom resource (CR). By configuring parameters, you can control how the Operator synchronizes services and routes with your external DNS provider.
10+
To customize the behavior of the External DNS Operator, configure the available parameters in the `ExternalDNS` custom resource (CR).
1111

1212
[cols="3a,8a",options="header"]
1313
|===

modules/nw-external-dns-operator.adoc

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,8 +6,6 @@
66
= Deploying the External DNS Operator
77

88
[role="_abstract"]
9-
You can deploy the External DNS Operator on-demand from the Software Catalog. Deploying the External DNS Operator creates a `Subscription` object.
10-
119
The External DNS Operator implements the External DNS API from the `olm.openshift.io` API group. The External DNS Operator updates services, routes, and external DNS providers.
1210

1311
.Prerequisites

networking/networking_operators/external_dns_operator/understanding-external-dns-operator.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ include::_attributes/common-attributes.adoc[]
77
toc::[]
88

99
[role="_abstract"]
10-
To provide name resolution for services and routes from an External DNS provider to {product-title}, use the External DNS Operator. This Operator deploys and manages `ExternalDNS` to synchronize your cluster resources with the external provider.
10+
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}.
1111

1212
// External DNS Operator domain name limitations
1313
include::modules/nw-external-dns-operator-domain-limitations.adoc[leveloffset=+1]

0 commit comments

Comments
 (0)