Suppress Delete events as we don't take any action in the reconiliation loop when invoked after the gatlingv1alpha1.Gatling is actually deleted
Test
In local depevelopment, I actually deploy gatling CR and deleted like this following
# deploy the operator to local KIND cluster
make kind-deploy
# deploy sample Gatling CR
make kind-sample-deploy
# delete Gatling CR
kubectl delete gatling gatling-sample01
As a test result, I don't come up with any error even when gatlingv1alpha1.Gatling is actually deleted 🎉 🎉 🎉
Before this, I had an error like this when gatlingv1alpha1.Gatling is actually deleted.
Description
Fix https://github.com/st-tech/gatling-operator/issues/14
Suppress Delete events as we don't take any action in the reconiliation loop when invoked after the gatlingv1alpha1.Gatling is actually deleted
Test
In local depevelopment, I actually deploy gatling CR and deleted like this following
As a test result, I don't come up with any error even when gatlingv1alpha1.Gatling is actually deleted 🎉 🎉 🎉