[
https://issues.apache.org/jira/browse/MESOS-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15054716#comment-15054716
]
James DeFelice commented on MESOS-4120:
---------------------------------------
If there's no support for updates via sidecar then a significant consequence
(of forcing service/endpoint metadata through a task's DiscoveryInfo) is that
every kubelet in the cluster will have to watch all changes to all endpoints in
the cluster. This will not scale.
OTOH if a sidecar component can make updates to DiscoveryInfo then we can run a
single instance of the sidecar (or sharded instances) and that should scale
much, much nicer.
In k8s there's no way to attach annotations to individual endpoint addresses,
instead we'd need to somehow annotate the entire Endpoints struct with
key/values such that taskId is reasonably discoverable by this sidecar. This is
ugly and forces us to maintain the forked version of the custom k8s
endpoint-controller that we maintain (which we ultimately want to drop support
for).
Overall I'd prefer to advertise service discovery metadata through a different
channel than a task's DiscoveryInfo.
> Make DiscoveryInfo dynamically updatable
> ----------------------------------------
>
> Key: MESOS-4120
> URL: https://issues.apache.org/jira/browse/MESOS-4120
> Project: Mesos
> Issue Type: Improvement
> Affects Versions: 0.25.0, 0.26.0
> Reporter: Sargun Dhillon
> Priority: Critical
> Labels: mesosphere
>
> K8s tasks can dynamically update what they expose to make discoverable by the
> cluster. Unfortunately, all DiscoveryInfo the cluster is immutable, at the
> time of task start.
> We would like to enable DiscoveryInfo to be dynamically updatable, so that
> executors can change what they're advertising based on their internal state,
> versus requiring DiscoveryInfo to be known prior to starting the tasks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
