Skip to content

Fix a bug with syncing services #282

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.

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

Merged

Conversation

alexeyklyukin
Copy link
Contributor

Avoid showing "there is no service in the cluster" when syncing a
service for the cluster if the operator has been restarted after
the cluster had been created.

Avoid showing "there is no service in the cluster" when syncing a
service for the cluster if the operator has been restarted after
the cluster had been created.
@coveralls
Copy link

Coverage Status

Coverage increased (+0.002%) to 11.329% when pulling 37caa3f on assign_existing_service_definition_during_sync into 8f08bef on master.

@alexeyklyukin
Copy link
Contributor Author

👍

1 similar comment
@Jan-M
Copy link
Member

Jan-M commented Apr 27, 2018

👍

@alexeyklyukin alexeyklyukin merged commit 4a3ccad into master Apr 27, 2018
@alexeyklyukin alexeyklyukin deleted the assign_existing_service_definition_during_sync branch April 27, 2018 11:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants