Skip to content

Commit

Permalink
Updates FAQ for progressing sts scenario (argoproj#2402)
Browse files Browse the repository at this point in the history
  • Loading branch information
alexec authored Oct 2, 2019
1 parent 039d81a commit 399a022
Showing 1 changed file with 1 addition and 0 deletions.
1 change: 1 addition & 0 deletions docs/faq.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,6 +25,7 @@ to return `Progressing` state instead of `Healthy`.
* `StatefulSet` is considered healthy if value of `status.updatedReplicas` field matches to `spec.replicas` field. Due to Kubernetes bug
[kubernetes/kubernetes#68573](https://github.com/kubernetes/kubernetes/issues/68573) the `status.updatedReplicas` is not populated. So unless you run Kubernetes version which
include the fix [kubernetes/kubernetes#67570](https://github.com/kubernetes/kubernetes/pull/67570) `StatefulSet` might stay in `Progressing` state.
* Your `StatefulSet` or `DaemonSet` is using `OnDelete` instead of `RollingUpdate` strategy. See [#1881](https://github.com/argoproj/argo-cd/issues/1881).

As workaround Argo CD allows providing [health check](operator-manual/health.md) customization which overrides default behavior.

Expand Down

0 comments on commit 399a022

Please sign in to comment.