mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
OSDOCS-16843-2: CQA for the NOP-2 External DNS Operator (EDO)
This commit is contained in:
dfitzmau
committed by
openshift-cherrypick-robot
openshift-cherrypick-robot
parent
6c3ce7a967
commit
466a559716
26
modules/external-dns-operator-release-notes-1.0.adoc
Normal file
26
modules/external-dns-operator-release-notes-1.0.adoc
Normal file
@@ -0,0 +1,26 @@
|
||||
// Module included in the following assemblies:
|
||||
//
|
||||
// * /networking/networking_operators/external_dns_operator/external-dns-operator-release-notes.adoc
|
||||
|
||||
:_mod-docs-content-type: REFERENCE
|
||||
[id="external-dns-operator-release-notes-1.0_{context}"]
|
||||
= External DNS Operator 1.0
|
||||
|
||||
[role="_abstract"]
|
||||
The External DNS Operator 1.0 release notes summarize all new features and enhancements, notable technical changes, major corrections from previous versions, and any known bugs upon general availability.
|
||||
|
||||
External DNS Operator 1.0.1::
|
||||
+
|
||||
The following advisory is available for the External DNS Operator version 1.0.1:
|
||||
+
|
||||
* link:https://access.redhat.com/errata/RHEA-2024:0537[RHEA-2024:0537 ExternalDNS Operator 1.0 operator/operand containers]
|
||||
|
||||
External DNS Operator 1.0.0::
|
||||
+
|
||||
The following advisory is available for the External DNS Operator version 1.0.0:
|
||||
+
|
||||
* link:https://access.redhat.com/errata/RHEA-2022:5867[RHEA-2022:5867 ExternalDNS Operator 1.0 operator/operand containers]
|
||||
+
|
||||
Bug fixes:
|
||||
+
|
||||
* Previously, the External DNS Operator issued a warning about the violation of the restricted SCC policy during ExternalDNS operand pod deployments. This issue has been resolved. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2086408[BZ#2086408])
|
||||
26
modules/external-dns-operator-release-notes-1.1.adoc
Normal file
26
modules/external-dns-operator-release-notes-1.1.adoc
Normal file
@@ -0,0 +1,26 @@
|
||||
// Module included in the following assemblies:
|
||||
//
|
||||
// * /networking/networking_operators/external_dns_operator/external-dns-operator-release-notes.adoc
|
||||
|
||||
:_mod-docs-content-type: REFERENCE
|
||||
[id="external-dns-operator-release-notes-1.1_{context}"]
|
||||
= External DNS Operator 1.1
|
||||
|
||||
[role="_abstract"]
|
||||
The External DNS Operator 1.1 release notes summarize all new features and enhancements, notable technical changes, major corrections from previous versions, and any known bugs upon general availability.
|
||||
|
||||
External DNS Operator 1.1.1::
|
||||
+
|
||||
The following advisory is available for the External DNS Operator version 1.1.1:
|
||||
+
|
||||
* link:https://access.redhat.com/errata/RHEA-2024:0536[RHEA-2024:0536 ExternalDNS Operator 1.1 operator/operand containers]
|
||||
|
||||
External DNS Operator 1.1.0::
|
||||
+
|
||||
This release included a rebase of the operand from the upstream project version 0.13.1. The following advisory is available for the External DNS Operator version 1.1.0:
|
||||
+
|
||||
* link:https://access.redhat.com/errata/RHEA-2022:9086[RHEA-2022:9086-01 ExternalDNS Operator 1.1 operator/operand containers]
|
||||
+
|
||||
Bug fixes:
|
||||
+
|
||||
* Previously, the ExternalDNS Operator enforced an empty `defaultMode` value for volumes, which caused constant updates due to a conflict with the OpenShift API. Now, the `defaultMode` value is not enforced and operand deployment does not update constantly. (link:https://issues.redhat.com/browse/OCPBUGS-2793[OCPBUGS-2793])
|
||||
24
modules/external-dns-operator-release-notes-1.2.adoc
Normal file
24
modules/external-dns-operator-release-notes-1.2.adoc
Normal file
@@ -0,0 +1,24 @@
|
||||
// Module included in the following assemblies:
|
||||
//
|
||||
// * /networking/networking_operators/external_dns_operator/external-dns-operator-release-notes.adoc
|
||||
|
||||
:_mod-docs-content-type: REFERENCE
|
||||
[id="external-dns-operator-release-notes-1.2_{context}"]
|
||||
= External DNS Operator 1.2
|
||||
|
||||
[role="_abstract"]
|
||||
The External DNS Operator 1.2 release notes summarize all new features and enhancements, notable technical changes, major corrections from previous versions, and any known bugs upon general availability.
|
||||
|
||||
External DNS Operator 1.2.0::
|
||||
+
|
||||
The following advisory is available for the External DNS Operator version 1.2.0:
|
||||
+
|
||||
* link:https://access.redhat.com/errata/RHEA-2023:7239[RHEA-2022:5867 ExternalDNS Operator 1.2 operator/operand containers]
|
||||
+
|
||||
New features:
|
||||
+
|
||||
* The External DNS Operator now supports {aws-short} shared VPC. For more information, see "Creating DNS records in a different {aws-short} Account using a shared VPC".
|
||||
+
|
||||
Bug fixes:
|
||||
+
|
||||
* The update strategy for the operand changed from `Rolling` to `Recreate`. (link:https://issues.redhat.com/browse/OCPBUGS-3630[OCPBUGS-3630])
|
||||
46
modules/external-dns-operator-release-notes-1.3.adoc
Normal file
46
modules/external-dns-operator-release-notes-1.3.adoc
Normal file
@@ -0,0 +1,46 @@
|
||||
// Module included in the following assemblies:
|
||||
//
|
||||
// * /networking/networking_operators/external_dns_operator/external-dns-operator-release-notes.adoc
|
||||
|
||||
:_mod-docs-content-type: REFERENCE
|
||||
[id="external-dns-operator-release-notes-1.3_{context}"]
|
||||
= External DNS Operator 1.3
|
||||
|
||||
[role="_abstract"]
|
||||
The External DNS Operator 1.3 release notes summarize all new features and enhancements, notable technical changes, major corrections from previous versions, and any known bugs upon general availability.
|
||||
|
||||
External DNS Operator 1.3.3::
|
||||
+
|
||||
The following advisory is available for the External DNS Operator version 1.3.3:
|
||||
+
|
||||
* link:https://access.redhat.com/errata/RHBA-2025:23077[RHBA-2025:23077 Product Enhancement Advisory]
|
||||
|
||||
External DNS Operator 1.3.2::
|
||||
+
|
||||
The following advisory is available for the External DNS Operator version 1.3.2:
|
||||
+
|
||||
* link:https://access.redhat.com/errata/RHEA-2025:22454[RHEA-2025:22454 Product Enhancement Advisory]
|
||||
|
||||
External DNS Operator 1.3.1::
|
||||
+
|
||||
The following advisory is available for the External DNS Operator version 1.3.1:
|
||||
+
|
||||
* link:https://access.redhat.com/errata/RHEA-2025:15598[RHEA-2025:15598 Product Enhancement Advisory]
|
||||
+
|
||||
This update includes improved container security.
|
||||
|
||||
External DNS Operator 1.3.0::
|
||||
+
|
||||
The following advisory is available for the External DNS Operator version 1.3.0:
|
||||
+
|
||||
* link:https://access.redhat.com/errata/RHEA-2024:8550[RHEA-2024:8550 Product Enhancement Advisory]
|
||||
+
|
||||
This update includes a rebase to the 0.14.2 version of the upstream project.
|
||||
+
|
||||
Bug fixes:
|
||||
+
|
||||
* Previously, the ExternalDNS Operator could not deploy operands on HCP clusters. With this release, the Operator deploys operands in a running and ready state. (link:https://issues.redhat.com/browse/OCPBUGS-37059[OCPBUGS-37059])
|
||||
+
|
||||
* Previously, the ExternalDNS Operator was not using RHEL 9 as its building or base images. With this release, RHEL9 is the base. (link:https://issues.redhat.com/browse/OCPBUGS-41683[OCPBUGS-41683])
|
||||
+
|
||||
* Previously, the godoc had a broken link for Infoblox provider. With this release, the godoc is revised for accuracy. Some links are removed while some other are replaced with GitHub permalinks. (link:https://issues.redhat.com/browse/OCPBUGS-36797[OCPBUGS-36797])
|
||||
@@ -6,11 +6,12 @@
|
||||
[id="nw-control-dns-records-public-dns-zone-infoblox_{context}"]
|
||||
= Creating DNS records on a public DNS zone on Infoblox
|
||||
|
||||
You can create DNS records on a public DNS zone on Infoblox by using the External DNS Operator.
|
||||
[role="_abstract"]
|
||||
To create DNS records on Infoblox, use the External DNS Operator. The Operator manages external name resolution for your cluster services.
|
||||
|
||||
.Prerequisites
|
||||
|
||||
* You have access to the OpenShift CLI (`oc`).
|
||||
* You have access to the {oc-first}.
|
||||
* You have access to the Infoblox UI.
|
||||
|
||||
.Procedure
|
||||
@@ -29,7 +30,7 @@ $ oc -n external-dns-operator create secret generic infoblox-credentials --from-
|
||||
$ oc get routes --all-namespaces | grep console
|
||||
----
|
||||
+
|
||||
.Example Output
|
||||
.Example output
|
||||
[source,terminal]
|
||||
----
|
||||
openshift-console console console-openshift-console.apps.test.example.com console https reencrypt/Redirect None
|
||||
@@ -44,10 +45,10 @@ openshift-console downloads downloads-openshift-console.apps.
|
||||
apiVersion: externaldns.olm.openshift.io/v1beta1
|
||||
kind: ExternalDNS
|
||||
metadata:
|
||||
name: sample-infoblox <1>
|
||||
name: sample-infoblox
|
||||
spec:
|
||||
provider:
|
||||
type: Infoblox <2>
|
||||
type: Infoblox
|
||||
infoblox:
|
||||
credentials:
|
||||
name: infoblox-credentials
|
||||
@@ -59,14 +60,20 @@ spec:
|
||||
matchType: Exact
|
||||
name: test.example.com
|
||||
source:
|
||||
type: OpenShiftRoute <3>
|
||||
type: OpenShiftRoute
|
||||
openshiftRouteOptions:
|
||||
routerName: default <4>
|
||||
routerName: default
|
||||
----
|
||||
<1> Specifies the External DNS name.
|
||||
<2> Defines the provider type.
|
||||
<3> You can define options for the source of DNS records.
|
||||
<4> If the source type is `OpenShiftRoute`, you can pass the OpenShift Ingress Controller name. External DNS selects the canonical hostname of that router as the target while creating CNAME record.
|
||||
+
|
||||
where:
|
||||
|
||||
`metadata.name`:: Specifies the External DNS name.
|
||||
|
||||
`provider.type`:: Specifies the provider type.
|
||||
|
||||
`source.type`:: Specifies options for the source of DNS records.
|
||||
|
||||
`routerName`:: If the source type is `OpenShiftRoute`, you can pass the OpenShift Ingress Controller name. External DNS selects the canonical hostname of that router as the target while creating a CNAME record.
|
||||
|
||||
. Create the `ExternalDNS` resource on Infoblox by running the following command:
|
||||
+
|
||||
@@ -76,6 +83,7 @@ $ oc create -f external-dns-sample-infoblox.yaml
|
||||
----
|
||||
|
||||
. From the Infoblox UI, check the DNS records created for `console` routes:
|
||||
|
||||
+
|
||||
.. Click *Data Management* -> *DNS* -> *Zones*.
|
||||
+
|
||||
.. Select the zone name.
|
||||
|
||||
@@ -7,7 +7,8 @@
|
||||
[id="nw-control-dns-records-public-managed-zone-gcp_{context}"]
|
||||
= Creating DNS records on a public managed zone for {gcp-short}
|
||||
|
||||
You can create DNS records on a public managed zone for {gcp-short} by using the External DNS Operator.
|
||||
[role="_abstract"]
|
||||
To create DNS records on {gcp-first}, use the External DNS Operator. The DNS Operator manages external name resolution for your cluster services.
|
||||
|
||||
.Prerequisites
|
||||
|
||||
@@ -72,27 +73,38 @@ $ gcloud dns managed-zones list | grep test.gcp.example.com
|
||||
apiVersion: externaldns.olm.openshift.io/v1beta1
|
||||
kind: ExternalDNS
|
||||
metadata:
|
||||
name: sample-gcp <1>
|
||||
name: sample-gcp
|
||||
spec:
|
||||
domains:
|
||||
- filterType: Include <2>
|
||||
matchType: Exact <3>
|
||||
name: test.gcp.example.com <4>
|
||||
- filterType: Include
|
||||
matchType: Exact
|
||||
name: test.gcp.example.com
|
||||
provider:
|
||||
type: GCP <5>
|
||||
type: GCP
|
||||
source:
|
||||
openshiftRouteOptions: <6>
|
||||
routerName: default <7>
|
||||
type: OpenShiftRoute <8>
|
||||
openshiftRouteOptions:
|
||||
routerName: default
|
||||
type: OpenShiftRoute
|
||||
# ...
|
||||
----
|
||||
<1> Specifies the External DNS name.
|
||||
<2> By default, all hosted zones are selected as potential targets. You can include your hosted zone.
|
||||
<3> The domain of the target must match the string defined by the `name` key.
|
||||
<4> Specify the exact domain of the zone you want to update. The hostname of the routes must be subdomains of the specified domain.
|
||||
<5> Defines the provider type.
|
||||
<6> You can define options for the source of DNS records.
|
||||
<7> If the source type is `OpenShiftRoute`, you can pass the OpenShift Ingress Controller name. External DNS selects the canonical hostname of that router as the target while creating CNAME record.
|
||||
<8> Defines the `route` resource as the source for {gcp-short} DNS records.
|
||||
+
|
||||
where:
|
||||
|
||||
`metadata.name`:: Specifies the External DNS name.
|
||||
|
||||
`spec.domains.filterType`:: By default, all hosted zones are selected as potential targets. You can include your hosted zone.
|
||||
|
||||
`spec.domains.matchType`:: Specifies the domain of the target that must match the string defined by the `name` key.
|
||||
|
||||
`spec.domains.name`:: Specifies the exact domain of the zone you want to update. The hostname of the routes must be subdomains of the specified domain.
|
||||
|
||||
`spec.provider.type`:: Specifies the provider type.
|
||||
|
||||
`source.openshiftRouteOptions`:: Specifies options for the source of DNS records.
|
||||
|
||||
`openshiftRouteOptions.routerName`:: If the source type is `OpenShiftRoute`, you can pass the OpenShift Ingress Controller name. External DNS selects the canonical hostname of that router as the target while creating a CNAME record.
|
||||
|
||||
`type`:: Specifies the `route` resource as the source for {gcp-short} DNS records.
|
||||
|
||||
. Check the DNS records created for {product-title} routes by running the following command:
|
||||
+
|
||||
|
||||
39
modules/nw-external-dns-operator-domain-limitations.adoc
Normal file
39
modules/nw-external-dns-operator-domain-limitations.adoc
Normal file
@@ -0,0 +1,39 @@
|
||||
// Module included in the following assemblies:
|
||||
// * networking/understanding-external-dns-operator.adoc
|
||||
|
||||
:_mod-docs-content-type: REFERENCE
|
||||
[id="nw-external-dns-operator-domain-limitations_{context}"]
|
||||
= External DNS Operator domain name limitations
|
||||
|
||||
[role="_abstract"]
|
||||
To prevent configuration errors when deploying the `ExternalDNS` resource, review the domain name limitations enforced by the External DNS Operator. Understanding these constraints ensures that your requested hostnames and domains are compatible with your underlying DNS provider.
|
||||
|
||||
The External DNS Operator uses the TXT registry that adds the prefix for TXT records. This reduces the maximum length of the domain name for TXT records. A DNS record cannot be present without a corresponding TXT record, so the domain name of the DNS record must follow the same limit as the TXT records. For example, a DNS record of `<domain_name_from_source>` results in a TXT record of `external-dns-<record_type>-<domain_name_from_source>`.
|
||||
|
||||
The domain name of the DNS records generated by the External DNS Operator has the following limitations:
|
||||
|
||||
[cols="3,2",options="header"]
|
||||
|===
|
||||
|Record type |Number of characters
|
||||
|
||||
|CNAME
|
||||
|44
|
||||
|
||||
|Wildcard CNAME records on AzureDNS
|
||||
|42
|
||||
|
||||
|A
|
||||
|48
|
||||
|
||||
|Wildcard A records on AzureDNS
|
||||
|46
|
||||
|
||||
|===
|
||||
|
||||
The following error shows in the External DNS Operator logs if the generated domain name exceeds any of the domain name limitations:
|
||||
|
||||
[source,terminal]
|
||||
----
|
||||
time="2022-09-02T08:53:57Z" level=error msg="Failure in zone test.example.io. [Id: /hostedzone/Z06988883Q0H0RL6UMXXX]"
|
||||
time="2022-09-02T08:53:57Z" level=error msg="InvalidChangeBatch: [FATAL problem: DomainLabelTooLong (Domain label is too long) encountered with 'external-dns-a-hello-openshift-aaaaaaaaaa-bbbbbbbbbb-ccccccc']\n\tstatus code: 400, request id: e54dfd5a-06c6-47b0-bcb9-a4f7c3a4e0c6"
|
||||
----
|
||||
@@ -5,45 +5,14 @@
|
||||
[id="nw-external-dns-operator-logs_{context}"]
|
||||
= Viewing External DNS Operator logs
|
||||
|
||||
You can view External DNS Operator logs by using the `oc logs` command.
|
||||
[role="_abstract"]
|
||||
To troubleshoot DNS configuration issues, view the External DNS Operator logs. Use the `oc logs` command to retrieve diagnostic information directly from the Operator pod.
|
||||
|
||||
.Procedure
|
||||
|
||||
. View the logs of the External DNS Operator by running the following command:
|
||||
* View the logs of the External DNS Operator by running the following command:
|
||||
+
|
||||
[source,terminal]
|
||||
----
|
||||
$ oc logs -n external-dns-operator deployment/external-dns-operator -c external-dns-operator
|
||||
----
|
||||
|
||||
== External DNS Operator domain name limitations
|
||||
|
||||
The External DNS Operator uses the TXT registry which adds the prefix for TXT records. This reduces the maximum length of the domain name for TXT records. A DNS record cannot be present without a corresponding TXT record, so the domain name of the DNS record must follow the same limit as the TXT records. For example, a DNS record of `<domain_name_from_source>` results in a TXT record of `external-dns-<record_type>-<domain_name_from_source>`.
|
||||
|
||||
The domain name of the DNS records generated by the External DNS Operator has the following limitations:
|
||||
|
||||
[cols="3a,8a",options="header"]
|
||||
|===
|
||||
|Record type |Number of characters
|
||||
|
||||
|CNAME
|
||||
|44
|
||||
|
||||
|Wildcard CNAME records on AzureDNS
|
||||
|42
|
||||
|
||||
|A
|
||||
|48
|
||||
|
||||
|Wildcard A records on AzureDNS
|
||||
|46
|
||||
|
||||
|===
|
||||
|
||||
The following error appears in the External DNS Operator logs if the generated domain name exceeds any of the domain name limitations:
|
||||
|
||||
[source,terminal]
|
||||
----
|
||||
time="2022-09-02T08:53:57Z" level=error msg="Failure in zone test.example.io. [Id: /hostedzone/Z06988883Q0H0RL6UMXXX]"
|
||||
time="2022-09-02T08:53:57Z" level=error msg="InvalidChangeBatch: [FATAL problem: DomainLabelTooLong (Domain label is too long) encountered with 'external-dns-a-hello-openshift-aaaaaaaaaa-bbbbbbbbbb-ccccccc']\n\tstatus code: 400, request id: e54dfd5a-06c6-47b0-bcb9-a4f7c3a4e0c6"
|
||||
----
|
||||
|
||||
@@ -3,7 +3,10 @@
|
||||
|
||||
:_mod-docs-content-type: PROCEDURE
|
||||
[id="nw-external-dns-operator_{context}"]
|
||||
= External DNS Operator
|
||||
= Deploying the External DNS Operator
|
||||
|
||||
[role="_abstract"]
|
||||
You can deploy the External DNS Operator on-demand from the Software Catalog. Deploying the External DNS Operator creates a `Subscription` object.
|
||||
|
||||
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.
|
||||
|
||||
@@ -13,8 +16,6 @@ The External DNS Operator implements the External DNS API from the `olm.openshif
|
||||
|
||||
.Procedure
|
||||
|
||||
You can deploy the External DNS Operator on demand from the software catalog. Deploying the External DNS Operator creates a `Subscription` object.
|
||||
|
||||
. Check the name of an install plan, such as `install-zcvlr`, by running the following command:
|
||||
+
|
||||
[source,terminal]
|
||||
|
||||
@@ -6,18 +6,17 @@
|
||||
[id="nw-installing-external-dns-operator-cli_{context}"]
|
||||
= Installing the External DNS Operator by using the CLI
|
||||
|
||||
You can install the External DNS Operator by using the CLI.
|
||||
[role="_abstract"]
|
||||
You can use the {oc-first} to install the External DNS Operator. The Operator manages the installation process directly from your terminal without you having to use the web console.
|
||||
|
||||
.Prerequisites
|
||||
|
||||
* You are logged in to the {product-title} web console as a user with `cluster-admin` permissions.
|
||||
|
||||
* You are logged into the OpenShift CLI (`oc`).
|
||||
* You are logged in to the {oc-first}.
|
||||
|
||||
.Procedure
|
||||
|
||||
. Create a `Namespace` object:
|
||||
|
||||
+
|
||||
.. Create a YAML file that defines the `Namespace` object:
|
||||
+
|
||||
.Example `namespace.yaml` file
|
||||
@@ -27,8 +26,9 @@ apiVersion: v1
|
||||
kind: Namespace
|
||||
metadata:
|
||||
name: external-dns-operator
|
||||
# ...
|
||||
----
|
||||
|
||||
+
|
||||
.. Create the `Namespace` object by running the following command:
|
||||
+
|
||||
[source,terminal]
|
||||
@@ -37,7 +37,7 @@ $ oc apply -f namespace.yaml
|
||||
----
|
||||
|
||||
. Create an `OperatorGroup` object:
|
||||
|
||||
+
|
||||
.. Create a YAML file that defines the `OperatorGroup` object:
|
||||
+
|
||||
.Example `operatorgroup.yaml` file
|
||||
@@ -52,8 +52,9 @@ spec:
|
||||
upgradeStrategy: Default
|
||||
targetNamespaces:
|
||||
- external-dns-operator
|
||||
# ...
|
||||
----
|
||||
|
||||
+
|
||||
.. Create the `OperatorGroup` object by running the following command:
|
||||
+
|
||||
[source,terminal]
|
||||
@@ -62,7 +63,7 @@ $ oc apply -f operatorgroup.yaml
|
||||
----
|
||||
|
||||
. Create a `Subscription` object:
|
||||
|
||||
+
|
||||
.. Create a YAML file that defines the `Subscription` object:
|
||||
+
|
||||
.Example `subscription.yaml` file
|
||||
@@ -79,8 +80,9 @@ spec:
|
||||
name: external-dns-operator
|
||||
source: redhat-operators
|
||||
sourceNamespace: openshift-marketplace
|
||||
# ...
|
||||
----
|
||||
|
||||
+
|
||||
.. Create the `Subscription` object by running the following command:
|
||||
+
|
||||
[source,terminal]
|
||||
|
||||
@@ -4,29 +4,37 @@
|
||||
|
||||
:_mod-docs-content-type: PROCEDURE
|
||||
[id="nw-installing-external-dns-operator_{context}"]
|
||||
= Installing the External DNS Operator with the software catalog
|
||||
= Installing the External DNS Operator with the Software Catalog
|
||||
|
||||
You can install the External DNS Operator by using the {product-title} software catalog.
|
||||
[role="_abstract"]
|
||||
You can install the External DNS Operator by using the {product-title} Software Catalog. You can then manage the Operator lifecycle directly from the web console.
|
||||
|
||||
.Procedure
|
||||
|
||||
. Click *Ecosystem* -> *Software Catalog* in the {product-title} web console.
|
||||
. Click *External DNS Operator*.
|
||||
You can use the *Filter by keyword* text box or the filter list to search for External DNS Operator from the list of Operators.
|
||||
|
||||
. Click *External DNS Operator*. You can use the *Filter by keyword* text box or the filter list to search for External DNS Operator from the list of Operators.
|
||||
|
||||
. Select the `external-dns-operator` namespace.
|
||||
|
||||
. On the *External DNS Operator* page, click *Install*.
|
||||
|
||||
. On the *Install Operator* page, ensure that you selected the following options:
|
||||
+
|
||||
.. Update the channel as *stable-v1*.
|
||||
+
|
||||
.. Installation mode as *A specific name on the cluster*.
|
||||
.. Installed namespace as `external-dns-operator`. If namespace `external-dns-operator` does not exist, it gets created during the Operator installation.
|
||||
.. Select *Approval Strategy* as *Automatic* or *Manual*. Approval Strategy is set to *Automatic* by default.
|
||||
+
|
||||
.. Installed namespace as `external-dns-operator`. If namespace `external-dns-operator` does not exist, the Operator gets created during the Operator installation.
|
||||
+
|
||||
.. Select *Approval Strategy* as *Automatic* or *Manual*. The Approval Strategy defaults to *Automatic*.
|
||||
+
|
||||
.. Click *Install*.
|
||||
|
||||
+
|
||||
If you select *Automatic* updates, the Operator Lifecycle Manager (OLM) automatically upgrades the running instance of your Operator without any intervention.
|
||||
|
||||
+
|
||||
If you select *Manual* updates, the OLM creates an update request. As a cluster administrator, you must then manually approve that update request to have the Operator updated to the new version.
|
||||
|
||||
|
||||
.Verification
|
||||
|
||||
Verify that the External DNS Operator shows the *Status* as *Succeeded* on the *Installed Operators* dashboard.
|
||||
* Verify that the External DNS Operator shows the *Status* as *Succeeded* on the *Installed Operators* dashboard.
|
||||
|
||||
@@ -16,99 +16,16 @@ The External DNS Operator is only supported on the `x86_64` architecture.
|
||||
|
||||
These release notes track the development of the External DNS Operator in {product-title}.
|
||||
|
||||
[id="external-dns-operator-release-notes-1.3.3"]
|
||||
== External DNS Operator 1.3.3
|
||||
include::modules/external-dns-operator-release-notes-1.3.adoc[leveloffset=+1]
|
||||
|
||||
The following advisory is available for the External DNS Operator version 1.3.3:
|
||||
include::modules/external-dns-operator-release-notes-1.2.adoc[leveloffset=+1]
|
||||
|
||||
* link:https://access.redhat.com/errata/RHBA-2025:23077[RHBA-2025:23077 Product Enhancement Advisory]
|
||||
[role="_additional-resources"]
|
||||
.Additional resources
|
||||
|
||||
[id="external-dns-operator-release-notes-1.3.2"]
|
||||
== External DNS Operator 1.3.2
|
||||
* xref:../../../networking/networking_operators/external_dns_operator/nw-creating-dns-records-on-aws.adoc#nw-control-dns-records-public-aws-with-VPC_creating-dns-records-on-aws[Creating DNS records in a different {aws-short} Account using a shared VPC]
|
||||
|
||||
The following advisory is available for the External DNS Operator version 1.3.2:
|
||||
include::modules/external-dns-operator-release-notes-1.1.adoc[leveloffset=+1]
|
||||
|
||||
* link:https://access.redhat.com/errata/RHEA-2025:22454[RHEA-2025:22454 Product Enhancement Advisory]
|
||||
include::modules/external-dns-operator-release-notes-1.0.adoc[leveloffset=+1]
|
||||
|
||||
[id="external-dns-operator-release-notes-1.3.1"]
|
||||
== External DNS Operator 1.3.1
|
||||
|
||||
The following advisory is available for the External DNS Operator version 1.3.1:
|
||||
|
||||
* link:https://access.redhat.com/errata/RHEA-2025:15598[RHEA-2025:15598 Product Enhancement Advisory]
|
||||
|
||||
This update includes improved container security.
|
||||
|
||||
[id="external-dns-operator-release-notes-1.3.0"]
|
||||
== External DNS Operator 1.3.0
|
||||
|
||||
The following advisory is available for the External DNS Operator version 1.3.0:
|
||||
|
||||
* link:https://access.redhat.com/errata/RHEA-2024:8550[RHEA-2024:8550 Product Enhancement Advisory]
|
||||
|
||||
This update includes a rebase to the 0.14.2 version of the upstream project.
|
||||
|
||||
[id="external-dns-operator-.3.0-bug-fixes"]
|
||||
=== Bug fixes
|
||||
|
||||
Previously, the ExternalDNS Operator could not deploy operands on HCP clusters. With this release, the Operator deploys operands in a running and ready state. (link:https://issues.redhat.com/browse/OCPBUGS-37059[*OCPBUGS-37059*])
|
||||
|
||||
Previously, the ExternalDNS Operator was not using RHEL 9 as its building or base images. With this release, RHEL9 is the base. (link:https://issues.redhat.com/browse/OCPBUGS-41683[*OCPBUGS-41683*])
|
||||
|
||||
Previously, the godoc had a broken link for Infoblox provider. With this release, the godoc is revised for accuracy. Some links are removed while some other are replaced with GitHub permalinks. (link:https://issues.redhat.com/browse/OCPBUGS-36797[*OCPBUGS-36797*])
|
||||
|
||||
[id="external-dns-operator-release-notes-1.2.0"]
|
||||
== External DNS Operator 1.2.0
|
||||
|
||||
The following advisory is available for the External DNS Operator version 1.2.0:
|
||||
|
||||
* link:https://access.redhat.com/errata/RHEA-2023:7239[RHEA-2022:5867 ExternalDNS Operator 1.2 operator/operand containers]
|
||||
|
||||
[id="external-dns-operator-1.2.0-new-features"]
|
||||
=== New features
|
||||
|
||||
* The External DNS Operator now supports {aws-short} shared VPC. For more information, see xref:../../../networking/networking_operators/external_dns_operator/nw-creating-dns-records-on-aws.adoc#nw-control-dns-records-public-aws-with-VPC_creating-dns-records-on-aws[Creating DNS records in a different {aws-short} Account using a shared VPC].
|
||||
|
||||
[id="external-dns-operator-1.2.0-bug-fixes"]
|
||||
=== Bug fixes
|
||||
|
||||
* The update strategy for the operand changed from `Rolling` to `Recreate`. (link:https://issues.redhat.com/browse/OCPBUGS-3630[*OCPBUGS-3630*])
|
||||
|
||||
[id="external-dns-operator-release-notes-1.1.1"]
|
||||
== External DNS Operator 1.1.1
|
||||
|
||||
The following advisory is available for the External DNS Operator version 1.1.1:
|
||||
|
||||
* link:https://access.redhat.com/errata/RHEA-2024:0536[RHEA-2024:0536 ExternalDNS Operator 1.1 operator/operand containers]
|
||||
|
||||
[id="external-dns-operator-release-notes-1.1.0"]
|
||||
== External DNS Operator 1.1.0
|
||||
|
||||
This release included a rebase of the operand from the upstream project version 0.13.1. The following advisory is available for the External DNS Operator version 1.1.0:
|
||||
|
||||
* link:https://access.redhat.com/errata/RHEA-2022:9086[RHEA-2022:9086-01 ExternalDNS Operator 1.1 operator/operand containers]
|
||||
|
||||
[id="external-dns-operator-1.1.0-bug-fix"]
|
||||
=== Bug fixes
|
||||
|
||||
* Previously, the ExternalDNS Operator enforced an empty `defaultMode` value for volumes, which caused constant updates due to a conflict with the OpenShift API. Now, the `defaultMode` value is not enforced and operand deployment does not update constantly. (link:https://issues.redhat.com/browse/OCPBUGS-2793[*OCPBUGS-2793*])
|
||||
|
||||
[id="external-dns-operator-release-notes-1.0.1"]
|
||||
== External DNS Operator 1.0.1
|
||||
|
||||
The following advisory is available for the External DNS Operator version 1.0.1:
|
||||
|
||||
* link:https://access.redhat.com/errata/RHEA-2024:0537[RHEA-2024:0537 ExternalDNS Operator 1.0 operator/operand containers]
|
||||
|
||||
|
||||
[id="external-dns-operator-release-notes-1.0.0"]
|
||||
== External DNS Operator 1.0.0
|
||||
|
||||
The following advisory is available for the External DNS Operator version 1.0.0:
|
||||
|
||||
* link:https://access.redhat.com/errata/RHEA-2022:5867[RHEA-2022:5867 ExternalDNS Operator 1.0 operator/operand containers]
|
||||
|
||||
[id="external-dns-operator-1.0.0-bug-fixes"]
|
||||
=== Bug fixes
|
||||
|
||||
* Previously, the External DNS Operator issued a warning about the violation of the restricted SCC policy during ExternalDNS operand pod deployments. This issue has been resolved. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2086408[*BZ#2086408*])
|
||||
@@ -1,12 +1,13 @@
|
||||
:_mod-docs-content-type: ASSEMBLY
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
[id="creating-dns-records-on-gcp"]
|
||||
= Creating DNS records on {gcp-short}
|
||||
= Creating DNS records on Google Cloud Platform
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
:context: creating-dns-records-on-gcp
|
||||
|
||||
toc::[]
|
||||
|
||||
You can create DNS records on {gcp-first} by using the External DNS Operator.
|
||||
[role="_abstract"]
|
||||
To create DNS records on {gcp-first}, use the External DNS Operator. The DNS Operator manages external name resolution for your cluster services.
|
||||
|
||||
[IMPORTANT]
|
||||
====
|
||||
|
||||
@@ -6,6 +6,8 @@ include::_attributes/common-attributes.adoc[]
|
||||
|
||||
toc::[]
|
||||
|
||||
You can create DNS records on Infoblox by using the External DNS Operator.
|
||||
[role="_abstract"]
|
||||
To create DNS records on Infoblox, use the External DNS Operator. The Operator manages external name resolution for your cluster services.
|
||||
|
||||
|
||||
include::modules/nw-control-dns-records-public-hosted-zone-infoblox.adoc[leveloffset=+1]
|
||||
|
||||
@@ -6,7 +6,8 @@ include::_attributes/common-attributes.adoc[]
|
||||
|
||||
toc::[]
|
||||
|
||||
You can install the External DNS Operator on cloud providers such as AWS, Azure, and {gcp-short}.
|
||||
[role="_abstract"]
|
||||
To manage DNS records on your cloud infrastructure, install the External DNS Operator. This Operator supports deployment on major cloud providers, including {aws-first}, {azure-first}, and {gcp-first}.
|
||||
|
||||
// Installing the External DNS Operator with OperatorHub
|
||||
include::modules/nw-installing-external-dns-operator.adoc[leveloffset=+1]
|
||||
|
||||
@@ -6,7 +6,11 @@ include::_attributes/common-attributes.adoc[]
|
||||
|
||||
toc::[]
|
||||
|
||||
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}.
|
||||
[role="_abstract"]
|
||||
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.
|
||||
|
||||
// External DNS Operator domain name limitations
|
||||
include::modules/nw-external-dns-operator-domain-limitations.adoc[leveloffset=+1]
|
||||
|
||||
// External DNS Operator
|
||||
include::modules/nw-external-dns-operator.adoc[leveloffset=+1]
|
||||
|
||||
Reference in New Issue
Block a user