Tyler Phelan
Tyler Phelan
@showpune Thank you for this issue! I'm curious, have you tried scaling the resource requests and limits for the `kpack-controller` deployment? Does it mitigate the problem at all?
Thanks again for this issue. I think this is a relevant use case and problem. This would require a drastic change to the kpack installation and api which we will...
@tsusadivyago Does the [full paketo stack](https://github.com/paketo-buildpacks/bionic-full-stack) fit your use case? It contains wget, curl, and git. Besides the curated [stacks from paketo](https://github.com/paketo-buildpacks/stacks), your best bet is a [custom buildpack](https://buildpacks.io/docs/buildpack-author-guide/) or...
please re-open the issue if you have questions!
Thank you for this issue and ideas! We have thought about this and want to add this behavior: https://github.com/pivotal/kpack/issues/514 We should use this issue to track. Closing the other.
how should modifying the image resource's storage class name work? The risk I see is differentiating between these two scenarios: - There is an existing image with the storage class...
@matthewmcnew the field is immutable for pvc's so it fails to update via a validation failure
>Shouldn't the kpack image do the same to prevent modification of the storage class? I think it's a good idea.
Note on deliverable: - We should ensure that ClusterStores and ClusterStacks are resilient to transient network errors as well
Is exponential backoff a good idea here?