docs: Issue on page Deploying Scylla on EKS

scylladb / scylla-operator

The Kubernetes Operator for ScyllaDB

https://operator.docs.scylladb.com/

Apache License 2.0

339 stars 175 forks source link

docs: Issue on page Deploying Scylla on EKS #2084

Open gcarmin opened 2 months ago

gcarmin commented 2 months ago

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

Problem

Where this configuration should go? Which file?

tnozicka commented 2 months ago

Where this configuration should go?

Please be specific about what you mean and what youa sk to be changed

gcarmin commented 2 months ago

All of the config snippets that are below this part - https://operator.docs.scylladb.com/v1.13/eks#creating-an-eks-cluster for example:

A NodeGroup of 3 i3-2xlarge Nodes, where the Scylla Pods will be deployed. These nodes will only accept pods having scylla-clusters toleration.

  - name: scylla-pool
    instanceType: i3.2xlarge
    desiredCapacity: 3
    labels:
      scylla.scylladb.com/node-type: scylla
    taints:
      role: "scylla-clusters:NoSchedule"
    ssh:
      allow: true
    kubeletExtraConfig:
      cpuManagerPolicy: static

tnozicka commented 2 months ago

yeah, this one is a bit of a mess. Some place should say this is from the eksctl config https://github.com/scylladb/scylla-operator/blob/b3da0a4/examples/eks/eks-cluster.yaml

scylla-operator-bot[bot] commented 1 month ago

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 commented 1 month ago

/remove-lifecycle stale /triage accepted