Skip to content
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

examples: using planetscale's vitess-operator #6154

Merged
merged 5 commits into from
May 13, 2020

Conversation

sougou
Copy link
Contributor

@sougou sougou commented May 6, 2020

This is the vitess example deployed against PlanetScale's operator.

The operator is much faster and feels more stable than the helm charts. Until we find a more committed maintainer for the helm charts, I feel like this should be the recommended way to use vitess on Kubernetes.

@sougou sougou requested review from enisoc and morgo May 6, 2020 20:49
Copy link
Member

@deepthi deepthi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice work!

name: example
spec:
images:
vtctld: us.gcr.io/planetscale-vitess/lite:2020-04-24.228e6fe
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any particular reason to pin the version? Local examples run against latest code/build.

tabletPools:
description: TabletPools specify groups of tablets in
a given cell with a certain tablet type and a shared
configuration template. There
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here we seem to always use the latest image.

@derekperkins
Copy link
Member

The helm charts should be deprecated, they're not a viable way to run Vitess

Copy link
Contributor

@morgo morgo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@@ -1,6 +0,0 @@
{
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are files being removed from examples/local in this PR? Is it related?

@@ -0,0 +1,43 @@
minikube start --cpus=8 --memory=11000 --disk-size=50g --kubernetes-version=v1.14.9
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we clean this up into a README.md before merging?

Signed-off-by: Sugu Sougoumarane <ssougou@gmail.com>
Signed-off-by: Sugu Sougoumarane <ssougou@gmail.com>
Signed-off-by: Sugu Sougoumarane <ssougou@gmail.com>
Signed-off-by: Sugu Sougoumarane <ssougou@gmail.com>
@enisoc
Copy link
Member

enisoc commented May 13, 2020

@sougou I've created a tag so we can pin the operator image too now:

planetscale/vitess-operator:v2.0.0

Signed-off-by: Sugu Sougoumarane <ssougou@gmail.com>
Copy link
Member

@enisoc enisoc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@morgo morgo merged commit 3f68101 into vitessio:master May 13, 2020
@sougou sougou deleted the ss-operator-example branch May 18, 2020 02:48
@deepthi deepthi added this to the v7.0 milestone Jul 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants