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

[Request] Multi cluster support for kubernetes discovery #642

Open
grzesuav opened this issue Sep 6, 2024 · 2 comments
Open

[Request] Multi cluster support for kubernetes discovery #642

grzesuav opened this issue Sep 6, 2024 · 2 comments
Labels
feat New feature or request needs-triage Needs thorough attention from code reviewers

Comments

@grzesuav
Copy link

grzesuav commented Sep 6, 2024

Describe the feature

Having several kubernetes clusters in the same service mesh, it would be good for Cryostat being able to discover targets in other clusters

Anything other information?

No response

@grzesuav grzesuav added feat New feature or request needs-triage Needs thorough attention from code reviewers labels Sep 6, 2024
@andrewazores
Copy link
Member

I think this sounds like a general solution might be to implement a service mesh discovery plugin. Are you talking about Istio in particular here?

@grzesuav
Copy link
Author

no, there are two separate problems.

For discover in remote cluster you just need kubernetes RBAC with remote api server endpoint. This is how i.e. ArgoCD does it (and many others). There is also initiative in kubernetes multicluster sig around standardizing Cluster Catalogue and Cluster Credentials - https://docs.google.com/document/d/1SZfgMiRArqlVJ0Yxygg7UAAGqPi4Eu18_2T7umxVTwg/edit - work in progress currently. The problem they aiming to solve is to define a common API, because currently different tools - like argocd, kueue etc are all using its own format.

As most API servers are publicly available it solves the accessibility problem for them.

However in case of cryostat it seconds step - even if you discover endpoints from api server cryostat still need to be able to connect via IP to those - they are various ways to do that, like https://docs.cilium.io/en/stable/network/clustermesh/clustermesh/#gs-clustermesh or istio.

This issue is about the first part - kubernetes service discovery

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feat New feature or request needs-triage Needs thorough attention from code reviewers
Projects
None yet
Development

No branches or pull requests

2 participants