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

Add docummentation page about using scylla enterprise #1396

Closed
tnozicka opened this issue Sep 14, 2023 · 4 comments
Closed

Add docummentation page about using scylla enterprise #1396

tnozicka opened this issue Sep 14, 2023 · 4 comments
Assignees
Labels
kind/documentation Categorizes issue or PR as related to documentation. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@tnozicka
Copy link
Member

operator.docs.scylladb.com should have an example with Scylla Enterprise and mention everything works the same way explicitly.

@tnozicka tnozicka added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. kind/documentation Categorizes issue or PR as related to documentation. labels Sep 14, 2023
@tnozicka tnozicka self-assigned this Sep 14, 2023
@tomer-sandler
Copy link

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] - #1396
[2] - https://github.com/scylladb/scylla-operator/blob/v1.10/deploy/README.md

Copy link
Contributor

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

@scylla-operator-bot scylla-operator-bot bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 28, 2024
@tnozicka
Copy link
Member Author

tnozicka commented Jul 1, 2024

/remove-lifecycle stale
/triage accepted

@scylla-operator-bot scylla-operator-bot bot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jul 1, 2024
@tnozicka
Copy link
Member Author

done in #2188

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/documentation Categorizes issue or PR as related to documentation. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

2 participants