You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is the issue report properly structured and detailed with version numbers?
Is this for Kubeflow development ?
Would you like to work on this issue?
You can join the CNCF Slack and access our meetings at the Kubeflow Community website. Our channel on the CNCF Slack is here #kubeflow-platform.
Version
1.8
Describe your issue
our k8s cluster has setup resource quota per namespace, i.e. each running pods in that namespace should be specify resource.requests / resource.limits.
when our newly installed kubeflow 1.8 (and we checked the code, version after 1.8 have similar issue),
running the following example raised failed quota errors.
fromkfpimportdslfromkfpimportcompilerimportos# In tests, we install a KFP package from the PR under test. Users should not# normally need to specify `kfp_package_path` in their component definitions._KFP_PACKAGE_PATH=os.getenv('KFP_PACKAGE_PATH')
@dsl.component(kfp_package_path=_KFP_PACKAGE_PATH)defhello_world(text: str) ->str:
print(text)
returntext@dsl.pipeline(name='hello-world', description='A simple intro pipeline')defpipeline_hello_world(text: str='hi there'):
"""Pipeline that passes small pipeline parameter string to consumer op."""consume_task=hello_world(
text=text).set_cpu_request('1').set_memory_request('650M').set_cpu_limit('1').set_memory_limit('1G') # Passing pipeline parameter as argument to consumer opif__name__=="__main__":
# execute only if run as a scriptcompiler.Compiler().compile(
pipeline_func=pipeline_hello_world,
package_path='hello_world_pipeline.json')
with the following error message:
task 'hello-world-w8rxr.root-driver' errored: pods "hello-world-w8rxr-1768006001" is forbidden: failed quota: kf-resource-quota: must specify cpu for: init,wait
the message suggests that default argo container (init/wait) requires resources quota too.
The above error message is gone when we patch the configmap of argo with:
" Are you posting in the right repository ?" Sadly no, this belongs to Kubeflow/pipelines. We synchronize the manifests from there.
Please reopen there and close here.
@juliusvonkohout thanks, it is related to kubeflow/pipelines#9089 and There are some directions on specifying resource limits in LimitRange or in the profile itself. closed it.
Validation Checklist
Version
1.8
Describe your issue
our k8s cluster has setup resource quota per namespace, i.e. each running pods in that namespace should be specify resource.requests / resource.limits.
when our newly installed kubeflow 1.8 (and we checked the code, version after 1.8 have similar issue),
running the following example raised failed quota errors.
with the following error message:
the message suggests that default argo container (init/wait) requires resources quota too.
The above error message is gone when we patch the configmap of argo with:
We also noted that this resources was added before v1.7.0 (including v1.6 and v1.5) but was removed since this Pr #2511 https://github.com/kubeflow/manifests/pull/2511/files#diff-2fb7c70cac207a370318e3f23a14eec22bec6fba5ec87916cb5d1a2e2d8585deL42
seems like these resources are removed accidentally?
if so I would like to contribute it~
Steps to reproduce the issue
kubectl -n <namespace> describe workflow <workflow-name>
Put here any screenshots or videos (optional)
No response
The text was updated successfully, but these errors were encountered: