Skip to content

Conversation

@linki
Copy link
Member

@linki linki commented Jun 25, 2025

We can now use the cluster-registry client from the cluster-registry project (or any other central library).

The goal is to unify several projects and have them use a single cluster-registry client implementation shared between them. In this first step it only extracts the generated part of it. However, we do also have a wrapper that adds certain convenience functions. If these were also extracted into a central library, other projects could also use them and we would have a unified and easy way to access cluster-registry throughout our projects.

Other higher-level functionality like asynchronous refreshing a local list of clusters from deployment-service could also be part of a central cluster-registry abstraction library.

@linki linki added the minor Minor changes, e.g. low risk config updates, changes that do not introduce a new API call. label Jun 25, 2025
@linki linki force-pushed the use-upstream-cluster-registry-client branch from 17b320a to 625eec7 Compare June 25, 2025 09:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge minor Minor changes, e.g. low risk config updates, changes that do not introduce a new API call.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants