Skip to content

CORS-4137: add CoreDNS upstream resolver config for dual-stack clusters#10362

Open
tthvo wants to merge 1 commit intoopenshift:mainfrom
tthvo:CORS-4137
Open

CORS-4137: add CoreDNS upstream resolver config for dual-stack clusters#10362
tthvo wants to merge 1 commit intoopenshift:mainfrom
tthvo:CORS-4137

Conversation

@tthvo
Copy link
Member

@tthvo tthvo commented Mar 4, 2026

In AWS dual-stack subnets, the resolver config file on instances only defines the IPv4 DNS resolver by default. This adds CoreDNS configuration to include the IPv6 DNS resolver (fd00:ec2::253) as an upstream resolver for dual-stack AWS clusters.

The CoreDNS operator config uses sequential forwarding policy to check the system resolver first, then the IPv6 AWS DNS resolver.

In AWS dual-stack subnets, the resolver config file on instances only
defines the IPv4 DNS resolver by default. This adds CoreDNS configuration
to include the IPv6 DNS resolver (fd00:ec2::253) as an upstream resolver
for dual-stack AWS clusters.

The CoreDNS operator config uses sequential forwarding policy to check
the system resolver first, then the IPv6 AWS DNS resolver.
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Mar 4, 2026

@tthvo: This pull request references CORS-4137 which is a valid jira issue.

Details

In response to this:

In AWS dual-stack subnets, the resolver config file on instances only defines the IPv4 DNS resolver by default. This adds CoreDNS configuration to include the IPv6 DNS resolver (fd00:ec2::253) as an upstream resolver for dual-stack AWS clusters.

The CoreDNS operator config uses sequential forwarding policy to check the system resolver first, then the IPv6 AWS DNS resolver.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 4, 2026
@openshift-ci openshift-ci bot requested review from andfasano and rwsu March 4, 2026 23:15
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 4, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign jcpowermac for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tthvo
Copy link
Member Author

tthvo commented Mar 4, 2026

/uncc @andfasano @rwsu
/cc @sadasu @patrickdillon

@openshift-ci openshift-ci bot requested review from patrickdillon and sadasu and removed request for andfasano and rwsu March 4, 2026 23:16
@tthvo
Copy link
Member Author

tthvo commented Mar 4, 2026

/jira cc-qa

FYI 😁

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Mar 4, 2026

@tthvo: This pull request references CORS-4137 which is a valid jira issue.

Requesting review from QA contact:
/cc @yunjiang29

Details

In response to this:

/jira cc-qa

FYI 😁

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested a review from yunjiang29 March 4, 2026 23:17
@tthvo
Copy link
Member Author

tthvo commented Mar 4, 2026

/label platform/aws

@tthvo
Copy link
Member Author

tthvo commented Mar 5, 2026

/test artifacts-images

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 5, 2026

@tthvo: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. platform/aws

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants