Skip to content

Conversation

@rna-afk
Copy link
Contributor

@rna-afk rna-afk commented Jun 9, 2025

Adding support to install multiple NAT gateways per subnet.
The zone in which they will be installed is not customizable
due to needing an upstream PR to fix CAPZ.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jun 9, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jun 9, 2025

@rna-afk: This pull request references CORS-4064 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.20.0" version, but no target version was set.

In response to this:

Adding support to install multiple NAT gateways per subnet.
The zone in which they will be installed is not customizable
due to needing an upstream PR to fix CAPZ.

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 review from jhixson74 and rwsu June 9, 2025 18:42
@rna-afk rna-afk force-pushed the azure_multi_zonal_nat_gateway branch 4 times, most recently from ec3602c to e18526f Compare August 12, 2025 21:16
@rna-afk rna-afk force-pushed the azure_multi_zonal_nat_gateway branch 3 times, most recently from 43a70a3 to 72a16de Compare August 13, 2025 14:56
@rna-afk rna-afk changed the title CORS-4064: Add support for multi zonal NAT gateways CORS-4064, CORS-4187: Add support for multi zonal NAT gateways Aug 13, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Aug 13, 2025

@rna-afk: This pull request references CORS-4064 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.20.0" version, but no target version was set.

This pull request references CORS-4187 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.20.0" version, but no target version was set.

In response to this:

Adding support to install multiple NAT gateways per subnet.
The zone in which they will be installed is not customizable
due to needing an upstream PR to fix CAPZ.

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.

@rna-afk
Copy link
Contributor Author

rna-afk commented Aug 13, 2025

/jira refresh

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Aug 13, 2025

@rna-afk: This pull request references CORS-4064 which is a valid jira issue.

This pull request references CORS-4187 which is a valid jira issue.

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.

@rna-afk
Copy link
Contributor Author

rna-afk commented Aug 19, 2025

/retest

@rna-afk rna-afk changed the title CORS-4064, CORS-4187: Add support for multi zonal NAT gateways [WIP] CORS-4064, CORS-4187: Add support for multi zonal NAT gateways Aug 25, 2025
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 25, 2025
@rna-afk rna-afk force-pushed the azure_multi_zonal_nat_gateway branch from 72a16de to c9719c8 Compare September 29, 2025 16:22
@rna-afk rna-afk force-pushed the azure_multi_zonal_nat_gateway branch 3 times, most recently from 1028092 to 15bcb23 Compare September 30, 2025 17:10
@rna-afk rna-afk changed the title [WIP] CORS-4064, CORS-4187: Add support for multi zonal NAT gateways CORS-4064, CORS-4187: Add support for multi zonal NAT gateways Sep 30, 2025
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Sep 30, 2025
@rna-afk rna-afk force-pushed the azure_multi_zonal_nat_gateway branch 4 times, most recently from de423e3 to 14ee71a Compare November 20, 2025 19:05
@jhixson74
Copy link
Member

This is looking pretty good to me. What do you think @patrickdillon and @sadasu ?

@patrickdillon
Copy link
Contributor

/test verify-codegen
Sorry I broke this. Should be fixed now.

updating capz to latest commit that has the upstream PR enabling the
setting of zone in the nat gateways.
Adding support to install multiple NAT gateways per subnet in
the specific zones they need to be in.

Also, allowing the users to bring their own subnets.

(NAT gateways on BYO subnets are not supported by CAPZ, it just
creates a dummy NAT gateway and doesn't attach it to the subnet).
@patrickdillon
Copy link
Contributor

Sorry for the confusion: you do need to run go generate pkg/types/installconfig.go due to #10025 You may need to rebase prior

@rna-afk rna-afk force-pushed the azure_multi_zonal_nat_gateway branch from 14ee71a to 1ed30f0 Compare November 20, 2025 20:56
@jhixson74
Copy link
Member

/lgtm

I'll wait for feedback from @patrickdillon and @sadasu before /approve

@jhixson74
Copy link
Member

/assign

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 21, 2025
Distributing the compute subnets across NAT gateways. Depends
on nat gateway availability zones and vm zones.
@rna-afk rna-afk force-pushed the azure_multi_zonal_nat_gateway branch from 1ed30f0 to 13b9636 Compare November 21, 2025 02:01
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Nov 21, 2025
@jhixson74
Copy link
Member

/lgtm

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

Tested with latest change, all functions are currently working well, no other issue have been found.

/verified by jima

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Nov 21, 2025
@openshift-ci-robot
Copy link
Contributor

@jinyunma: This PR has been marked as verified by jima.

In response to this:

Tested with latest change, all functions are currently working well, no other issue have been found.

/verified by jima

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.

@jhixson74
Copy link
Member

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 21, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jhixson74

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

The pull request process is described 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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 21, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit e8da62a into openshift:main Nov 21, 2025
23 of 30 checks passed
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 21, 2025

@rna-afk: 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/e2e-azure-ovn-shared-vpc 13b9636 link false /test e2e-azure-ovn-shared-vpc
ci/prow/e2e-gcp-secureboot 13b9636 link false /test e2e-gcp-secureboot
ci/prow/e2e-azurestack 13b9636 link false /test e2e-azurestack
ci/prow/okd-scos-e2e-vsphere-ovn 13b9636 link false /test okd-scos-e2e-vsphere-ovn
ci/prow/e2e-gcp-xpn-dedicated-dns-project 13b9636 link false /test e2e-gcp-xpn-dedicated-dns-project

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.

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

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants