Right now, frameworks can advertise their capabilities to the master via the FrameworkInfo they use for registration/re-registration. This allows masters to provide backward compatibility for old frameworks that don't support new functionality.
To allow new frameworks to support backward compatibility with old masters, the inverse concept would be useful: masters would tell frameworks which capabilities are supported by the master, which the frameworks could then use to decide whether to use features only supported by more recent versions of the master.
For now, frameworks can workaround this by looking at the master's version number, but that seems a bit fragile and hacky.
- blocks
-
MESOS-7683 Introduce a master capability for reservation refinement.
-
- Resolved
-
- relates to
-
MESOS-7681 Add safeguard for new agents with new features + old master
-
- Open
-
-
-
- Resolved
-