Skip to content

Conversation

@cadenmarchese
Copy link

According to linked access checks in Azure, if the user has configured a nat gateway on their subnet, the network resource provider will also check for Microsoft.Network/natGateways/join/action when FSO attempts to execute a Microsoft.Network/virtualNetworks/subnets/write operation. Since the FSO credentialsrequest requires Microsoft.Network/virtualNetworks/subnets/write, and many users also bring a nat gateway, Microsoft.Network/natGateways/join/action is also required.

@openshift-ci openshift-ci bot requested review from jsafrane and tsmetana March 7, 2025 17:26
@cadenmarchese
Copy link
Author

/retest-required

@jsafrane
Copy link
Contributor

@cadenmarchese can you please post a PR upstream (here)? We don't want to diverge from upstream permissions, as it would be just us to maintain them.

@cadenmarchese
Copy link
Author

@jsafrane thanks, I went ahead and opened a PR there: kubernetes-sigs/azurefile-csi-driver#2495

@jsafrane
Copy link
Contributor

Now that the upstream PR is merged, I can see there were some more additions. Do we need them in OCP?

@cadenmarchese
Copy link
Author

@jsafrane that depends - does OCP support configuring those additional resources (serviceEndpointPolicies, networkIntentPolicies, ipamPools) on the subnet?

@cadenmarchese cadenmarchese changed the title Add required Microsoft.Network/natGateways/join/action permission OCPBUGS-55182: Add required Microsoft.Network/natGateways/join/action permission Apr 21, 2025
@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Apr 21, 2025
@openshift-ci-robot
Copy link
Contributor

@cadenmarchese: This pull request references Jira Issue OCPBUGS-55182, which is invalid:

  • expected the bug to target the "4.19.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

According to linked access checks in Azure, if the user has configured a nat gateway on their subnet, the network resource provider will also check for Microsoft.Network/natGateways/join/action when FSO attempts to execute a Microsoft.Network/virtualNetworks/subnets/write operation. Since the FSO credentialsrequest requires Microsoft.Network/virtualNetworks/subnets/write, and many users also bring a nat gateway, Microsoft.Network/natGateways/join/action is also 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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 21, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: cadenmarchese
Once this PR has been reviewed and has the lgtm label, please assign tsmetana 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

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 21, 2025

@cadenmarchese: 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/okd-scos-e2e-aws-ovn 9f2f681 link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-gcp-manual-oidc 9f2f681 link false /test e2e-gcp-manual-oidc
ci/prow/e2e-aws-csi 9f2f681 link true /test e2e-aws-csi

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.

@RomanBednar
Copy link
Contributor

@cadenmarchese We don't document all options for every driver as there's too many, on the other hand we do support them to some extent.

I've just noticed this PR but already synced the permissions in scope of #576 - can we close this?

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Apr 23, 2025
@openshift-merge-robot
Copy link
Contributor

PR needs rebase.

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.

@cadenmarchese
Copy link
Author

Closing as this was addressed in #576 already. Thanks @RomanBednar

@openshift-ci-robot
Copy link
Contributor

@cadenmarchese: This pull request references Jira Issue OCPBUGS-55182. The bug has been updated to no longer refer to the pull request using the external bug tracker. All external bug links have been closed. The bug has been moved to the NEW state.

Details

In response to this:

According to linked access checks in Azure, if the user has configured a nat gateway on their subnet, the network resource provider will also check for Microsoft.Network/natGateways/join/action when FSO attempts to execute a Microsoft.Network/virtualNetworks/subnets/write operation. Since the FSO credentialsrequest requires Microsoft.Network/virtualNetworks/subnets/write, and many users also bring a nat gateway, Microsoft.Network/natGateways/join/action is also 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 openshift-eng/jira-lifecycle-plugin repository.

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

Labels

jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants