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

Support kubectl scale and the /scale subresource #497

Open
tnozicka opened this issue Mar 15, 2021 · 4 comments
Open

Support kubectl scale and the /scale subresource #497

tnozicka opened this issue Mar 15, 2021 · 4 comments
Assignees
Labels
priority/backlog Higher priority than priority/awaiting-more-evidence. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@tnozicka
Copy link
Member

Is this a bug report or feature request?

  • Feature Request

What should the feature do:

# kubectl get scyllacluster/basic
NAME    AGE
basic   3m57s

# kubectl scale scyllacluster/basic --replicas=3
Error from server (NotFound): scyllaclusters.scylla.scylladb.com "basic" not found

What is use case behind this feature:

Additional Information:
We need to support the scale subresource.

@tnozicka tnozicka added the kind/feature Categorizes issue or PR as related to a new feature. label Mar 15, 2021
@tnozicka tnozicka added this to the 1.x milestone Mar 15, 2021
@tnozicka
Copy link
Member Author

I suppose would scale the members in every rack.

@tnozicka tnozicka removed this from the v1.x milestone May 27, 2021
@rzetelskik rzetelskik self-assigned this Aug 2, 2021
@tnozicka tnozicka added the priority/backlog Higher priority than priority/awaiting-more-evidence. label Aug 2, 2021
@tnozicka tnozicka modified the milestones: v1.6, v1.7 Aug 2, 2021
@tnozicka tnozicka modified the milestones: v1.7, v1.8 Dec 9, 2021
@zimnx zimnx modified the milestones: v1.8, v1.9 Jan 27, 2023
@tnozicka tnozicka removed this from the v1.9 milestone Aug 16, 2023
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 Jun 24, 2024
@tnozicka tnozicka assigned zimnx and unassigned rzetelskik Jun 24, 2024
@tnozicka tnozicka added triage/accepted Indicates an issue or PR is ready to be actively worked on. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/backlog Higher priority than priority/awaiting-more-evidence. labels Jun 24, 2024
@tnozicka
Copy link
Member Author

@zimnx this might be a good one to look at for ScyllaDBDatacenter

@tnozicka
Copy link
Member Author

We have decided to postpone it in favour of a dedicated proposal, but for the future some context on the complexities is in #1994 (comment)

@tnozicka tnozicka added priority/backlog Higher priority than priority/awaiting-more-evidence. and removed priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. kind/feature Categorizes issue or PR as related to a new feature. labels Jul 12, 2024
@tnozicka tnozicka changed the title Support kubectl scale Support kubectl scale and the /scale subresource Jul 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/backlog Higher priority than priority/awaiting-more-evidence. 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