Revolyssup commented on issue #2058: URL: https://github.com/apache/apisix-ingress-controller/issues/2058#issuecomment-1878222625
@jinjianming We have few ways around it. 1. Deleting all resources in that namespace: This might not be a good idea because the controller should not delete a resource. It should only be deleted by the user and controller should only react on it. 2. Giving a warning that the resources are still present: We can check for Apisix related CRs in that namespace and if there are still few CRs then we can put a warning log that XYZ resources are not deleted. And leave it to the user 3. Always watching for deletion, for add and update we keep the logic same but for deletion of APISIX CRs, we watch all the namespaces so that later on when user deleted the APISIX CR, the resources are deleted even when not being watched. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
