"resourceVersion now: 13748114" and processing old versions of CRD resources

[max-rocket-internet]

The problem is that often the controller that is watching a CRD starts processing old versions of the CRD resources.

This is potentially disastrous.

Example log output:

{"time":"2019-01-15 11:21:50,490", "level":"DEBUG", "resource_name":"-", "new_relic_app":"-", "message":"Error code 410"}
{"time":"2019-01-15 11:21:50,491", "level":"DEBUG", "resource_name":"-", "new_relic_app":"-", "message":"Updating resource version to 18726332 due to "too old" error"}
{"time":"2019-01-15 11:21:51,229", "level":"DEBUG", "resource_name":"-", "new_relic_app":"-", "message":"Error code 410"}
{"time":"2019-01-15 11:21:51,229", "level":"DEBUG", "resource_name":"-", "new_relic_app":"-", "message":"Updating resource version to 20220905 due to "too old" error"}
{"time":"2019-01-15 11:21:51,927", "level":"DEBUG", "resource_name":"-", "new_relic_app":"-", "message":"resourceVersion now: 20220906"}

I tried to use an a function to parse the 410 error correctly but it still doesn't work correctly.

I opened an issue here with the kubernetes-client/python project: kubernetes-client/python#693

@juliantaylor created a PR to fix it in the kubernetes-client/python-base project: kubernetes-client/python-base#109

Another issue: kubernetes-client/python#609

[max-rocket-internet]

Fixed in 1f10e6d