Skip to content
This repository has been archived by the owner on Nov 1, 2022. It is now read-only.

Create probes for flux standalone deployment #2200

Closed
mpashka opened this issue Jun 27, 2019 · 0 comments · Fixed by #2355
Closed

Create probes for flux standalone deployment #2200

mpashka opened this issue Jun 27, 2019 · 0 comments · Fixed by #2355
Labels
blocked-needs-validation Issue is waiting to be validated before we can proceed enhancement

Comments

@mpashka
Copy link
Contributor

mpashka commented Jun 27, 2019

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?

  1. User starts up standalone Flux as described here [https://github.com/weaveworks/flux/blob/master/site/get-started.md#deploying-flux-to-the-cluster]
  2. During warmup flux reports flux pod is not ready.
  3. 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.

@mpashka mpashka added blocked-needs-validation Issue is waiting to be validated before we can proceed enhancement labels Jun 27, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
blocked-needs-validation Issue is waiting to be validated before we can proceed enhancement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant