@David Drápela I appreciate your patience on this. Thanks for sharing the details over email.
The Microsoft Azure Team has investigated the issue in which you may have experienced unexpected application restart on your Azure Container Apps.
Upon investigation, engineers determined that the restart is caused by os image version upgrade. During upgrade, Azure Container Apps will first reschedule customer (Your) applications to a new created node then stop the existing one. Upon deeper investigation, we found we stop the existing application before the new created one is up and ready.
We are continuously taking steps to improve the Azure Container Apps service and our processes to ensure such incidents do not occur in the future, and in this case it includes (but is not limited to):
Improve container apps schedule logic, increase the availability
Improve alerting and detection for platform os upgrade.
We apologize for any inconvenience.
Regards,
The Microsoft Azure Team
**
Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.