-
Notifications
You must be signed in to change notification settings - Fork 642
etcd-less #3442
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
base: main
Are you sure you want to change the base?
etcd-less #3442
Conversation
/// Status of a service instance | ||
#[derive(Debug, Clone, PartialEq, Eq, Serialize, Deserialize)] | ||
pub enum InstanceStatus { | ||
/// Instance is ready to receive traffic |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
question do we need ready / not ready - or just rely on added and removed?
Signed-off-by: Anna Tchernych <[email protected]>
let metadata = self.metadata.clone(); | ||
let readiness_status = self.readiness_status.clone(); | ||
|
||
let app = axum::Router::new() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we combine this with the system http server?
impl KubernetesServiceDiscovery { | ||
/// Create a new Kubernetes service discovery client | ||
pub async fn new(namespace: String) -> Result<Self> { | ||
// TODO: Initialize Kubernetes client when kube crate is available |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
question: what is blocking kube crate?
} | ||
|
||
#[async_trait] | ||
impl ServiceRegistry for EtcdServiceDiscovery { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
question: currently we have 'endpoint' discovery - do we maintain that here or is there some common portion of the metadata that will include endpoints?
|
||
/// Represents a discovered service instance | ||
#[derive(Debug, Clone)] | ||
pub struct Instance { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
for endpoints - how would they be discovered or listed?
how do we get the client from the instance?
Overview:
Details:
Where should the reviewer start?
Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)
closes https://linear.app/nvidia/issue/DEP-386/kubernetes-implementation-for-servicediscovery-interface