Created
December 16, 2020 01:47
-
-
Save vincent-pli/f047406bdcb59ad4c6a95a631634b3fc to your computer and use it in GitHub Desktop.
Edge for redhat
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 | |
but in very begging stage, the challenges Redhat though are: | |
a. Network separation | |
b. Power outage | |
c. Latency spikes or temporary reduction in throughput | |
For #a, redhat has no specific solution, the key point of the #a is avoid eviction. Redhat suggest to use Taint/toleration | |
For #b, redhat has no specific solution, the key point is recover, Redhat suggest to use static pod, Taint/toleration | |
In Openyurt, they use conception: "autonomy", they enhance the "kube-controller-manager" not evicted the pod on a "autonomy" node. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment