commit | 6ba11f333881739326d62675f4dea32aeea2fca3 | [log] [tgz] |
---|---|---|
author | Trista Pan <hannkenn@163.com> | Sun Sep 18 20:05:38 2022 +0800 |
committer | GitHub <noreply@github.com> | Sun Sep 18 20:05:38 2022 +0800 |
tree | 227e5d51e5adbba63273ab8798dcd13b61d8e8b3 | |
parent | fe40f07b4e39377ad27af93e9f99644f47b13466 [diff] | |
parent | 15665301c8557cf31d6fa0f26ad12da70e6090ae [diff] |
Merge pull request #63 from mlycore/it-case
Apache ShardingSphere Official Website: https://shardingsphere.apache.org/
This repository collects scripts, tools, manifests and documentations, provides home for Apache ShardingSphere on cloud solutions.
Solutions currently included in this project:
Currently, either The ShardingSphere Helm Charts and The ShardingSphere Operator would create the latest version as 5.2.0 of ShardingSphere Proxy. Just following the Quick Start and give it a try!
The ShardingSphere Helm Charts uses Helm to provide guidance for the installation of ShardingSphere-Proxy instance in a Kubernetes cluster.
Please follows instructions to deploy a ShardingSphere cluster with version 5.2.0.
The ShardingSphere Operator uses predefined CustomResourceDefinitions for describing a Deployment for Apache ShardingSphere on Kubernetes.
With the help of ShardingSphere-Operator you could create a ShardingSphere-Proxy cluster including the ZooKeeper cluster in minutes.
For installation of SharingSphere-Operator, you will need a Kubernetes cluster, no matter it is a managed Kubernetes service like AWS EKS or self-hosted Kubernetes, or just a mini-kube, you can easily install ShardingSphere-Operator with respective ShardingSphere Operator Helm Charts, and apply the manifests in ShardingSphere Cluster Helm Charts describing the expected Apache ShardingSphere deployment. Kubernetes 1.18+ is recommended.
Minimum Viable Product
Please follows instructions to deploy a ShardingSphere cluster with version 5.2.0.
To build ShardingSphere Operator from scratch you will need to install the following tools:
To contribute to this project, refer to Contributing.
:link: Mailing List. Best for: Apache community updates, releases, changes.
:link: GitHub Issues. Best for: larger systemic questions/bug reports or anything development related.
:link: GitHub Discussions. Best for: technical questions & support, requesting new features, proposing new features.
:link: Slack channel. Best for: instant communications and online meetings, sharing your applications.
:link: Twitter. Best for: keeping up to date on everything ShardingSphere.
Apache License 2.0, see LICENSE.