Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[K8s Operator] Wait for available replicas before starting service watcher #521

Closed
CarlosLanderas opened this issue May 5, 2020 · 0 comments
Closed

[K8s Operator] Wait for available replicas before starting service watcher #521

CarlosLanderas opened this issue May 5, 2020 · 0 comments
Assignees
@CarlosLanderas
Labels
enhancement New feature or request in-progress

Comments

@CarlosLanderas
Copy link
Contributor

CarlosLanderas commented May 5, 2020 •
edited
Loading

What would you like to be added:

Right now, the HealthChecks Kubernetes operator starts the service watcher, and sometimes the UI is not ready so service push notifications fail.

The k8s operator should wait for the UI replica to be ready before starting the service watcher so discovered labeled service can be properly notified.
@CarlosLanderas CarlosLanderas self-assigned this May 5, 2020
@CarlosLanderas CarlosLanderas added enhancement New feature or request in-progress labels May 5, 2020
@CarlosLanderas CarlosLanderas changed the title [K8s Operator] Discover healthchecks services in deploy provisioning [K8s Operator] Wait for available replicas before starting service watcher May 5, 2020
@CarlosLanderas CarlosLanderas mentioned this issue May 5, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@CarlosLanderas CarlosLanderas

Labels
enhancement New feature or request in-progress
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@CarlosLanderas