Hi Stephan, The buildpack cache (aka "app cache," or "build artifacts cache") is a per-app cache that is stored as a tarball in the blob store and recovered when an existing app is restaged

We cut routing release 0.179.0 yesterday with a bug fix for an issue where backends were not being pruned on a TLS handshake failure potentially leading to stale routes in the routing tables, now

Thanks, Aaron. A couple of notes: The Garden Windows team has started working on contributing to the Envoy Windows support. We're betting on this as the most likely path forward for data-in-motion

Just to close on this Microsoft has confirmed that this is expected for now, using IPSec along with WinNAT is not supported in 1709, 1803, or the upcoming Windows Server 2019. They are considering it

Hi, is there documentation available that describes how the buildpack cache works? I found the following info: https://docs.cloudfoundry.org/concepts/how-applications-are-staged.html “The

FYI... Please remember to join Wednesday the Zoom call [0] June 20th at 8a Pacific for QAs, highlights, and two presentations: 1. CF Stratos UI update and demo of latest version by Neil

Hi, The CF Networking team is working towards making Polyglot service discovery GA [1]. As part of this, operators can configure their own internal domains and we envision the following 2

Hello all, Recently on the CAPI team we've been updating our BOSH jobs to run within BPM. BPM is opinionated with regards to which directories can be mounted within its containerized jobs. This means

Let us use #advocacy channel to share information on upcoming industry events, "call for paper" deadlines, and other speaking opportunities that might be of interest for y'all.

Hello cf-dev, Thanks to those who have taken the short survey; we very much appreciate your feedback. If you haven't had a chance to take the survey, please take a look and give us your feedback on

+1 We had to introduce a number of workarounds / extra book keeping to keep track for e.g. ‘system applications’, orgs belonging to the installation and not to customers, orgs requiring

Cool, that makes a lot of sense. Thanks for filling in that gap in my understanding.

Thanks for taking the time to read through it. There was no specific consideration around API similarity in general. It just seemed to make sense for this specific use case. Kube has a nice

Hi Swarna, Thanks for the email. Actually I was wondering how to edit my proposal after submitting it, I would like to add few more points. Hope you can help! Best Regards, Sara Sr. TPM | Cloud

I read through this yesterday and didn't have any specific comments to leave in-line, but I am happy to see this surface now as I know it's come up in a number of settings in the past. I also thought

Hey all, The CAPI team would like to share a proposal to apply metadata to API resources. Please have a look and add comments for any questions or

Our community has done a phenomenal job of electing the co-chairs for Summit EU in Basel. Please take a look at the co-chairs at

hi Enrique, UAA used to ship with Oracle compatibility back in 2012. Licensing issues can be overcome from a shipping standpoint since UAA only needs to ship with the JDBC library What became

Jesse, sorry for the late reply. One thing we normally add to our internal bosh releases - something that is especially useful for the control/drain scripts, but that we do almost for every single

I understand that UAA can run against MySQL and Postgres as the backend database, and Oracle was considered in the past but was discarded due to the enterprise licensing model