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.

Sign up for GitHub

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

Jump to bottom

Multi-cluster support with Antrea #2770

Closed
15 tasks done
abhiraut opened this issue Sep 13, 2021 · 4 comments
Closed
15 tasks done

Multi-cluster support with Antrea #2770

abhiraut opened this issue Sep 13, 2021 · 4 comments
Labels
area/multi-cluster Issues or PRs related to multi cluster. kind/design Categorizes issue or PR as related to design. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@abhiraut
Copy link
Contributor

abhiraut commented Sep 13, 2021 •
edited by luolanzone
Loading

Describe what you are trying to solve

As the deployment of K8s clusters become more multiple cluster oriented, where users may deploy a single Service in multiple clusters or require access to Service in one cluster from other mutually trusted clusters, Antrea must be able to integrate with this multi cluster story and provide a set of APIs which makes it easier for users to consume Services in multiple clusters in a secure fashion. For more details on upstream MultiCluster Service APIs effort in k8s, see MCS API.

Describe the solution you have in mind

Introduce CRDs which allow users to easily create a set of mutually trusted K8s clusters and easily exchange information between these clusters in a secure manner.

Describe how your solution impacts user flows

Existing users will not be impacted. Users may start using the multi cluster APIs to connect their existing clusters to each other.

Describe the main design/architecture of your solution

See doc

Additional context
Following is an expected list of work items:

  • Introduce cluster registration/unregistration CRDs
  • Introduce resource exchange pipeline CRDs
  • Add multi cluster skeleton
  • Separate leader cluster controller and member cluster controller
  • Unlink from cert manager dependency
  • Add controllers to register/unregister clusters
  • Add controllers for exporting Services
  • Add reconcilers to reconcile MCS
  • Add controllers for importing MCS
  • Ensure validation webhooks are implemented for all components
  • Ensure e2e tests for all components
  • Ensure unit tests
  • CI pipeline
  • Introduce Stretched Antrea-native Network Policy design (track detailed items separately)
  • Introduce datapath connectivity plan between Multi clusters (track detailed items separately)
@abhiraut abhiraut added the kind/design Categorizes issue or PR as related to design. label Sep 13, 2021
@abhiraut
Copy link
Contributor Author

/cc @luolanzone @aravindakidambi

@luolanzone luolanzone added the area/multi-cluster Issues or PRs related to multi cluster. label Oct 21, 2021
@luolanzone luolanzone mentioned this issue Oct 21, 2021
Closed
@luolanzone luolanzone mentioned this issue Dec 9, 2021
Closed
@github-actions
Copy link
Contributor

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment, or this will be closed in 90 days

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 16, 2022
@luolanzone luolanzone removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 16, 2022
@luolanzone luolanzone mentioned this issue Mar 22, 2022
Closed
@github-actions
Copy link
Contributor

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment, or this will be closed in 90 days

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 15, 2022
@luolanzone luolanzone removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 15, 2022
@github-actions
Copy link
Contributor

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment, or this will be closed in 90 days

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/multi-cluster Issues or PRs related to multi cluster. kind/design Categorizes issue or PR as related to design. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@abhiraut @luolanzone