In order to enforce that all traffic is encrypted and delivered over gRPC going forward the Loggregator team will be removing the UDP endpoint and associated properties from Doppler. This change also

What is the hostname you are trying to access from outside? And are you getting connection refused or 502 bad gateway? If connection refused then it is network routing issue if 502 it is very likely

Thanks

Great work, team CF CLI! We've updated the ECS Team CF CLI quick reference guide [1] to include the new Isolation Segments commands. Also, the latest version of the "cf top" CLI plugin [2] will

Fantastic work! Thank you! 2017-04-07 17:35 GMT-03:00 Dieu Cao <dcao(a)pivotal.io>: -- Mis mejores deseos, Best wishes, Meilleurs vœux, Juan

Great release! Super excited about this release with Isolation Segment support! wrote:

I have created the new security group cf security-group private-network Getting info for security group private-network as admin OK Name private-network Rules [ { "destination":

--health-check-type none is misleading and the none value is deprecated in favor of the type 'process' The none/process health check types will check if the process is alive and instance is restarted

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