You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 1, 2022. It is now read-only.
Describe the feature
Currently there are no probes in flux deployment manifest file [https://github.com/weaveworks/flux/blob/master/deploy/flux-deployment.yaml]
That means flux reports as ready before initialization and if flux stops doing things for some reason no actions will be taken.
What would the new user story look like?
User starts up standalone Flux as described here [https://github.com/weaveworks/flux/blob/master/site/get-started.md#deploying-flux-to-the-cluster]
During warmup flux reports flux pod is not ready.
If flux stops operating then flux pod is restarted.
Expected behavior
Flux must report to kubernetes that it is ready only when it is able to accept and process connections.
If flux stops operating by some reason then it must be restarted.
The text was updated successfully, but these errors were encountered:
Describe the feature
Currently there are no probes in flux deployment manifest file [https://github.com/weaveworks/flux/blob/master/deploy/flux-deployment.yaml]
That means flux reports as ready before initialization and if flux stops doing things for some reason no actions will be taken.
What would the new user story look like?
Expected behavior
Flux must report to kubernetes that it is ready only when it is able to accept and process connections.
If flux stops operating by some reason then it must be restarted.
The text was updated successfully, but these errors were encountered: