This repository has been archived by the owner on Feb 14, 2023. It is now read-only.
cf-for-k8s deployed locally - buildpack creation fails 413 Payload Too Large/Request Entity Too Large; Error unmarshalling the following into a cloud controller error #634
Labels
Hi CF community!
Describe the bug
I came up with an idea to deploy cf-for-k8s using minikube on WSL2 - Ubuntu 20.04.1 LTS (Focal Fossa).
https://github.com/cloudfoundry/cf-for-k8s/blob/develop/docs/deploy-local.md#steps-to-deploy-on-minikube
After deployment, any cf command resulted in a timeout. So I decided to use 127.0.0.1 instead and this worked fine.
so I did some research around and found out a solution for this by applying envoy filter for istio ingress:
https://stackoverflow.com/questions/61439893/istio-how-to-use-envoyfilter-to-change-max-request-bytes-of-envoy-sidecar
since then, it started to fail with another error:
..so far I am stuck. Anyone knows if this can be handled by any other filter?
Something's also wrong with local buildpacks "store". After all those failures, it leaves some metadata which can't be deleted nor recreated. It says the buildpack already exists but can't be deleted or listed using cf buildpacks.
///
update: seems like buildpack record gets created and it's in 'AWAITING' status for the file upload
..disappears if not provided in a short period of time.
///
What's also weird. Buildpack creation says 'OK' and error appears afterwards. This part of comment also contains the command I use to create the buildpack.
Expected behavior
My current goal is to create a buildpack and push IBM's test app. However, buildpack creation fails.
buildpack: https://github.com/cloudfoundry/ibm-websphere-liberty-buildpack
app: https://github.com/IBM-Cloud/get-started-java
Cluster information
local minikube using WSL2
CLI versions
paste output of the following commands
ytt --version
: ytt version 0.31.0kapp --version
: kapp version 0.35.0kubectl version
: v1.19.3cf version
: cf version 7.2.0+be4a5ce2b.2020-12-10The text was updated successfully, but these errors were encountered: