Closed abel-von closed 3 years ago
@abel-von this timeout is not configurable
do we have plan to support it or is it supported in shimv2? @devimc
We should support this. Can you try to reproduce with shim-v2?
I think shimv2 support this because the kill request is sent to agent directly, I reproduced with our own shimv2(reimplemented with rust), this is supported.
This issue is being automatically closed as Kata Containers 1.x has now reached EOL (End of Life). This means it is no longer being maintained.
Important:
All users should switch to the latest Kata Containers 2.x release to ensure they are using a maintained release that contains the latest security fixes, performance improvements and new features.
This decision was discussed by the @kata-containers/architecture-committee and has been announced via the Kata Containers mailing list:
If you believe this issue still applies to Kata Containers 2.x, please open an issue against the Kata Containers 2.x repository, pointing to this one, providing details to allow us to migrate it.
hi, recently my customer reported an issue of our container service. the "terminationGracePeriodSeconds" definition does not work properly in kata container.
I checked the codes in kata, found that when we call kata-runtime kill with a SIGTERM, kata signal user process and then wait 10 seconds before sending SIGKILL, as this waiting will hold the sandbox lock, then the terminationGracePeriodSeconds has no use at all(even it is smaller than 10 seconds). the whole the graceful termination process is controlled by kata, with a 10 second timeout.
my question is, does kata support this graceful termination with configurable timeout?