-
Notifications
You must be signed in to change notification settings - Fork 0
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
Update README.md #4
Conversation
Removing the know flaws section because when the watcher starts it picks up all the changes from the beginning, that is, if something happens between the end of the bootstrap and the start of the watcher, it will pick it up. There is no flaw.
How do you define "the beginning"? Do you have a documentation reference? |
Yes, I have not only documentation, but I have tested it. This behavior comes from the Kubernetes API itself. Reference: https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#watch-configmap-v1-core You can run the code bellow on your machine and try It by yourself.
|
Does this work on the basis of the |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 24 hours if no further activity occurs. |
Removing the know flaws section because when the watcher starts it picks up all the changes from the beginning, that is, if something happens between the end of the bootstrap and the start of the watcher, it will pick it up. There is no flaw.