Skip to content

CORS-3993: Promote GCPClusterHostedDNS to Default - #2300

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:masterfrom
sadasu:gcp-custom-dns-ga
Sep 11, 2025
Merged

CORS-3993: Promote GCPClusterHostedDNS to Default#2300
openshift-merge-bot[bot] merged 1 commit into
openshift:masterfrom
sadasu:gcp-custom-dns-ga

Conversation

@sadasu

@sadasusadasu commented Apr 29, 2025

Copy link
Copy Markdown
Contributor

Promotes GCP Cluster Hosted DNS feature from techpreview to available by default.

@openshift-ci

Copy link
Copy Markdown
Contributor

Hello @sadasu! Some important instructions when contributing to openshift/api:
API design plays an important part in the user experience of OpenShift and as such API PRs are subject to a high level of scrutiny to ensure they follow our best practices. If you haven't already done so, please review the OpenShift API Conventions and ensure that your proposed changes are compliant. Following these conventions will help expedite the api review process for your PR.

@openshift-ciopenshift-ciBot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Apr 29, 2025
@sadasusadasu changed the title Promote GCPClusterHostedDNS to DefaultCORS-3993: Promote GCPClusterHostedDNS to DefaultApr 29, 2025
@openshift-ci-robotopenshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 29, 2025
@openshift-ci-robot

openshift-ci-robot commented Apr 29, 2025

Copy link
Copy Markdown

@sadasu: This pull request references CORS-3993 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

Details

In response to this:

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.

@sadasu

Copy link
Copy Markdown
ContributorAuthor

/jira refresh

@openshift-ci-robot

openshift-ci-robot commented Apr 29, 2025

Copy link
Copy Markdown

@sadasu: This pull request references CORS-3993 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

Details

In response to this:

/jira refresh

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.

@sadasu

Copy link
Copy Markdown
ContributorAuthor

/jira refresh

@openshift-ci-robot

openshift-ci-robot commented Apr 29, 2025

Copy link
Copy Markdown

@sadasu: This pull request references CORS-3993 which is a valid jira issue.

Details

In response to this:

/jira refresh

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-ciopenshift-ciBot added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Apr 29, 2025
@sadasu
sadasuforce-pushed the gcp-custom-dns-ga branch 2 times, most recently from 742fbce to b385a03CompareApril 30, 2025 02:09
@openshift-ciopenshift-ciBot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Apr 30, 2025
@openshift-merge-robotopenshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label May 12, 2025
@sadasu
sadasuforce-pushed the gcp-custom-dns-ga branch from d668c33 to 4a7fe43CompareMay 27, 2025 20:15
@openshift-merge-robotopenshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label May 27, 2025
@sadasu
sadasuforce-pushed the gcp-custom-dns-ga branch 2 times, most recently from 0a623cf to b2df60cCompareMay 27, 2025 21:56
@sadasu
sadasuforce-pushed the gcp-custom-dns-ga branch from b2df60c to aff303cCompareJuly 24, 2025 15:00
@openshift-merge-robotopenshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 24, 2025
@sadasu
sadasuforce-pushed the gcp-custom-dns-ga branch from aff303c to d45b615CompareJuly 24, 2025 17:12
@openshift-merge-robotopenshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 24, 2025
This promotes GCP Cluster Hosted DNS feature from techpreview to
available by default.
@openshift-ciopenshift-ciBot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 8, 2025
@JoelSpeed

Copy link
Copy Markdown
Contributor

@sadasu The custom DNS job that was set up to monitor this feature is currently only configured for 4.20 and only for tech preview. We will need to also have the job created for 4.21 and, then once this is merged, moved from tech preview to the stable feature set right?

@sadasu

sadasu commented Sep 8, 2025

Copy link
Copy Markdown
ContributorAuthor

@sadasu The custom DNS job that was set up to monitor this feature is currently only configured for 4.20 and only for tech preview. We will need to also have the job created for 4.21 and, then once this is merged, moved from tech preview to the stable feature set right?

The 4.21 techpreview periodic job already exists. I have triggered some manual runs.

@gpei

gpei commented Sep 9, 2025

Copy link
Copy Markdown

/verified later @gpei

@openshift-ci-robotopenshift-ci-robot added verified-later verified Signifies that the PR passed pre-merge verification criteria labels Sep 9, 2025
@openshift-ci-robot

Copy link
Copy Markdown

@gpei: This PR has been marked to be verified later by @gpei.

Details

In response to this:

/verified later @gpei

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

Copy link
Copy Markdown

/retest-required

Remaining retests: 0 against base HEAD 8634aa4 and 2 for PR HEAD 677781c in total

1 similar comment
@openshift-ci-robot

Copy link
Copy Markdown

/retest-required

Remaining retests: 0 against base HEAD 8634aa4 and 2 for PR HEAD 677781c in total

@gpei

gpei commented Sep 9, 2025

Copy link
Copy Markdown

/retest-required

@gpei

gpei commented Sep 9, 2025

Copy link
Copy Markdown

/test e2e-aws-ovn-hypershift

@openshift-ci-robot

Copy link
Copy Markdown

/retest-required

Remaining retests: 0 against base HEAD be976da and 1 for PR HEAD 677781c in total

@JoelSpeed

Copy link
Copy Markdown
Contributor

/override ci/prow/e2e-aws-serial-2of2

Commatrix failure is a known test harness issue

/retest-required

@openshift-ci

Copy link
Copy Markdown
Contributor

@JoelSpeed: Overrode contexts on behalf of JoelSpeed: ci/prow/e2e-aws-serial-2of2

Details

In response to this:

/override ci/prow/e2e-aws-serial-2of2

Commatrix failure is a known test harness issue

/retest-required

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.

@openshift-ci-robot

Copy link
Copy Markdown

/retest-required

Remaining retests: 0 against base HEAD be976da and 2 for PR HEAD 677781c in total

@sadasu

Copy link
Copy Markdown
ContributorAuthor

e2e-aws-ovn-hypershift* jobs are having a high failure rate but have nothing to do with this feature because of the current feature being on the GCP platform. Monitoring them closely to see if they are candidates to be overridden also.

@openshift-ci-robot

Copy link
Copy Markdown

/retest-required

Remaining retests: 0 against base HEAD be976da and 2 for PR HEAD 677781c in total

@sadasu

Copy link
Copy Markdown
ContributorAuthor

/override ci/prow/e2e-aws-serial-2of2

Based on comment #2300 (comment)

@openshift-ci

Copy link
Copy Markdown
Contributor

@sadasu: sadasu unauthorized: /override is restricted to Repo administrators, approvers in top level OWNERS file, and the following github teams:openshift: openshift-release-oversight openshift-staff-engineers openshift-sustaining-engineers.

Details

In response to this:

/override ci/prow/e2e-aws-serial-2of2

Based on comment #2300 (comment)

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.

@openshift-ci-robot

Copy link
Copy Markdown

/retest-required

Remaining retests: 0 against base HEAD be976da and 2 for PR HEAD 677781c in total

3 similar comments
@openshift-ci-robot

Copy link
Copy Markdown

/retest-required

Remaining retests: 0 against base HEAD be976da and 2 for PR HEAD 677781c in total

@openshift-ci-robot

Copy link
Copy Markdown

/retest-required

Remaining retests: 0 against base HEAD be976da and 2 for PR HEAD 677781c in total

@openshift-ci-robot

Copy link
Copy Markdown

/retest-required

Remaining retests: 0 against base HEAD be976da and 2 for PR HEAD 677781c in total

@JoelSpeed

Copy link
Copy Markdown
Contributor

/override ci/prow/e2e-aws-ovn-hypershift
/override ci/prow/e2e-aws-ovn-hypershift-conformance

This feature won't affect HCP or AWS, so I'm confident overriding these is going to be fine

@openshift-ci

Copy link
Copy Markdown
Contributor

@JoelSpeed: Overrode contexts on behalf of JoelSpeed: ci/prow/e2e-aws-ovn-hypershift, ci/prow/e2e-aws-ovn-hypershift-conformance

Details

In response to this:

/override ci/prow/e2e-aws-ovn-hypershift
/override ci/prow/e2e-aws-ovn-hypershift-conformance

This feature won't affect HCP or AWS, so I'm confident overriding these is going to be fine

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.

@openshift-ci-robot

Copy link
Copy Markdown

/retest-required

Remaining retests: 0 against base HEAD e515d9c and 2 for PR HEAD 677781c in total

@openshift-ci

openshift-ciBot commented Sep 11, 2025

Copy link
Copy Markdown
Contributor

@sadasu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test nameCommitDetailsRequiredRerun command
ci/prow/e2e-aws-serial-techpreviewd668c33linktrue/test e2e-aws-serial-techpreview

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.

@gpei

gpei commented Sep 11, 2025

Copy link
Copy Markdown

/test e2e-aws-serial-2of2

@openshift-merge-bot
openshift-merge-botBot merged commit 9116741 into openshift:masterSep 11, 2025
27 checks passed
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approvedIndicates a PR has been approved by an approver from all required OWNERS files.jira/valid-referenceIndicates that this PR references a valid Jira ticket of any type.lgtmIndicates that a PR is ready to be merged.size/LDenotes a PR that changes 100-499 lines, ignoring generated files.verifiedSignifies that the PR passed pre-merge verification criteriaverified-later

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants

@sadasu@openshift-ci-robot@gpei@JoelSpeed@candita@patrickdillon@openshift-merge-robot