Closed kramerul closed 4 years ago
We have created an issue in Pivotal Tracker to manage this:
https://www.pivotaltracker.com/story/show/170640405
The labels on this github issue will be updated when the story is started.
Interesting... what blobstore are you using in this quarks environment?
It bears mentioning we ourselves have never got capi-k8s-release to complete a push.
How far through the push did you get before it errored? It seems likely that it would break around the package upload endpoint (POST /v2/.../bits) because the nginx upload module is not configured in that context.
I think the present plan is to try to move away from old school buildpacks and towards cloud native buildpacks. That means building in kpack support first. We're thinking that we might be able to remove our dependency on an object store [or at least make it an optional part to support old school buildpacks] and replace it with a container registry.
We are using S3 as blobstore.
I have no idea how far the push did. When this error occurred, we gave up.
Hey @kramerul,
Given how fast some things are moving in capi-k8s-release, and this issue being related to the cf push
experience, could you share whether you are still experiencing this after updating capi-k8s-release?
in the meanwhile , we switch our deployment from kubecf
to cf-for-k8s
. cf push
is working. But we are not using an external blob store. I think, this is currently not possible with cf-for-k8s
. For the moment we are not able to reproduce this issue.
That's good to hear!
Please re-open or open a new issue if you come across other issues!
Thanks for submitting an issue to
cloud_controller_ng
. We are always trying to improve! To help us, please fill out the following template.Issue
We tried to run the cloud_controller_ng in a quarks environment using the
capi-k8s-release
. After several steps we ended up with the following problem when runningcf push
:Context
We are using the following configuration
Steps to Reproduce
capi-k8s-release
with a few changescf push
Expected result
No
Nokogiri::XML::SyntaxError
Current result
Possible Fix
[not obligatory, but suggest fixes or reasons for the bug]
name of issue
screenshot[if relevant, include a screenshot]