-
Notifications
You must be signed in to change notification settings - Fork 9
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
Re-queue validation intermittently #36
Labels
Comments
19 tasks
20 tasks
maksymvavilov
added a commit
that referenced
this issue
Mar 27, 2024
maksymvavilov
added a commit
that referenced
this issue
Apr 3, 2024
maksymvavilov
added a commit
that referenced
this issue
Apr 3, 2024
maksymvavilov
added a commit
that referenced
this issue
Apr 3, 2024
maksymvavilov
added a commit
that referenced
this issue
Apr 4, 2024
maksymvavilov
added a commit
that referenced
this issue
Apr 4, 2024
maksymvavilov
added a commit
that referenced
this issue
Apr 4, 2024
maksymvavilov
added a commit
that referenced
this issue
Apr 4, 2024
maksymvavilov
added a commit
that referenced
this issue
Apr 4, 2024
maksymvavilov
added a commit
that referenced
this issue
Apr 4, 2024
maksymvavilov
added a commit
that referenced
this issue
Apr 4, 2024
maksymvavilov
added a commit
that referenced
this issue
Apr 11, 2024
maksymvavilov
added a commit
that referenced
this issue
Apr 11, 2024
maksymvavilov
added a commit
that referenced
this issue
Apr 11, 2024
github-merge-queue bot
pushed a commit
that referenced
this issue
Apr 11, 2024
GH-36 dns record lifecycle
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To ensure consistency across all of our clusters, we will need to occasionally queue a verification check to ensure the zone looks as expected for the local cluster.
To do this, when a verification reconcile finishes successfully (thereby setting the count of failed verifications in the status to 0), it should be requeued for 15 minutes later to re-verify and update the DNS Record status if required.
Update status with the next queued time and the time it was queued and valid length.
Requeue time should have a sane default (e.g. 15 minutes) and be possible to override as a flag to the runtime.
When observedGeneration == generation and the time it was queued is younger than valid length old - do not go to DNS Provider API actions, only verify metadata, e.g. finalizers.
The text was updated successfully, but these errors were encountered: