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

Improve controller readiness probe #29

Closed
polskikiel opened this issue Sep 10, 2019 · 0 comments
Closed

Improve controller readiness probe #29

polskikiel opened this issue Sep 10, 2019 · 0 comments
Assignees
Labels
area/service-management Issues or PRs related to service management kind/feature Categorizes issue or PR as related to a new feature.

Comments

@polskikiel
Copy link
Contributor

Description

The helm-controller readiness probe is implemented in the dummy way to just return 200OK on every call.
We should return 200OK only when the controller is able to work.

We need to find the best way to implement the checking of the controller status.

Ideas:

@polskikiel polskikiel added kind/feature Categorizes issue or PR as related to a new feature. area/service-management Issues or PRs related to service management labels Sep 10, 2019
@PK85 PK85 added this to the Sprint_Gopher_26 milestone Sep 16, 2019
@jasiu001 jasiu001 self-assigned this Sep 23, 2019
@PK85 PK85 closed this as completed Sep 30, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/service-management Issues or PRs related to service management kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

3 participants