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

Workload: Container: Unable to set cpu and memory limitations #11955

Closed
richard-cox opened this issue Sep 18, 2024 · 1 comment
Closed

Workload: Container: Unable to set cpu and memory limitations #11955

richard-cox opened this issue Sep 18, 2024 · 1 comment
Labels
area/vue3 kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Milestone

Comments

@richard-cox
Copy link
Member

Setup

  • Rancher version: 2.10.0

Describe the bug

  • Input fields for CPU Reservation, Memory Reservation, CPU Limit and Memory Limit are really broken
    • CPU fields - enter 1 and get 1000 instead
    • Memory fields - unable to enter anything other than 1 or 0

To Reproduce
Cluster Explorer --> Workloads --> Pods --> Create --> container --> Resources tab

Result
as per description

Expected Result

  • user should be able to enter whatever value they wish (there might possibly be a restriction if there are resource limits set in the project of the target namespace)

Screenshots
image

Additional context
assuming this is something to do with how we handle user input vs the actual base unit of what we set on the model

@richard-cox richard-cox added this to the v2.10.0 milestone Sep 18, 2024
@github-actions github-actions bot added QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this and removed area/vue3 labels Sep 18, 2024
@rak-phillip
Copy link
Member

Closing this issue as a duplicate of #11881. Fixed in #11939.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/vue3 kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Projects
None yet
Development

No branches or pull requests

2 participants