Skip to content

Conversation

@sadasu
Copy link

@sadasu sadasu commented Sep 23, 2025

  1. Added AWS and Azure as platforms that support DualStack on Day-0
  2. Added AWS, Azure and OpenStack as platforms that do not support conversion to DualStack on Day-2.
  3. Updated tests to reflect the newly supported platforms and when they support DualStack.
  4. Currently DualStack for AWS and Azure are behind featuregates. Updated to check that these featuregates are enabled before DualStack support is extended to these platforms.

@sadasu sadasu changed the title Allow AWS and Azure as platforms that support dual-stack on Day-0 CORS-4180: Allow AWS and Azure as platforms that support dual-stack on Day-0 Sep 23, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 23, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Sep 23, 2025

@sadasu: This pull request references CORS-4180 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.21.0" version, but no target version was set.

In response to this:

  1. Added AWS and Azure as platforms that support DualStack on Day-0
  2. Added AWS, Azure and OpenStack as platforms that do not support conversion to DualStack on Day-2.
  3. Updated tests to reflect the newly supported platforms and when they support DualStack.

Developed with Cursor.

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
Contributor

openshift-ci-robot commented Sep 23, 2025

@sadasu: This pull request references CORS-4180 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.21.0" version, but no target version was set.

In response to this:

  1. Added AWS and Azure as platforms that support DualStack on Day-0
  2. Added AWS, Azure and OpenStack as platforms that do not support conversion to DualStack on Day-2.
  3. Updated tests to reflect the newly supported platforms and when they support DualStack.

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
Author

sadasu commented Sep 23, 2025

/retest-required

@patrickdillon
Copy link

This looks good to me. AWS tests are failing to find a lease... i think we're hitting ci infra problems.

@sadasu
Copy link
Author

sadasu commented Sep 24, 2025

/retest-required

@sadasu sadasu force-pushed the update-for-dualstack branch from 4696a48 to 621b294 Compare October 3, 2025 14:02
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Oct 3, 2025

@sadasu: This pull request references CORS-4180 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.21.0" version, but no target version was set.

In response to this:

  1. Added AWS and Azure as platforms that support DualStack on Day-0
  2. Added AWS, Azure and OpenStack as platforms that do not support conversion to DualStack on Day-2.
  3. Updated tests to reflect the newly supported platforms and when they support DualStack.
  4. Currently DualStack for AWS and Azure are behind featuregates. Updated to check that these featuregates are enabled before DualStack support is extended to these platforms.

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 sadasu force-pushed the update-for-dualstack branch from 621b294 to 9fbf4db Compare October 3, 2025 14:12
@sadasu
Copy link
Author

sadasu commented Oct 8, 2025

/jira-refresh

@sadasu
Copy link
Author

sadasu commented Oct 14, 2025

/retest-required

@jhixson74
Copy link
Member

/cc

@openshift-ci openshift-ci bot requested a review from jhixson74 October 15, 2025 20:38
@jhixson74
Copy link
Member

/retest-required

1 similar comment
@jhixson74
Copy link
Member

/retest-required

@tthvo
Copy link
Member

tthvo commented Oct 21, 2025

/retest

@jhixson74
Copy link
Member

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 23, 2025
return nil, progressing, err
}

updateDualStackPlatforms(featureGates)
Copy link
Member

Choose a reason for hiding this comment

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

Should we move the function to earlier in the func Render so that any rendering, if any later on, can always pick up the most up-to-date list of supported dualstack platform?

Comment on lines +41 to +45
var conversionToDualStackPlatforms = sets.NewString(
string(configv1.BareMetalPlatformType),
string(configv1.NonePlatformType),
string(configv1.VSpherePlatformType),
)
Copy link
Member

Choose a reason for hiding this comment

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

question: Previously, only OpenStack is rejected. Just wondering if we confirmed this is OK?

Copy link
Member

Choose a reason for hiding this comment

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

The code comments seem to indicate so, but I have 0 clue 😞

Copy link
Author

Choose a reason for hiding this comment

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

This is the "allow" list so it contains the list of platforms that allow conversion to DualStack on Day-2. The code earlier was looking at OpenStack platform as the reject list. It could be implemented either ways.

Copy link
Member

Choose a reason for hiding this comment

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

Oh sounds good! I was just unsure if there are any other platforms that allow dualstack, which is not yet accounted for here...

@sadasu sadasu force-pushed the update-for-dualstack branch from 9fbf4db to 43ceb4d Compare October 23, 2025 20:29
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Oct 23, 2025
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Oct 23, 2025
@tthvo
Copy link
Member

tthvo commented Oct 23, 2025

Maybe another rebase?

Bringing in the feature gates added for AWS and Azure DualStack
support.
This is required to bring in the lastest featuregates
1. Added AWS and Azure as platforms that support DualStack on Day-0
2. Created another set of platforms that support DualStack on Day-2
3. Updated Render logic to take enabled featuregates into consideration
to determine supported DualStack platforms
4. Updated tests to reflect the newly supported platforms and when
they support DualStack.
@sadasu sadasu force-pushed the update-for-dualstack branch from 43ceb4d to d95a14b Compare October 23, 2025 21:08
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Oct 23, 2025
Copy link
Member

