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

docs: Issue on page Deploying Scylla on a Kubernetes Cluster #2082

Open
Tracked by #1578
gcarmin opened this issue Aug 18, 2024 · 7 comments
Open
Tracked by #1578

docs: Issue on page Deploying Scylla on a Kubernetes Cluster #2082

gcarmin opened this issue Aug 18, 2024 · 7 comments
Labels
kind/documentation Categorizes issue or PR as related to documentation. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@gcarmin
Copy link

gcarmin commented Aug 18, 2024

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?

@scylla-operator-bot scylla-operator-bot bot added the needs-priority Indicates a PR lacks a `priority/foo` label and requires one. label Aug 18, 2024
@tnozicka
Copy link
Member

see #1396 (comment)

dupe of #1396

@tnozicka tnozicka closed this as not planned Won't fix, can't repro, duplicate, stale Aug 19, 2024
@gcarmin
Copy link
Author

gcarmin commented Aug 19, 2024

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
Copy link
Contributor

tzach commented Aug 19, 2024

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.

@tzach tzach reopened this Aug 19, 2024
@tnozicka
Copy link
Member

tnozicka commented Aug 19, 2024

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
Copy link
Contributor

tzach commented Aug 19, 2024

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

@tnozicka tnozicka added kind/documentation Categorizes issue or PR as related to documentation. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Aug 19, 2024
@scylla-operator-bot scylla-operator-bot bot removed the needs-priority Indicates a PR lacks a `priority/foo` label and requires one. label Aug 19, 2024
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 Sep 19, 2024
@tnozicka
Copy link
Member

/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 Sep 24, 2024
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-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

3 participants