[MILESTONENOTIFIER] Milestone Pull Request Needs Attention
@brendandburns @jingxu97 @rohitjogvmw @vishh @kubernetes/sig-storage-misc
Action required: During code slush, pull requests in the milestone should be in progress.
If this pull request is not being actively worked on, please remove it from the milestone.
If it is being worked on, please add the status/in-progress label so it can be tracked with other in-flight pull requests.
Note: If this pull request is not resolved or labeled as priority/critical-urgent by Wed, Nov 22 it will be moved out of the v1.9 milestone.
sig/storage: Pull Request will be escalated to these SIGs if needed.priority/important-soon: Escalate to the pull request owners and SIG owner; move out of milestone after several unsuccessful escalation attempts.kind/feature: New functionality.—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.![]()
Automatic merge from submit-queue (batch tested with PRs 55112, 56029, 55740, 56095, 55845). If you want to cherry-pick this change to another branch, please follow the instructions here.
Merged #55845.
@andremarianiello done
This PR introduced shared datastore check even when no SPBM is enabled, IMHO this check should be made optional , because it requires excessive permissions, which reveal too much information about cluster were datastores are. I opened issue #67206 to discuss