-
Notifications
You must be signed in to change notification settings - Fork 29
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
Enhance ComputeNode reconciliation #277
Labels
Milestone
Comments
mlycore
added
gsoc-2023
GSoC 2023
operator
solutions of operator
type: enhancement
New feature or request
labels
Mar 22, 2023
mlycore
changed the title
[GSOC 2023] Enhance ComputeNode reconciliation
Enhance ComputeNode reconciliation
May 18, 2023
7 tasks
Stale issue. Closed |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Apache ShardingSphere
Apache ShardingSphere is positioned as a Database Plus, and aims at building a standard layer and ecosystem above heterogeneous databases. It focuses on how to reuse existing databases and their respective upper layer, rather than creating a new database. The goal is to minimize or eliminate the challenges caused by underlying databases fragmentation.
Page: https://shardingsphere.apache.org/
Github: https://github.com/apache/shardingsphere
Background
There is a proposal about new CRD Cluster and ComputeNode as belows:
Currently we try to promote ComputeNode as major CRD to represent a special ShardingSphere Proxy deployment. And plan to use Cluster indicating a special ShardingSphere Proxy cluster.
Task
This issue is to enhance ComputeNode reconciliation availability. The specific case list is as follows.
Notice, these issues can be a good example.
Relevant Skills
Targets files
ComputeNode IT - https://github.com/apache/shardingsphere-on-cloud/blob/main/shardingsphere-operator/pkg/reconcile/computenode/compute_node_test.go
The text was updated successfully, but these errors were encountered: