-
Notifications
You must be signed in to change notification settings - Fork 475
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
doesn't see work on 1.12.6 EKS #63
Comments
The difference between version 0.0.27 and 0.0.26 is this log message, as you can see here #60. In 0.0.27 position of this log has been changed so log is only going to be be printed when reloader will restart a pod. This way, it will not print additional logs when there is no reload happening. |
In 0.0.27, reloader works the same way as in 0.0.26. Please check if your configmap is getting updated. After a change in configmap, you will see the pod restart and above mentioned log in reloader. |
Also, please make sure you are using the annotations correctly. If you think every thing is on point, and reloader still doesn't restart the pod, please share your annotation configuration. |
@roeera Closing this. If you face this issue again, please re-open again. |
version 0.0.27 - do nothing - means reloader comes up and that's it.
only shows :
time="2019-05-07T15:08:49Z" level=info msg="Starting Reloader"
time="2019-05-07T15:08:49Z" level=warning msg="KUBERNETES_NAMESPACE is unset, will detect changes in all namespaces."
time="2019-05-07T15:08:49Z" level=info msg="Starting Controller to watch resource type: secrets"
time="2019-05-07T15:08:49Z" level=info msg="Starting Controller to watch resource type: configMaps"
version 0.0.26 - writing to log such message "level=info msg="Changes detected in 'prometheus-alert-rules' of type 'CONFIGMAP' in namespace 'monitoring'"
but pod don't make restart.
any idea ?
The text was updated successfully, but these errors were encountered: