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

Commit

Permalink
Updated README.md (#281)
Browse files Browse the repository at this point in the history
There are people who think MySQL Operator can work with MySQL NDB Cluster. Update the readme to avoid confusion.
  • Loading branch information
YoshiakiYamasaki authored and owainlewis committed May 15, 2019
1 parent cfc3e5b commit 9aebcc3
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# MySQL Operator

The MySQL [Operator][1] creates, configures and manages MySQL clusters running on Kubernetes.
The MySQL [Operator][1] creates, configures and manages MySQL InnoDB clusters running on Kubernetes. It is not for MySQL NDB Cluster.

[![issues](https://img.shields.io/github/issues/oracle/mysql-operator.svg)](https://github.com/oracle/mysql-operator/issues)
[![tags](https://img.shields.io/github/tag/oracle/mysql-operator.svg)](https://github.com/oracle/mysql-operator/tags)
Expand All @@ -23,7 +23,7 @@ See the [tutorial][5] which provides a quick-start guide for users of the Oracle

The MySQL Operator provides the following core features:

- Create and delete highly available MySQL clusters in Kubernetes with minimal effort
- Create and delete highly available MySQL InnoDB clusters in Kubernetes with minimal effort
- Automate database backups, failure detection, and recovery
- Schedule automated backups as part of a cluster definition
- Create "on-demand" backups.
Expand Down

0 comments on commit 9aebcc3

Please sign in to comment.