Operator reports Workspace as "not found" even though it exists

[EmmanuelOgiji]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

terraform-k8s & Kubernetes Version

terraform-k8s:1.1.0 and Kubernetes version:1.22

Affected Resource(s)

syncWorkspace operator

Debug Output

Expected Behavior

The operator should be able to create the workspace, find it and send runs to it as it does normally.

Actual Behavior

SyncOperator pod reports a workspace is "not found" even after creating the said workspace. Thus, the workflow becomes stuck even if you delete the operator pod or delete the workspace from the UI for it to retry. This occurred after a workspace of the same name was deleted. In the absence of a solution, it'll be good to know how to do a hard refresh of the operator as it seems like this problem comes from the operator pods being "stateful" even though said state is wrong.

Steps to Reproduce

• Setup operator
• Create a workspace referencing a module
• Delete said workspace
• Create a new workspace with the same name as the previous one.

[EmmanuelOgiji]

Issue was that the name of the one of the run Triggers in the manifest did not exist