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

Be able to scale SeldonDeployment objects using kubectl #1598

Closed
pisymbol opened this issue Mar 25, 2020 · 1 comment · Fixed by #1633
Closed

Be able to scale SeldonDeployment objects using kubectl #1598

pisymbol opened this issue Mar 25, 2020 · 1 comment · Fixed by #1633

Comments

@pisymbol
Copy link

kubectl allows one to scale their normal Deployment objects using the 'kubectl scale' command by setting the '--replicaset' command line argument to the number of Pods you want the underlying ReplicaSet to achieve.

However, with SeldonDeployment objects, you can't do this. In fact, in 1.0+, you can't even use kubectl scale on the underlying Deployment object that backs the SeldonDeployment one to up the number of prediction server Pods.

What you have to do is delete and redeploy the SeldonDeployment object and up the number of 'replicas' in the original YAML/JSON deployment file.

I think it would be best if SeldonDeployment objects could scale like regular Deployment ones as their configuration and management idioms should be fairly the same.

(I also think both 'seldonDeployment' and 'seldondeploy' should work with kubectl too, just like deployment).

@pisymbol pisymbol added the triage Needs to be triaged and prioritised accordingly label Mar 25, 2020
@pisymbol pisymbol changed the title Be able to scale SeldonDeployments using kubectl Be able to scale SeldonDeployment objects using kubectl Mar 25, 2020
@ukclivecox
Copy link
Contributor

Duplicate #1592

@ukclivecox ukclivecox removed the triage Needs to be triaged and prioritised accordingly label Mar 30, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants