Open tnozicka opened 9 months ago
Capturing what @tnozicka sent over email.
Regarding enterprise, there is nothing special except changing where the image
comes from with repository
and version
.
$ kubectl explain scyllacluster.spec.repository
KIND: ScyllaCluster
VERSION: [scylla.scylladb.com/v1](http://scylla.scylladb.com/v1)
FIELD: repository <string>
DESCRIPTION:
repository is the image repository to pull the Scylla image from.
$ kubectl explain scyllacluster.spec.version
KIND: ScyllaCluster
VERSION: [scylla.scylladb.com/v1](http://scylla.scylladb.com/v1)
FIELD: version <string>
DESCRIPTION:
version is a version tag of Scylla to use.
So if they want to use image docker.io/scylladb/scylla-enterprise:2023.1 then
they would add/replace repository: [docker.io/scylladb/scylla-enterprise
](http://docker.io/scylladb/scylla-enterprise) and
version: 2023.1
in the ScyllaCluster CR which looks like
https://github.com/scylladb/scylla-operator/blob/v1.10/examples/generic/cluster.yaml
I've filled an issue to add a specific docs page around using enterprise [1].
Not sure if they are looking for GitOps style instructions or Helm but just in case the GitOps / manifests deployment is shown in [2].
Regards, Tomas
[1] - https://github.com/scylladb/scylla-operator/issues/1396 [2] - https://github.com/scylladb/scylla-operator/blob/v1.10/deploy/README.md
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:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
/lifecycle stale
/remove-lifecycle stale /triage accepted
operator.docs.scylladb.com should have an example with Scylla Enterprise and mention everything works the same way explicitly.