Sebastian Florek

Does kubectl get/describe for this pod shows some additional info, i.e. that this other pod (container in pod) is failing/crashing? The reason why I'm asking is that we want to...

> UI of this service, does not display 10.2.6.2 and 10.2.73.3 in the endpoints section That's true. We are displaying endpoints of a service but not endpoints of a pods...

This endpoint is additional kubernetes resource, so maybe we could show them as a related object and use some of that logic to match pods to a service better. ```...

> I like this idea. Is this something you can work on? :) Probably yes but it can take some time as I have some other open issues in core...

@djschny I'm not sure if I understand correctly. Currently on service detail page you can see list of pods targeting chosen service. They are matched using labels. I think that...

~Readiness~Liveness probe has to be defined in resource definition during creation. If it is defined then kubernetes is responsible for checking if application is healthy. In case this check fails...

Ahh... you are right. My mistake. So you are defining `readinessProbe` for your resources right? We could use that to differentiate between actively targeted pods and not.

Good that we got to conclusion here :) We will take a look at this. Should not be that hard to implement.

I like the general idea. I don't see any reason why we couldn't have that upstream. It is generic enough and templating variables like in grafana could be used by...

Unfortunately, I can't reproduce that. Tried on fresh `v1.21` and `v1.24` clusters and the scale feature works as expected. Is there anything special about your configuration that might cause this?