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

Remove redundant reload on resource creation #187

Merged
merged 1 commit into from
Jan 11, 2021
Merged

Conversation

faizanahmad055
Copy link
Contributor

Signed-off-by: faizanahmad055 faizan.ahmad55@outlook.com

Should Fix #166

Signed-off-by: faizanahmad055 <faizan.ahmad55@outlook.com>
@faizanahmad055
Copy link
Contributor Author

It seems the add operation is causing the issue where sometimes the reloader reloads the pods when the reloader itself gets restarted as the queue is filled with all the k8s objects as new resources. And the add operation also is not required as reloader should update the resource in the event of any change and not in the event of any resource creation.

@ahmedwaleedmalik @kahootali Please review and comment.

@stakater-user
Copy link
Contributor

@faizanahmad055 Image is available for testing. docker pull stakater/reloader:SNAPSHOT-PR-187-1

Copy link
Contributor

@ahmedwaleedmalik ahmedwaleedmalik left a comment

Choose a reason for hiding this comment

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

LGTM

@ahmedwaleedmalik ahmedwaleedmalik merged commit 81c840e into master Jan 11, 2021
@ahmedwaleedmalik ahmedwaleedmalik deleted the fix-issue-166 branch January 11, 2021 04:36
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.

Multiple pods recreated when reloader pod was recreated, without any change to configmap/secrets
3 participants