[GitHub] [apisix-dashboard] gxthrj commented on issue #819: request help: Is it normal that upstreams used by a router can be deleted directly?

[GitBox <gi...@apache.org>]

gxthrj commented on issue #819:
URL: https://github.com/apache/apisix-dashboard/issues/819#issuecomment-729333405


   Yes, I think upstream can be deleted directly, and 503 can be used when the route cannot find upstream.
   In other systems, such as k8s, this way is more respected. 
   The `propagationPolicy` is for GC, the scenario is to delete the `deployment`, which needs to be cascaded to delete replicasets and pods. You should not refer to this feature, because deployment, replicaset, and pod are inherited, they are different from upstream and route binding.
   In APISIX, the relationship between the `route` and `upstream` can refer to the `service` and `pod` in k8s. They are the selection relationship of the selector label. We can indeed delete all pods, but the `service` is not affected.


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org