Fixing route-operator not processing tunnelendpoints.net.liqo.io resources on restart #266
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR fixes the route-operator not processing
tunnelendpoints.net.liqo.io
resources when restarted.When the operator proccessed a
tunnelendpoints.net.liqo.io
instance it added a label to the resource to say that it has been processed. Each time the reconcile function of the operator is called upon an update event of the resource it checks if the label is present if yes it would do nothing. This label prevents also the operator to reconcile the state of a resource according to theresyncPeriod
. TheresyncPeriod
is really important to check that the routes and iptables rules have not been modified by an external actor.This check was introduced to sync the various operators that handled a
tunnelendpoints.net.liqo.io
resource.Fixes #264
How Has This Been Tested?
Restarting the route-operator pod and verifying that: