Hi all, We are currently in the process of moving all of the Diego repositories from `cloudfoundry-incubator` to the `cloudfoundry` organization. Specifically we are moving the following repositories

Hi, You can set this property ( https://github.com/cloudfoundry-incubator/diego-release/blob/develop/jobs/stager/spec#L78-L80) on your Diego deployment to add insecure docker registries that are publi

I believe he is referring to bosh's dynamic networks: https://bosh.io/docs/networks.html#dynamic. Per another thread there seems to be an issue with metron_agent templates and dynamic networks in rece

One of the goals of V3 is that we are exposing a few internal CF concepts as domain objects in the API. Specifically droplets and packages. In V2, after you have pushed applications bits (created a pa

I have to agree with Matt on this one. I feel that the recycling of containers is a very anti-developer default. When you approach Cloud Foundry from the perspective of running production applications