@tthvo tthvo left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 23, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 24, 2025

@sadasu: The following tests 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/4.20-upgrade-from-stable-4.19-e2e-azure-ovn-upgrade 9fbf4db link false /test 4.20-upgrade-from-stable-4.19-e2e-azure-ovn-upgrade
ci/prow/4.20-upgrade-from-stable-4.19-e2e-aws-ovn-upgrade 9fbf4db link false /test 4.20-upgrade-from-stable-4.19-e2e-aws-ovn-upgrade
ci/prow/e2e-aws-hypershift-ovn-kubevirt 9fbf4db link false /test e2e-aws-hypershift-ovn-kubevirt
ci/prow/security d95a14b link false /test security
ci/prow/4.21-upgrade-from-stable-4.20-e2e-gcp-ovn-upgrade d95a14b link false /test 4.21-upgrade-from-stable-4.20-e2e-gcp-ovn-upgrade
ci/prow/e2e-metal-ipi-ovn-dualstack-bgp d95a14b link true /test e2e-metal-ipi-ovn-dualstack-bgp
ci/prow/e2e-gcp-ovn d95a14b link true /test e2e-gcp-ovn
ci/prow/e2e-metal-ipi-ovn-dualstack-bgp-local-gw d95a14b link true /test e2e-metal-ipi-ovn-dualstack-bgp-local-gw
ci/prow/4.21-upgrade-from-stable-4.20-e2e-aws-ovn-upgrade d95a14b link false /test 4.21-upgrade-from-stable-4.20-e2e-aws-ovn-upgrade
ci/prow/okd-scos-e2e-aws-ovn d95a14b link false /test okd-scos-e2e-aws-ovn
ci/prow/4.21-upgrade-from-stable-4.20-e2e-azure-ovn-upgrade d95a14b link false /test 4.21-upgrade-from-stable-4.20-e2e-azure-ovn-upgrade

Full PR test history. Your PR dashboard.

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.

Comment on lines +56 to +58
// Update the list of supported DualStack platforms based on enabled feature gates.
updateDualStackPlatforms(featureGates)

Copy link
Member

Choose a reason for hiding this comment

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

@sadasu this is added in the Render function is, I believe, is called when rendering manifests for bootstrap.

This means when the cluster-network-operator is running in the cluster, such function is not called, right? And the list is not modified at all?

Copy link
Member

Choose a reason for hiding this comment

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

/lgtm cancel

Pending question above 👀

Copy link
Member

Choose a reason for hiding this comment

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

I think we should have the function isSupportedDualStackPlatform keeps the list of supported platforms (i.e. both static and feature-gated items), instead of having a global variable and modifying them at runtime.

WDYT?

Copy link
Member

Choose a reason for hiding this comment

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

Whoops, nvmind... It is also called during reconcilation 😓 so its fine. Please ignore it :D

@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Oct 24, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 24, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

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
Contributor

@kyrtapz kyrtapz left a comment

Choose a reason for hiding this comment

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

Thanks @sadasu!
There are a few changes we need to make and I think we should be good.

// of platforms that support DualStack on Day-0. Currently the 2 platforms added here
// donot support conversion to DualStack on Day-2. When that happens, we will need to
// update `conversionToDualStackPlatforms` too.
func updateDualStackPlatforms(featureGates featuregates.FeatureGate) {
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't like the fact that we are modifying the global variable through this function. My proposal is to set the supported platforms as part of the bootstrap.InfraStatus and read it from there. Same applies to conversionToDualStackPlatforms.

Copy link
Author

Choose a reason for hiding this comment

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

@kyrtapz happy to make that change but I am not sure how future proof that is. As long as the dualStackPlatforms is in place, we run the risk of someone using that global instead of the InfraStatus.

Copy link
Contributor

Choose a reason for hiding this comment

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

With the change I proposed we should get rid of the global dualStackPlatforms variable.

objs := []*uns.Unstructured{}

// Update the list of supported DualStack platforms based on enabled feature gates.
updateDualStackPlatforms(featureGates)
Copy link
Contributor

@kyrtapz kyrtapz Oct 28, 2025

Choose a reason for hiding this comment

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

Calling it here would mean adding elements to dualStackPlatforms every time Render is called, we cannot do that.

Edit: this isn't a problem since we use a set. I still don't like the fact that it tries to modify the global variable so often.

return errors.Errorf("%s is not one of the supported platforms for dual stack (%s)", infraRes.PlatformType,
strings.Join(dualStackPlatforms.List(), ", "))
} else if string(configv1.OpenStackPlatformType) == string(infraRes.PlatformType) {
} else if !isConversionSupportedDualStackPlatform(infraRes.PlatformType) {
Copy link
Contributor

Choose a reason for hiding this comment

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

I know you didn't introduce this but we can simplify the code and ditch the else if since the if returns.
something like this:

if !isSupportedDualStackPlatform(infraRes.PlatformType) {
    return ...
}
if !isConversionSupportedDualStackPlatform(infraRes.PlatformType) {
    return ...
}

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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants