Skip to content
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

Closed
dushaniw opened this issue Oct 24, 2022 · 4 comments
Closed

APK Management server and Adapter implementation #11

dushaniw opened this issue Oct 24, 2022 · 4 comments

Comments

@dushaniw
Copy link

dushaniw commented Oct 24, 2022

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

  • Talks to the K8s API server and manages (Create, Update, Delete) resources in the K8s cluster(DP) -> Create APIs (in UI driven approach), Applying policies (from UI)
  • Update rate limit service with rate limit policies -> Will be an xDS communication
  • Update enforcer with subscription details, etc. -> Will be an xDS communication
  • Should have a K8s operator to listen on the resources created on the DP cluster.
  • Communicate with CP - xDS

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).

  • Send API create/delete/update, Subscription, Policy events to the APK client - xDS
  • Service registering.
  • Update control plane with the resources created on dataplane(using cli) such as APIs, Policies, etc..

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.

@npamudika
Copy link

npamudika commented Oct 24, 2022

Sub Tasks

Initial Designs and Definitions

Management server XDS communication

Adapter to Management Server gRPC unary communication

Main issue:

Sub tasks:

Data partitioning for Choreo

Agent Implementation - CP

Agent Implementation - DP

Management Server to DB Transactions

Additional Sub Tasks

@AmaliMatharaarachchi
Copy link
Contributor

AmaliMatharaarachchi commented Nov 16, 2022

Updated Task list

GRPC Unary call for sending API updates to Management Server

@AmaliMatharaarachchi
Copy link
Contributor

closing as this issue is no longer required.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment