Skip to content

CORS-4029: Promote AzureClusterHostedDNS to default#2774

Open
sadasu wants to merge 1 commit intoopenshift:masterfrom
sadasu:azureClusterHostedDNS-default
Open

CORS-4029: Promote AzureClusterHostedDNS to default#2774
sadasu wants to merge 1 commit intoopenshift:masterfrom
sadasu:azureClusterHostedDNS-default

Conversation

@sadasu
Copy link
Contributor

@sadasu sadasu commented Mar 23, 2026

No description provided.

@openshift-ci-robot
Copy link

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 23, 2026

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-ci openshift-ci bot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Mar 23, 2026
@coderabbitai
Copy link

coderabbitai bot commented Mar 23, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: add14027-5457-44dc-ac89-20f50b694323

📥 Commits

Reviewing files that changed from the base of the PR and between f1fa34a and c67875d.

⛔ Files ignored due to path filters (5)
  • config/v1/zz_generated.crd-manifests/0000_10_config-operator_01_infrastructures-Default.crd.yaml is excluded by !**/zz_generated.crd-manifests/*
  • config/v1/zz_generated.crd-manifests/0000_10_config-operator_01_infrastructures-OKD.crd.yaml is excluded by !**/zz_generated.crd-manifests/*
  • machineconfiguration/v1/zz_generated.crd-manifests/0000_80_machine-config_01_controllerconfigs-Default.crd.yaml is excluded by !**/zz_generated.crd-manifests/*
  • machineconfiguration/v1/zz_generated.crd-manifests/0000_80_machine-config_01_controllerconfigs-OKD.crd.yaml is excluded by !**/zz_generated.crd-manifests/*
  • openapi/openapi.json is excluded by !openapi/**
📒 Files selected for processing (12)
  • config/v1/tests/infrastructures.config.openshift.io/AAA_ungated.yaml
  • config/v1/tests/infrastructures.config.openshift.io/AzureClusterHostedDNSInstall.yaml
  • features.md
  • features/features.go
  • payload-manifests/crds/0000_10_config-operator_01_infrastructures-Default.crd.yaml
  • payload-manifests/crds/0000_10_config-operator_01_infrastructures-OKD.crd.yaml
  • payload-manifests/crds/0000_80_machine-config_01_controllerconfigs-Default.crd.yaml
  • payload-manifests/crds/0000_80_machine-config_01_controllerconfigs-OKD.crd.yaml
  • payload-manifests/featuregates/featureGate-4-10-Hypershift-Default.yaml
  • payload-manifests/featuregates/featureGate-4-10-Hypershift-OKD.yaml
  • payload-manifests/featuregates/featureGate-4-10-SelfManagedHA-Default.yaml
  • payload-manifests/featuregates/featureGate-4-10-SelfManagedHA-OKD.yaml
✅ Files skipped from review due to trivial changes (2)
  • payload-manifests/featuregates/featureGate-4-10-SelfManagedHA-Default.yaml
  • payload-manifests/crds/0000_80_machine-config_01_controllerconfigs-Default.crd.yaml
🚧 Files skipped from review as they are similar to previous changes (4)
  • payload-manifests/featuregates/featureGate-4-10-Hypershift-Default.yaml
  • payload-manifests/featuregates/featureGate-4-10-Hypershift-OKD.yaml
  • features/features.go
  • payload-manifests/crds/0000_10_config-operator_01_infrastructures-OKD.crd.yaml

📝 Walkthrough

Walkthrough

This pull request introduces Azure cluster-hosted DNS configuration support. It adds a new cloudLoadBalancerConfig schema to Azure platform specifications across multiple CRD files, with fields for selecting DNS type (PlatformDefault or ClusterHosted) and optionally specifying load balancer IPs. The AzureClusterHostedDNSInstall feature gate is expanded to include Default and OKD release eligibility, and is enabled in corresponding feature gate manifests. Test configurations are updated to validate the new schema fields and disable the AzureDualStackInstall feature gate.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 golangci-lint (2.11.3)

Error: build linters: unable to load custom analyzer "kubeapilinter": tools/_output/bin/kube-api-linter.so, plugin: not implemented
The command is terminated due to an error: build linters: unable to load custom analyzer "kubeapilinter": tools/_output/bin/kube-api-linter.so, plugin: not implemented


Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci openshift-ci bot requested review from JoelSpeed and sinnykumari March 23, 2026 21:34
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 23, 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 joelspeed 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

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
config/v1/tests/infrastructures.config.openshift.io/AAA_ungated.yaml (1)

387-388: Add targeted Azure cloudLoadBalancerConfig validation tests.

This expected-output update verifies defaulting, but it would be safer to also cover dnsType immutability and clusterHosted conditional validation in dedicated cases to reduce regression risk.

As per coding guidelines, "Focus on major issues impacting performance, readability, maintainability and security. Avoid nitpicks and avoid verbosity."

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@config/v1/tests/infrastructures.config.openshift.io/AAA_ungated.yaml` around
lines 387 - 388, Add two focused tests around cloudLoadBalancerConfig: one to
assert dnsType immutability and another to assert clusterHosted conditional
validation. Specifically, in the tests for the infrastructure OpenShift config
(the AAA_ungated.yaml test suite) add a case that attempts to change
cloudLoadBalancerConfig.dnsType after creation and expects a validation error
(verify behavior of the immutability rule for dnsType), and add a case that
supplies clusterHosted=true/false combinations with and without the required
platform-specific fields to confirm conditional validation for clusterHosted is
enforced. Reference the cloudLoadBalancerConfig, dnsType and clusterHosted
fields in the new tests so they explicitly exercise those validations and update
expected outputs accordingly.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@config/v1/tests/infrastructures.config.openshift.io/AAA_ungated.yaml`:
- Around line 387-388: Add two focused tests around cloudLoadBalancerConfig: one
to assert dnsType immutability and another to assert clusterHosted conditional
validation. Specifically, in the tests for the infrastructure OpenShift config
(the AAA_ungated.yaml test suite) add a case that attempts to change
cloudLoadBalancerConfig.dnsType after creation and expects a validation error
(verify behavior of the immutability rule for dnsType), and add a case that
supplies clusterHosted=true/false combinations with and without the required
platform-specific fields to confirm conditional validation for clusterHosted is
enforced. Reference the cloudLoadBalancerConfig, dnsType and clusterHosted
fields in the new tests so they explicitly exercise those validations and update
expected outputs accordingly.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: ce88a19d-6671-40ae-8679-7ba976a21be4

📥 Commits

Reviewing files that changed from the base of the PR and between 324a1bc and eda8c3c.

⛔ Files ignored due to path filters (5)
  • config/v1/zz_generated.crd-manifests/0000_10_config-operator_01_infrastructures-Default.crd.yaml is excluded by !**/zz_generated.crd-manifests/*
  • config/v1/zz_generated.crd-manifests/0000_10_config-operator_01_infrastructures-OKD.crd.yaml is excluded by !**/zz_generated.crd-manifests/*
  • machineconfiguration/v1/zz_generated.crd-manifests/0000_80_machine-config_01_controllerconfigs-Default.crd.yaml is excluded by !**/zz_generated.crd-manifests/*
  • machineconfiguration/v1/zz_generated.crd-manifests/0000_80_machine-config_01_controllerconfigs-OKD.crd.yaml is excluded by !**/zz_generated.crd-manifests/*
  • openapi/openapi.json is excluded by !openapi/**
📒 Files selected for processing (11)
  • config/v1/tests/infrastructures.config.openshift.io/AAA_ungated.yaml
  • features.md
  • features/features.go
  • payload-manifests/crds/0000_10_config-operator_01_infrastructures-Default.crd.yaml
  • payload-manifests/crds/0000_10_config-operator_01_infrastructures-OKD.crd.yaml
  • payload-manifests/crds/0000_80_machine-config_01_controllerconfigs-Default.crd.yaml
  • payload-manifests/crds/0000_80_machine-config_01_controllerconfigs-OKD.crd.yaml
  • payload-manifests/featuregates/featureGate-4-10-Hypershift-Default.yaml
  • payload-manifests/featuregates/featureGate-4-10-Hypershift-OKD.yaml
  • payload-manifests/featuregates/featureGate-4-10-SelfManagedHA-Default.yaml
  • payload-manifests/featuregates/featureGate-4-10-SelfManagedHA-OKD.yaml

@sadasu sadasu changed the title Promote AzureClusterHostedDNS to default CORS-4029: Promote AzureClusterHostedDNS to default Mar 23, 2026
@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 23, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Mar 23, 2026

@sadasu: This pull request references CORS-4029 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.22.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
Contributor Author

sadasu commented Mar 23, 2026

/jira refresh

@openshift-ci-robot
Copy link

openshift-ci-robot commented Mar 23, 2026

@sadasu: This pull request references CORS-4029 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.

@sadasu
Copy link
Contributor Author

sadasu commented Mar 24, 2026

@JoelSpeed, I would like some guidance on the integration test failures https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_api/2774/pull-ci-openshift-api-master-integration/2036210924280352768

There is another featuregate AzureDualStackInstall that is currently available in techpreview / devpreview. So the tests in https://github.com/openshift/api/blob/master/config/v1/tests/infrastructures.config.openshift.io/AzureClusterHostedDNSInstall.yaml#L63 have to account for the field ipFamily introduced by that featuregate when run for TP, DP and CustomNoUpgrade.
For running the same tests for OKD and Default CRDs, the integration tests report the errors seen in the output because ipFamily is not available in those versions of the CRD yet.
Seems like state of one featuregate is stomping on the integration test results for the other.
Any ideas on how to proceed?
/cc @patrickdillon

@openshift-ci openshift-ci bot requested a review from patrickdillon March 24, 2026 00:44
@patrickdillon
Copy link
Contributor

patrickdillon commented Mar 24, 2026

@JoelSpeed, I would like some guidance on the integration test failures https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_api/2774/pull-ci-openshift-api-master-integration/2036210924280352768

There is another featuregate AzureDualStackInstall that is currently available in techpreview / devpreview. So the tests in https://github.com/openshift/api/blob/master/config/v1/tests/infrastructures.config.openshift.io/AzureClusterHostedDNSInstall.yaml#L63 have to account for the field ipFamily introduced by that featuregate when run for TP, DP and CustomNoUpgrade. For running the same tests for OKD and Default CRDs, the integration tests report the errors seen in the output because ipFamily is not available in those versions of the CRD yet. Seems like state of one featuregate is stomping on the integration test results for the other. Any ideas on how to proceed? /cc @patrickdillon

This is passing tests locally for me: patrickdillon@99e7d68
Claude helped me understand that the syntax

 crdName: infrastructures.config.openshift.io
 featureGates:
 - AzureClusterHostedDNSInstall
 - -AzureDualStackInstall

means something like "run this test where AzureClusterHostedDNSInstall feature gate is enabled and AzureDualStackInstall is not enabled (which is what we want). I didn't realize that was how it worked.

@sadasu
Copy link
Contributor Author

sadasu commented Mar 24, 2026

@JoelSpeed, I would like some guidance on the integration test failures https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_api/2774/pull-ci-openshift-api-master-integration/2036210924280352768
There is another featuregate AzureDualStackInstall that is currently available in techpreview / devpreview. So the tests in https://github.com/openshift/api/blob/master/config/v1/tests/infrastructures.config.openshift.io/AzureClusterHostedDNSInstall.yaml#L63 have to account for the field ipFamily introduced by that featuregate when run for TP, DP and CustomNoUpgrade. For running the same tests for OKD and Default CRDs, the integration tests report the errors seen in the output because ipFamily is not available in those versions of the CRD yet. Seems like state of one featuregate is stomping on the integration test results for the other. Any ideas on how to proceed? /cc @patrickdillon

This is passing tests locally for me: patrickdillon@99e7d68 Claude helped me understand that the syntax

 crdName: infrastructures.config.openshift.io
 featureGates:
 - AzureClusterHostedDNSInstall
 - -AzureDualStackInstall

means something like "run this test where AzureClusterHostedDNSInstall feature gate is enabled and AzureDualStackInstall is not enabled (which is what we want). I didn't realize that was how it worked.

Wasn't aware of this syntax to selectively disable featuregates. Thanks!

Also make it part of OKD.
@sadasu sadasu force-pushed the azureClusterHostedDNS-default branch from f1fa34a to c67875d Compare March 24, 2026 04:17
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 24, 2026

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

Test name Commit Details Required Rerun command
ci/prow/verify-feature-promotion c67875d link true /test verify-feature-promotion

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. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants