[MESOS-2998] Disable Persistent Volumes, Dynamic Reservations via master flags

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 0.23.0
• Component/s: master
• Labels: mesosphere persistence reservations volumes
• Assignee: Michael Park
• Reporter: Adam B
• Shepherd: Adam B
• Created: 07/Jul/15 04:13
• Updated: 26/Nov/18 12:32
• Resolved: 26/Nov/18 12:32

Description

As an operator, I might not want frameworks using the experimental dynamic reservations/persistent volumes APIs in 0.23, since there are no ACLs or operator endpoints for me to manage them. That means that a rogue framework could start reserving resources and creating volumes with all resources provided, and I would have no way to clean them up.
Is it possible to disable these features from the master (flags, etc.)?

Issue Links

• is superceded by: MESOS-3903 Add authorization for '/create-volume' and '/destroy-volume' HTTP endpoints
• is superceded by: MESOS-3065 Add framework authorization for persistent volume