-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
[bug] Kubeflow VolumeOp (PVC) not delete after Pipeline execution. #6649
Comments
Possible related: #3938 |
Hi @peterhaddad3121 , to GC the resources created by pipelines/sdk/python/kfp/dsl/_resource_op.py Line 104 in 5892bf9
This essentially ties the CR to the workflow and makes it to get deleted once the agent GCs the workflow. |
there is something wrong with RBAC
|
set_owner_resources needs #6622 to set the finalizers for blockowner deletion
or you get something like this
|
… (#6622) * Update view-edit-cluster-roles.yaml * Update view-edit-cluster-roles.yaml
Please close, since with #6622 merged you can set the owner references properly. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
…eflow#6649 (kubeflow#6622) * Update view-edit-cluster-roles.yaml * Update view-edit-cluster-roles.yaml
This issue has been automatically closed because it has not had recent activity. Please comment "/reopen" to reopen it. |
What steps did you take
The first step of a Pipeline is creating a VolumeOp to be attached to a couple of KF components in a Pipeline.
After the pipeline finishes and all Component pods are Completed then deleted, the PVC created does not delete.
What happened:
I edited the deployment of ml-pipeline-persistenceagent to include:
What did you expect to happen:
The PVC of the VolumeOp created to be deleted. All pods are deleted after pipeline completion, the PVC still exists and no deletion timestamp exists.
Environment:
Anything else you would like to add:
I saw all the corresponding issues, but this is related to using ArgoCD. This is using the Python SDK to run and create PIpelines.
Labels
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.
The text was updated successfully, but these errors were encountered: