-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
APK Management server and Adapter implementation #11
Comments
Design and User Flows Document - https://docs.google.com/document/d/1F15zHzHi8ercomq5J3yR8P6TjkVWhhUQ1lnOF4_JCcU/edit?usp=sharing Events and Data Document - https://docs.google.com/document/d/1opdltBxJIkz3Tn_CsxXbHI7RrhmsXaSgZAq27oayr_s/edit?usp=sharing DP and CP K8s CRDs for APK - https://docs.google.com/document/d/1CL5ug6neMn-caLbjzLOJms8TNuMSw9evSaEHjQRFudQ/edit?usp=sharing APK Management Server and Agent Client Implementation - https://docs.google.com/document/d/16-dsKnp_PgnAHdxoaTUTsP51yZ_unRTmf6dScGw9UgM/edit?usp=sharing |
Updated Task listGRPC Unary call for sending API updates to Management Server |
closing as this issue is no longer required. |
Functionality of APK Agent Client
APK Agent is the responsible party for managing the data-plane cluster by managing its components as well as keeping the control plane sync-up with data-plane.
Mainly it has the following functionality
Functionality of APK Management Server
Management server is the responsible party for keeping the CP & DP sync by communicating with APK clients in each data-planes (or in the same control-plane when we run in a single cluster).
APK Management Server to APK Agent Client Communication
API Agent Client should be associated with a k8s operator, which is watching for resource updates and sending the updates to the control plane’s Management Server and the Gateway.
Since we have only one control plane available, we decided to make this communication as a gRPC client to server streaming communication.
The text was updated successfully, but these errors were encountered: