docs: Issue on page Deploying Scylla on a Kubernetes Cluster

[gcarmin]

I would like to report an issue on page https://operator.docs.scylladb.com/v1.13/generic

Problem

Where can I configure the Scylla version - OSS / Ent?

[tnozicka]

see #1396 (comment)

dupe of #1396

[gcarmin]

Hi @tnozicka - I've followd the links provided and didn't found where and when there is a plan to add this one to our official doc's.
can you please elaborate on this one.

[tzach]

dupe of #1396

The context is different:
#1396 is about Enterprise
This issue concerns choosing the Scylla version (e.g. 6.1, 2024.2) in Enterprise or Open Source. The data is probably available as a reference, but it is hard to find.
This essential information element should be available on the install/onboarding page.

[tnozicka]

On the referenced page there exactly 6 matches for firefox search for version - each 2 of them match an example setting the version and agentVersion correspondingly.

There is also a description of that field on ScyllaCluster.spec in our docs https://operator.docs.scylladb.com/v1.13/api-reference/groups/scylla.scylladb.com/scyllaclusters.html#spec

I am not saying there isn't space for improvement but I am surprised for it being hard to find.
(We do have plans to address the structure, overview and initial guidance, just not the bandwidth yet.)

[tzach]

I am not saying there isn't space for improvement but I am surprised for it being hard to find.

Its hard. There are many "versions": API, Doc, Operator ...

We do have plans to address the structure, overview and initial guidance

+1

It is not the same, but this page is a good example for highlighting the most relevant option of the install (like version)
https://opensource.docs.scylladb.com/stable/getting-started/install-scylla/install-on-linux.html

[scylla-operator-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