revive the liveness/readiness probe config#3335
Conversation
The real problem of 'crash loop' of mixer is failure of initialization; the mixer CRD store will wait for up to 30 seconds for init. (see https://github.com/istio/istio/blob/master/mixer/pkg/config/crd/store.go#L52) Considering this, this PR sets the initial delay for liveness to be 60 seconds for safety.
|
/assign @myidpt |
|
/test istio-pilot-e2e |
|
this sounds risky for 0.6 given the recent history of those checks ? |
|
/test istio-pilot-e2e |
|
/retest |
1 similar comment
|
/retest |
|
Thanks a lot for the work! |
|
probably istio-auth-with-control-plane-health-check.yaml is enough but yes, pending helm settings adding this to the default has proven risky in the past |
|
I think we can have both non-auth and auth config files. This fits the needs for different users. For example, Oath don't have auth enabled :) |
|
Okay, separated the liveness / readiness for mixer into a different file. PTAL. |
|
/test e2e-bookInfo |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: myidpt Assign the PR to them by writing The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these OWNERS Files:You can indicate your approval by writing |
The real problem of 'crash loop' of mixer is failure of initialization;
the mixer CRD store will wait for up to 30 seconds for init.
(see
https://github.com/istio/istio/blob/master/mixer/pkg/config/crd/store.go#L52)
Considering this, this PR sets the initial delay for liveness
to be 60 seconds for safety.