kezhenxu94 commented on pull request #83:
URL: 
https://github.com/apache/skywalking-kubernetes/pull/83#issuecomment-979660076


   > > > Once recent optimization are done, we should add document about how to 
set up load balancer in the main doc, and provide it(next release) as activated 
component in the showcase.
   > 
   > > > Please submit an issue to track for doc and showcase.
   > 
   > > 
   > 
   > > Just a reminder, satellite is not mandatory so we won't make all agent 
services connect to it in showcase, as we have 2 Java services (gateway and 
songs) we can make one of them send data to satellite and leave all others as 
is.
   > 
   > 
   > 
   > With time, more and more verification, could come from the product, if all 
are good, I would like to put it as recommended. In all these days perf testing 
and local balance testing, connection based load balance has very clear 
disadvantage, but most proxies are only supporting this way.
   > 
   > Users complained many times, now, we have the solution.
   > 
   > So, once we confirm Satellite is good, it should be some kind of 
mandatory(recommended as it is better to have). Does this make sense to you?
   
   We could recommend, but showcase repo serves as a demonstration that will be 
referenced by all users, we should have examples without Satellite, unless we 
say officially SkyWalking cannot work without Satellite, which is obviously not 
the case.
   
   I know Satellite can work with or without Kubernetes but for traditional 
deployments I don't believe users will deploy another Satellite process along 
with their application process, in this case they will ask for non-Satellite 
solution. That's why I want to keep agents without Satellite in showcase. 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to