We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Follow-up from #11374
python -m venv venv source venv/bin/activate
pip install kfp==2.10
from kfp import dsl @dsl.component() def pass_component(): pass @dsl.pipeline(name='pipeline-requests') def pipeline_requests(): task = pass_component() task.set_cpu_request('100m').set_memory_request('100Mi').set_cpu_limit('500m').set_memory_limit('500Mi')
kfp dsl compile --py req-test.py --output req-test.yaml
According to @vanHavel user:
After updating to kfp SDK 2.10, we saw pods running with no resources on kfp server 2.3. It seems that in the generated pipeline spec, the keys for CPU / RAM requests and limits have changed as well (probably in https://github.com/kubeflow/pipelines/pull/11097).
The pod should include the resources definition for CPU/Memory, including requests and limits.
When compiling the pipeline with 2.10 it renders the following:
resources: resourceCpuLimit: 500m resourceCpuRequest: 100m resourceMemoryLimit: 500Mi resourceMemoryRequest: 100Mi
With older version such as 2.9, it renders the following:
resources: cpuLimit: 0.5 cpuRequest: 0.1 memoryLimit: 0.524288 memoryRequest: 0.1048576
Impacted by this bug? Give it a 👍.
The text was updated successfully, but these errors were encountered:
/assign @rimolive
Sorry, something went wrong.
rimolive
Successfully merging a pull request may close this issue.
Follow-up from #11374
Environment
Steps to reproduce
According to @vanHavel user:
Expected result
The pod should include the resources definition for CPU/Memory, including requests and limits.
Materials and Reference
When compiling the pipeline with 2.10 it renders the following:
With older version such as 2.9, it renders the following:
Impacted by this bug? Give it a 👍.
The text was updated successfully, but these errors were encountered: