Hi Dan, The scaling issues are primarily related to CF's use of Istio. Currently every Envoy sidecar in the platform receives configuration for all internal routes, regardless of whether there are C2C

Thanks to Dan from Engineer Better for prompting this update. We (the CF-Networking team) haven't reached out in a while. Last October we shared that with our integration between and CF and Istio Pilo

Members of the Routing and Container Networking teams have for some time expressed pain from broad domain surface area and challenges in context switching, overlapping objectives and challenges with c

For several years CF has supported app developers using the CF API to map routes to specific ports on their application. This eliminates the limitations that apps must listen on 8080, and that they ca

That issue could be addressed by having CFCR use a different router group, which is part of the solution we have proposed here: https://docs.google.com/document/d/1RXu-o44zxwrU5gKqsghT86hXKwgPrPpSk6-T

Kudos to the Networking team! Shannon Coen Product Manager, Cloud Foundry Pivotal, Inc.

Today the CF Routing team added the ability for an Envoy proxy deployed as the edge router for CF (using istio-release) to return a 503 instead of a 404 for a requested route when the mapped app is st

Hello Bernd, Would you please grant anyone with the link permissions to comment on these docs? Thank you. Shannon Coen Product Manager, Cloud Foundry Pivotal, Inc.

FWIW, on Feb 26th we shared more context on this initiative here: http://cf-dev.70369.x6.nabble.com/cf-dev-Additional-context-on-Istio-integration-td8408.html#a8411 https://docs.google.com/document/d/

Carlo, Just saw this feedback. Thank you very much for your response. Best, Shannon Coen Product Manager, Cloud Foundry Pivotal, Inc.

Thank you for the offer, Mike. We'll certainly reach out when we've got something you can play with. Shannon Coen Product Manager, Cloud Foundry Pivotal, Inc.

In December we shared the fact that the CF Routing team was exploring an integration with Istio Pilot and Envoy to facilitate new routing features: http://cf-dev.70369.x6.nabble.com/cf-dev-Designing-a

Hello John, See also http://cf-dev.70369.x6.nabble.com/cf-dev-Brokered-route-services-only-receiving-traffic-for-routes-mapped-to-started-apps-td4699.html The root of the issue is that because Goroute

On behalf of Eric Malm, the CF Diego team, and the CF Routing team, I am thrilled to announce three exciting improvements to Cloud Foundry, rolled up in one big shiny feature, available now using this

I should clarify that we are looking at ingress use cases initially; HTTP/2 from external clients to apps on CF. Shannon Coen Product Manager, Cloud Foundry Pivotal, Inc.

The CF Routing team has been working on a productized integration with Istio+Envoy for Cloud Foundry. One of the first features we could deliver using this integration is support for HTTP/2. We’d like

Currently routes are only known to Gorouter when they are mapped to an app AND the app has running instances. If the app is stopped or crashing, Gorouter will return a 404 for the route. This is becau

In routing-release 0.160.0 Gorouter began validating client certificates; we've received some feedback that this caused upgrade issues. These issues fall into two categories; load balancers had client

The CF Routing team proposes that routing-release [1] be promoted to an active project and moved to github.com/cloudfoundry. This probably could have been done a long time ago. These components are ru

I am stepping down as chair of the OSB API project management committee (PMC) and have nominated Alex Ley for the role. The PMC members met and confirmed the change. I will continue as a member of the