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.

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

pkg: exit early if caches can't be synced #4149

Conversation

simonpasquier
Copy link
Contributor

If a cache sync times out, there's no need to continue since the
operator will exit eventually.

Signed-off-by: Simon Pasquier spasquie@redhat.com

Release Note Template (will be copied)


If a cache sync times out, there's no need to continue since the
operator will exit eventually.

Signed-off-by: Simon Pasquier <spasquie@redhat.com>
@simonpasquier simonpasquier requested a review from a team as a code owner July 6, 2021 09:31
Copy link
Member

@paulfantom paulfantom left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@dgrisonnet
Copy link
Contributor

I think it would make sense to also backport this change to 0.48 along with #4148.

@simonpasquier
Copy link
Contributor Author

@dgrisonnet since it will part of the upcoming v0.49.0, I'm not sure I would worry about a v0.48.2.

@paulfantom paulfantom merged commit 88f102f into prometheus-operator:master Jul 6, 2021
@dgrisonnet
Copy link
Contributor

I will need the fix made to the informers cache synchronization in 0.48, so I opened a backport PR after discussing with @paulfantom.
Since this change also improves the cache synchronization workflow, I think it would great to backport it alongside the addition of the timeout, but that's not required to fix the issue I have in 0.48.

@simonpasquier simonpasquier deleted the exit-early-on-sync-failures branch July 6, 2021 12:40
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.

None yet

3 participants