[
https://issues.apache.org/jira/browse/MESOS-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14031335#comment-14031335
]
Niklas Quarfot Nielsen commented on MESOS-1486:
-----------------------------------------------
We need it to prevent slaves to register malicious (or unintentional) masters.
As with the whitelist on masters, a master that hasn't been whitelisted can be
added while the slave is running (so if an unknown master comes up - the slave
will log that it doesn't know about it, and can be added later on). If
frameworks that want to, can implement their own whitelist if needed.
Does that make sense?
> Add whitelisting of masters in slaves.
> --------------------------------------
>
> Key: MESOS-1486
> URL: https://issues.apache.org/jira/browse/MESOS-1486
> Project: Mesos
> Issue Type: Improvement
> Components: slave
> Reporter: Niklas Quarfot Nielsen
> Assignee: Niklas Quarfot Nielsen
>
> Like masters can whitelist slaves (and only announce available resources from
> slaves whitelisted), slaves should be able to whitelist masters they are
> willing/allowed to connect to. I have a proof-of-concept ready which ties
> into the slave::detected() method and prevents non-whitelisted masters to
> register.
> If "*" is provided - whitelisting is not enforced (which would be the usual
> case).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
