Skip to content
This repository has been archived by the owner on Apr 25, 2023. It is now read-only.

kubefed: remove CrossClusterServiceDiscovery feature #1283

Closed
hectorj2f opened this issue Sep 28, 2020 · 1 comment
Closed

kubefed: remove CrossClusterServiceDiscovery feature #1283

hectorj2f opened this issue Sep 28, 2020 · 1 comment
Assignees
@hectorj2f
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@hectorj2f
Copy link
Contributor

hectorj2f commented Sep 28, 2020 •
edited
Loading

What would you like to be added:
Kubefed v2 should be only focused on the federation of resources across kubefed clusters. In the Kubernetes ecosystem there are other third party tools (such as service meshes or multi-cluster mesh) that already provide support to a DNS based cross cluster service discovery.

Why is this needed:

Therefore, we need to remove any related work as part of kubefed to keep the source code clean and focused on satisfying certain the federation of resources.

/kind feature
@hectorj2f hectorj2f self-assigned this Sep 28, 2020
@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Sep 28, 2020
@hectorj2f hectorj2f mentioned this issue Oct 12, 2020
Merged
@hectorj2f hectorj2f mentioned this issue Jan 28, 2021
Merged
@hectorj2f
Copy link
Contributor Author

Closing this issue. It has been addressed in #1351

@hectorj2f hectorj2f mentioned this issue Apr 7, 2021
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@hectorj2f hectorj2f

Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@hectorj2f @k8s-ci-robot