idrennanvmware

High interest in this. We have a windows fleet that has no ability to run a service in the mesh. Given we will be in this hybrid environment for a...

The above describes a very similar set of criteria to our platform too

We're seeing a pretty healthy amount of these messages as well across our clusters. Keeping our eyes on this. Given the above, option 2 is definitely our preference. Not sure...

Here's an example we saw on a production server this morning. All allocations on the same client

@tgross - here's the alloc from one of the services all packed on the same node ``` ID = ec019321-2797-2398-93ed-8a46e80e5a0f Eval ID = 81baa965-3ddc-c506-2b46-bd7a7c4cb0db Name = device-log-job.device-log-api-group[1] Node ID =...

@tgross - apologies here, too - been buried in a million things :) To answer your question, yes there could be a large number of excluded nodes given we have...

@evandam given you're running in mesh, is there a reason you aren't using hard coded ports? Since it's all internal there's no chance of conflict. Here's an example of how...

+1 for this request. We use structured logging whenever possible across our log aggregators and most products already support this (json format or flat).