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.

Sign up for GitHub

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

Jump to bottom

GKE RAID improvements #93

Closed
mmatczuk opened this issue May 26, 2020 · 2 comments
Closed

GKE RAID improvements #93

mmatczuk opened this issue May 26, 2020 · 2 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@mmatczuk
Copy link
Contributor

mmatczuk commented May 26, 2020 •
edited
Loading

GKE raid-daemonset.yaml uses yanniszark/raid-setup:0.1 image you can just use any image for that like alpine. In addition to that it seems that there is more room for improvement with regards to disks [1] in the context of [2] I have found [3] witch seems to be k8s implementation of [1].

We should evaluate it.

[1] https://cloud.google.com/compute/docs/disks/optimizing-local-ssd-performance
[2] kubernetes-sigs/sig-storage-local-static-provisioner#65
[3] https://github.com/pingcap/tidb-operator/blob/master/manifests/gke/local-ssd-provision/local-ssd-provision.yaml#L24
@mmatczuk mmatczuk added the kind/feature Categorizes issue or PR as related to a new feature. label May 26, 2020
@mmatczuk mmatczuk mentioned this issue May 28, 2020
Closed
@ezbz ezbz added this to the 1.x milestone Feb 23, 2021
@tnozicka tnozicka removed this from the v1.x milestone May 27, 2021
@scylla-operator-bot
Copy link
Collaborator

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 19, 2024
@scylla-operator-bot scylla-operator-bot
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 rotten
  • Close this issue with /close
  • Offer to help out

/lifecycle rotten

@scylla-operator-bot scylla-operator-bot bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jul 20, 2024
@tnozicka
Copy link
Contributor

now managed with https://operator.docs.scylladb.com/v1.13/api-reference/groups/scylla.scylladb.com/nodeconfigs.html#api-scylla-scylladb-com-nodeconfigs-v1alpha1-spec-localdisksetup-raids

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@ezbz @mmatczuk @tnozicka @scylla-operator-bot