PR4408 and networking changes for Clustering #4454
Merged
Conversation
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
- check kubernetes pod status and publish ENClusterAppStatus for multi-node cluster - subscribe the EdgeNodeClusterConfig and DeviceNetworkStatus for publishing the EdgeNodeClusterStatus for cluster-init.sh to use - implement cluster server status HTTP service for others to join the cluster - collect stats from kubernetes cluster for node/pod/vmi and publish clusterInfo - implement cluster leader election for cluster reporter - documented the functionalities of zedkube in pillar/doc/zedkube.md Signed-off-by: Naiming Shen <[email protected]>
- Add vendor files for Implement Cluster for zedkube related functions Signed-off-by: Naiming Shen <[email protected]>
NIM subscribes to EdgeNodeClusterStatus published by zedkube and passes this to DPCManager and further into DPCReconciler. Cluster IP address is assigned to the cluster interface statically (directly using netlink, not via dhcpcd). zedkube subscribes to DeviceNetworkStatus to determine if the cluster IP address is assigned and ready to use. Once assigned, it will update EdgeNodeClusterStatus with ClusterIPIsReady set to true, which the script cluster-init.sh is waiting for before it starts the procedure of node joining the cluster. Signed-off-by: Milan Lenco <[email protected]>
Ensure that packets destined for K3s services do not use the default route, but are instead routed through the cluster port. This guarantees that traffic handled by kube-proxy is properly SNATed to the cluster IP. That's the theory at least. We're not entirely certain. Without this route, however, some Longhorn pods fail to access K3s services when the cluster IP is configured on a non-default port. Signed-off-by: Milan Lenco <[email protected]>
milan-zededa
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR takes @naiming-zededa's commits from PR4408, fixes merge conflicts with the master and adds the last outstanding networking changes needed for the EVE node clustering (that depend on the content from PR4408).
For the description of the first 2 commits, see PR4408 (which is closed now since it is superseded with this PR).
The other two commits extends DPC Reconciler to configure cluster IP on the cluster interface and add some ACL rules to open ports needed for the nodes to communicate with each other.