Deploying Scylla on GKE - minimal example

[tzach]

The GKE example is great, but often newcomers want to run a minimal, functional demo. It would be nice to have an easy option to do that.

[tnozicka]

Minimal as using developer mode and no tuning?

Without tuning it would be fairly easy as it would be cloud agnostic and didn't grow our examples matrix.

What I do is:

1. Deploy the operator
2. kubectl create namespace test
3. kubectl -n test create -f test/e2e/fixture/scyllacluster/basic.scyllacluster.yaml (or custom CR)
4. kubectl -n test create serviceaccount basic-member
5. kubectl -n test create rolebinding basic-member --clusterrole=scyllacluster-member --serviceaccount=test:basic-member

Steps 4. and 5. will go away when we fix https://github.com/scylladb/scylla-operator/issues/450 so it's just deploying the operator and creating a scyllacluster CR.

We can certainly expand our easy ramp up and document this case.

[tnozicka]

There is also the question of storage. We currently support only local disks but dedicated disks cost a lot of money just for a minimal test case. There is a way to set it up (https://github.com/scylladb/scylla-operator/pull/694) which doesn't need SSDs but that could also get easier when we can run on cloud persistent storage.

[scylla-operator-bot[bot]]

The Scylla Operator project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 30d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out

/lifecycle stale

[tnozicka]

/remove-lifecycle stale /triage accepted