I apologize if I misunderstood the question. I thought about something
like this.
Thanks! I'd prefer a text explanation as I still need to interpret the sketch. As far as I read it, something should be blocking on the health state of another container.
So it's not possible for one container to know the health state of another container. That knowledge must either be implemented in the application logic inside the container (e.g., ping a server) or be used outside the containers, for instance, by moving the containers into systemd units which will only mark the unit as ready when the health check fired.
вт, 21 нояб. 2023 г. в 12:49, Valentin Rothberg <vrothberg@redhat.com>:
>
> On Tue, Nov 21, 2023 at 10:12 AM Александр Илюшкин <ailjushkin@gmail.com> wrote:
>>
>> For example, you can define a custom /health API for this.
>>
>> In this API you can call and process health results from another hosts you are integrating with.
>
>
> Can you describe the use case? I don't yet fully understand what you want to do. I am a bit confused as you first mentioned "another container in the same pod" and now mention "another host".
>
> Kind regards,
> Valentin
>
>>
>> С уважением, А. И.
>>
>> вт, 21 нояб. 2023 г., 11:45 Михаил Иванов <ivans@isle.spb.ru>:
>>>
>>> Hi, is it possible to run health check on a container from another container in same pod?
>>>
>>> --
>>>
>>> Michael Ivanov
>>>
>>> _______________________________________________
>>> Podman mailing list -- podman@lists.podman.io
>>> To unsubscribe send an email to podman-leave@lists.podman.io
>>
>> _______________________________________________
>> Podman mailing list -- podman@lists.podman.io
>> To unsubscribe send an email to podman-leave@lists.podman.io
--
С уважением,
А.И.