knative
On-cluster build: Use unique PVC name used by a Pipeline
[UPDATE] by @zroubalik : Reasoning behind this: if for some reasons the PVC created for a function is not ready/healthy and we would like to re-create the function (or one with the same name) we won't be able to do so, because the Pipeline will fail on the PVC creation.
We can just append a random number to the PVC name, but we need to be sure that we are using the correct PVC for the function -> we need to track the generated name somewhere locally or maybe use a k8s labels to find out whether the PV for this function already exists.
This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
@zroubalik what about other ideas like func deploy --remote --force or func deploy --remote --reset where it can mimic the behavior of func delete (or part of it)? In my opinion we should avoid "producing" too many temporary resources that need to be cleaned up later because they cause e.g. high storage consumption, e.g. the default size of a pvc on AWS with the EBS volume type is 1Gi and cannot be decreased even if our default size is 256Mi.
This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.
This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.
This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.