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 #2158

Closed
Tracked by #1578
swasik opened this issue Oct 17, 2024 · 2 comments · May be fixed by #2159
Closed
Tracked by #1578

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

swasik opened this issue Oct 17, 2024 · 2 comments · May be fixed by #2159
Labels
kind/documentation Categorizes issue or PR as related to documentation. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Comments

@swasik
Copy link

swasik commented Oct 17, 2024

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

Problem

The following paragraph: For specific configuration and setup, check for details about your particular environment: lists just the link to GKE description.

Suggest a fix

Add missing link to EKS.

@scylla-operator-bot scylla-operator-bot bot added the needs-priority Indicates a PR lacks a `priority/foo` label and requires one. label Oct 17, 2024
@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 Oct 17, 2024
@scylla-operator-bot scylla-operator-bot bot removed the needs-priority Indicates a PR lacks a `priority/foo` label and requires one. label Oct 17, 2024
swasik added a commit to swasik/scylla-operator that referenced this issue Oct 17, 2024
Add missing link to EKS documentation.

Resolves scylladb#2158
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 Nov 17, 2024
@tnozicka
Copy link
Member

gone with #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. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants