Skip to content
This repository has been archived by the owner on May 13, 2024. It is now read-only.

feat: sync exported services to new joined clusters #124

Open
reaver-flomesh opened this issue Nov 11, 2022 · 3 comments
Open

feat: sync exported services to new joined clusters #124

reaver-flomesh opened this issue Nov 11, 2022 · 3 comments
Assignees
Labels
area/multi-cluster Multicluster task/issue change/go Pull requests that update Go code kind/enhancement New feature or request kind/research-required size/L 14 days (~2.5 weeks)
Milestone

Comments

@reaver-flomesh
Copy link
Collaborator

Please describe the Improvement and/or Feature Request

Scope (please mark with X where applicable)

  • New Functionality [ ]
  • Install [ ]
  • Gateway API - GatewayClass [ ]
  • Gateway API - Gateway [ ]
  • Gateway API - HTTPRoute [ ]
  • Gateway API - TLSRoute [ ]
  • Gateway API - TCPRoute [ ]
  • Gateway API - UDPRoute [ ]
  • Gateway API - PolicyReference [ ]
  • Ingress [ ]
  • Egress [ ]
  • MultiCluster [x]
  • PIPY Control Plane [ ]
  • PIPY Script/Config [ ]
  • CLI Tool [ ]
  • Metrics [ ]
  • Certificate Management [ ]
  • Sidecar Injection [ ]
  • Logging [ ]
  • Debugging [ ]
  • Tests [ ]
  • Demo [ ]
  • CI System [ ]
  • Project Release [ ]

Possible use cases

@reaver-flomesh reaver-flomesh added this to the v0.2.0 milestone Nov 11, 2022
@reaver-flomesh reaver-flomesh added kind/enhancement New feature or request change/go Pull requests that update Go code area/multi-cluster Multicluster task/issue labels Nov 11, 2022
@reaver-flomesh reaver-flomesh self-assigned this Nov 17, 2022
@reaver-flomesh
Copy link
Collaborator Author

  1. persist the service export and import state, propagate and maintain the state to be consistent across the entire ClusterSet
  2. handle the case which service spec is modified, should export it again and remove imports if there's any conflicts

@reaver-flomesh
Copy link
Collaborator Author

reaver-flomesh commented Nov 24, 2022

  1. persist the service export and import state, propagate and maintain the state to be consistent across the entire ClusterSet
  2. handle the case which service spec is modified, should export it again and remove imports if there's any conflicts

Item 2 will be covered in another issue #138

@reaver-flomesh reaver-flomesh modified the milestones: v0.2.0, v0.2.1 Nov 24, 2022
@reaver-flomesh
Copy link
Collaborator Author

need some investigation, nats-server is a good option

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/multi-cluster Multicluster task/issue change/go Pull requests that update Go code kind/enhancement New feature or request kind/research-required size/L 14 days (~2.5 weeks)
Projects
None yet
Development

No branches or pull requests

1 participant