> kubectl logs ... --previous ?
>
I have tried that, but it shows `Error from server (BadRequest): previous
terminated container "main" in pod "demo-1050-5fb5698d4f-8qtsw" not found`
BTW, I found `maximum-dead-containers-per-container` and
`maximum-dead-containers` to configure the policy,
kubectl logs ... --previous ?
On Wed, Jan 31, 2018 at 6:38 AM, Colstuwjx wrote:
>>
>>
>>>
>>> But, what if we want to trigger the detail exited reason for the exited
>>> containers? Is there any parameters configure that?
>>
>>
>> Have you checked the terminationGracePeriod?
On Wed, Jan 31, 2018 at 06:38:36AM -0800, Colstuwjx wrote:
> >
> >> But, what if we want to trigger the detail exited reason for the exited
> >> containers? Is there any parameters configure that?
> >
> > Have you checked the terminationGracePeriod? I think it will do just that.
>
> I'm afraid
>
>
>
>
>> But, what if we want to trigger the detail exited reason for the exited
>> containers? Is there any parameters configure that?
>>
>
> Have you checked the terminationGracePeriod? I think it will do just that.
>
I'm afraid not, I need to check the exited container, such as some
On Wednesday, January 31, 2018, Colstuwjx wrote:
> Hi team,
>
> As I known, kubernetes will kill the POD while the readiness probe failed
> over than `FailureThreshold` limit, and the unhealthy containers will be
> deleted by kubelet.
>
I think only the liveness probe will