vincent-pli

https://www.stackpath.com/edge-academy/edge-serverless/

The what is called "Edge Serverless" from STACKPATH company/organization do not solve the problems of Cloud-Edge, I meann, cloud-edgee
synchronization. it make assumption that cloud and edge is connected.

It focus on decrease the latency of Serverless invoke by:
- Add serverless function (customer's function) to many node(edge), expect it near the end user
- Make a smart DNS, will resolve the request to the address which near the end user

vincent-pli

kubernates zone: https://kubernetes.io/docs/setup/best-practices/multiple-zones/
kubernates zone can slow down the rate or, in some cases, completely stop the pod evictions.

Edge solution from Redhat
1. Three-node architeccture
Basically, the solution is a mutiple cluster solution, like k3s. to make Openshift smaller to make it could deploy on edge side
then leverage ACM to do the mangement.

2. Remote worker node
Same solution as Openyurt and KubeEdge

vincent-pli

The minimum requirement for a three-node steup:
    Base OS: Red Hat Enterprise Linux CoreOS 
    6 CPU
    24GB of RAM
    120GB of disk space


Standard Openshift:
The smallest OpenShift Container Platform clusters require the following hosts:
    1. One temporary bootstrap machine

vincent-pli

For Openyurt, they:
1. disable original nodelifecycleController(kube-controller-manager) by delete the secret.
2. Keep a copy of nodelifecycleController in Openyurt and modify the evicted policy by add:
https://github.com/alibaba/openyurt/blob/b6b02d77eb1f94964f1b700cf45b538ff0c16302/pkg/controller/nodelifecycle/node_lifecycle_controller.go#L1493

So the pod on edge node which mark as autonomy will never be evicted.

vincent-pli

https://openkruise.io/en-us/blog/blog2.html