[manila-csi-plugin]: use new access rules GET method when possible

[kayrus]

Is this a BUG REPORT or FEATURE REQUEST?:

/kind feature

What happened:

Some OpenStack deployments can have middlewares that limit an amount of POST/PUT requests, which are categorized as write requests. One of the wrongly categorized request is a deprecated list access rules action.

What you expected to happen:

In order to prevent excessive requests rate limiting, CSI Manila plugin should support a newer Manila API call.

How to reproduce it:

n/a

Anything else we need to know?:

See also terraform-provider-openstack/terraform-provider-openstack#1582

Environment:

• openstack-cloud-controller-manager(or other related binary) version: n/a
• OpenStack version: n/a
• Others: n/a

cc @Carthaca

[mdbooth]

According to https://docs.openstack.org/manila/latest/contributor/api_microversion_history.html#id40 it looks like this microversion has been available since Rocky which, according to https://releases.openstack.org/ is the oldest release which isn't EOL.

That said, if we bumped the minimum microversion to Rocky it still might make folks like @lentzi90 unhappy. We should discuss which versions of OpenStack we want to support.

[kayrus]

@mdbooth see a PR that corresponds to terraform-provider-openstack/terraform-provider-openstack#1582. Before calling the share access list, we check API microversions.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[gouthampacha]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[gouthampacha]

/remove-lifecycle stale