planetscale / planetscale/vitess-operator
Question about External MySQL + --unmanaged=false
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 372
- Forks
- 102
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 15
Description
Hello, I wonder it is possible to operate External MySQL with --unmanaged=false flag.
I consider to operate with my own vanilla MySQL to manage mysql myself(init/start/stop..), not with vitess and want to use vitess management features(reparent, reshard, replication, ...) except backup/restore.
I wonder there is some potential problem and usecase like this.
For example,
vttablet:
extraFlags:
db-charset: utf8mb4
log-format: text
unmanaged: "false"
resources:
limits:
memory: 256Mi
requests:
cpu: 100m
memory: 256Mi
externalDatastore:
user: vt_dba
host: targethost
port: 3306
database: vt_test
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how the operator handles the vttablet unmanaged flag together with externalDatastore. Determine whether an externally managed vanilla MySQL can still support reparenting, resharding, and replication while excluding backup and restore; document any limitations or required changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100