You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a developer, if I pass the -f flag to kubectl command to delete a resource, I expect it to delete the resource. However, the Tyk Operator hangs infinitely during the reconciliation loop.
Recreate Steps
As a developer, if I (accidentally) delete an API/Policy in the Dashboard that was created through the Operator, and then I try to delete the
IE, when I try to modify the resource through Operator, it hangs forever because the Dashboard resource does not exist.
Expected Behavior
If I pass the --force command to the kubectl delete, the Operator should respect that.
sedkis
changed the title
Need to force-delete reconciliation infinite loops
Tyk Operator ignores "-f" during reconciliation infinite loops
May 25, 2022
MichaelTyk
changed the title
Tyk Operator ignores "-f" during reconciliation infinite loops
[TT-5489] Tyk Operator ignores "-f" during reconciliation infinite loops
May 25, 2022
Alternatively, maybe we could check if the API does not exist on Dashboard, then treat it as deleted?
caroltyk
changed the title
[TT-5489] Tyk Operator ignores "-f" during reconciliation infinite loops
[TT-5482] Tyk Operator ignores "-f" during reconciliation infinite loops
Nov 24, 2022
* ignore 404 when deleting an API, fixes#469
* Update CHANGELOG.md
* typo
* check for 404 error using tykclient.IsNotFound
* move change mention to Unreleased
* add bdd test scenario for deleting ApiDefinition not present in dashboard
* use a separate sample resource to test deletion of deleted apis
* fix linter
* fix createDashURL
* fix ::set-output warnings
* fix typos in feature files
* make bdd tests more reliable
* fix actionlint errors
* use gateway-api for deletion bdd test
* disable bdd strict
* change order of bdd example resources
* split apidefinition from context to fix test
* typos
* fix test
* (re)disable the failing test
As a developer, if I pass the
-f
flag to kubectl command to delete a resource, I expect it to delete the resource. However, the Tyk Operator hangs infinitely during the reconciliation loop.Recreate Steps
As a developer, if I (accidentally) delete an API/Policy in the Dashboard that was created through the Operator, and then I try to delete the
IE, when I try to modify the resource through Operator, it hangs forever because the Dashboard resource does not exist.
Expected Behavior
If I pass the
--force
command to thekubectl delete
, the Operator should respect that.Possible Solution
Here, we should skip the reconciliation process if the
-f / --force
command is passed in from kubectl in addition to the current check that looks for a finalizerhttps://github.com/TykTechnologies/tyk-operator/blob/master/controllers/apidefinition_controller.go#L482
The text was updated successfully, but these errors were encountered: