search

kubernetes-sigs / mcs-api

This repository hosts the Multi-Cluster Service APIs. Providers can import packages in this repo to ensure their multi-cluster service controller implementations will be compatible with MCS data planes.
Apache License 2.0
199 stars 39 forks source link

General feedback/questions #9

Closed steeling closed 2 years ago

steeling commented 3 years ago

I'm not familiar with the standard procedure around K8s proposals and the implementation process. Is there a place where k8s looks for community feedback? Or a way to comment/ask questions around designs?

I've read kep 1645, and have some general questions I'd like to get answered. In lieu of a better place to put these questions I'll add them here, but feel free to close this if there's a better place:

  1. The implementation of the MCS is not well defined in the spec. Including how it learns about the endpoints/endpointslices from non-local clusters that are part of the clusterset. How does the MCS authenticate, or what API's is it hitting specifically? Are there new API's or does it use the standard K8s API's?
  2. Since the interop API's are not defined, is it expected that 2 different K8s implementations can be part of the same clusterset?
  3. Can you elaborate how networking works for Cluster IP's with internal IP addresses on non-network connected K8s clusters?

My guess for #3 is that it's not supported, but I'd also guess that this is one of the biggest use cases (or at least would be if it was supported). I'm surprised to see this proposal not include an ingress option for these services, or at least a way to configure it.

Cheers!

k8s-triage-robot commented 2 years ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 2 years ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot commented 2 years ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

k8s-ci-robot commented 2 years ago

@k8s-triage-robot: Closing this issue.

In response to [this](https://github.com/kubernetes-sigs/mcs-api/issues/9#issuecomment-950091609): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages issues and PRs according to the following rules: >- After 90d of inactivity, `lifecycle/stale` is applied >- After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied >- After 30d of inactivity since `lifecycle/rotten` was applied, the issue is closed > >You can: >- Reopen this issue or PR with `/reopen` >- Mark this issue or PR as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.