Hi, does anyone know what is the right approach to remove unnecessary cache in these places? I've already removed unused deployments and releases but the size in the following folders are still quite

Hi Zach, thanks for the feedback. Nevertheless, using "--health-check-type none" option sounds like a bit of hackish workaround? Is CF going to support monitoring for this kind of processes like

For updating ASG, you don't need to run 'bosh deploy' https://docs.cloudfoundry.org/adminguide/app-sec-groups.html#updating-groups You can use this tool to generate the rules from

The CF CLI team just cut 6.26.0. Deb, yum and Homebrew repos have been updated; binaries, installers and link to release notes are available

Hi, I have changed the range of security group for public_networks in cf-release/bosh-lite/deployments/cf.yml - name: public_networks rules: - destination: 0.0.0.0-9.255.255.255

Yes, that is supported using the "--health-check-type none" option for cf push that Leandro mentioned. -Zach

CAPI has been continuing the work to secure internal traffic with CAPI VMs [1]. Next on the list of jobs that now need certs is CC-Uploader. CC-Uploader's purpose is to manage blobstore upload

This is a real problem that we face in some of our apps as well. We’ve addressed it with the app environment variable configuration to tell the purpose of each service instance. Such approach works,

By default, bosh-lite is configured to use ASG if I'm not wrong as I couldn't get "cf allow-access ..." as a registered command. You will need to configure the network to allow proper egress to your

I have installed the vagrant and didn't make any change in the network configuration by myself. $./bin/add-route + old_ips=10.244.0.0/19 + ips=10.244.0.0/16 + gw=192.168.50.4 + echo 'Adding the

Hi Zach, I saw this "Experimental - Applications consisting of several processes via a Procfile" but is this a worker process feature for web app to achieve multi-process backend? What I'm looking

AFAIK, all *.bosh-lite.com resolves to 10.244.0.34 Did you setup via vagrant or manually? There scripts within the VM itself that will add iptables rules to route traffic to proper interface for

I'm pleased to announce that haproxy-boshrelease has been accepted for incubation into the Runtime PMC! Geoff Franks will be serving as the project lead. Will work with Geoff on the

The Routing and Diego teams are starting to think about how to avoid pruning routes after two minutes when there's a failure with NATS or a network partition between Emitters, NATS, and Routers, while

Hi Teo, Thanks for the reply. I have changed the code, Now application code is not handling any thread by itself Now getting the error 502 Bad Gateway: Registered endpoint failed to handle the

Support for Procfiles is currently being added to Cloud Foundry. It is part of the V3 API, which are experimental at the moment, docs here: http://v3-apidocs.cloudfoundry.org/ You can follow

The Loggregator team has seen an increase in the rate of `doppler.shedEnvelopes` and `doppler.dropped` metrics starting in the CF253[1] deployment. The doppler.dropped increase has been attributed to

Great, thanks a lot Leandro.

If you need to run cron tasks you have several alternatives like: - https://docs.run.pivotal.io/marketplace/services/temporize.html - https://github.com/18F/cg-cron -

Hi, it seems the CF only support 'web' process type as of now? I couldn't find much information about this in CF