mchtech commented on issue #610:
URL:
https://github.com/apache/apisix-ingress-controller/issues/610#issuecomment-1579153261
discuss a scenario:
If these four situations are met:
1. k8s control plane works well
2. apps are rolling update
3. "ingress controller" cannot sync ingress rules (or long sync delay)
3.1 ingress controller crashloop
3.2 or their nodes down
3.3 or they cannot connect to apiserver (node network problem)
3.4 or apisix etcd down (old architecture)
4. k8s/apisix administrators don't notice what happened
data plane (upstream) will reference obsoleted pod ip, which leads to:
1. app A pod IP is recycled by cni ipam, the redundancy of app A will reduce
2. or app A pod has been terminated, its IP re-assigned to app B pod: app A
will `HTTP 404` randomly
how about `dp and cp run in same pod` architecture? I think it can minimized
the risk (3.2, 3.3: only affect corresponding apisix dp, not all apisix dp).
--
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]
