Thanks for posting this Adam. I love the direction and improvements the Loggregator team has been working towards lately! Isolation segment support will be yet another plus. Mike

Thanks Eric for these posts. You caught us literally moments before we started updating to cf-deployment 1.16.0. Mike

So, reading through the document you provided Iryna and re-reading David's rotation steps everything now makes sense when using bosh-cli generated certs. Are there steps to do the same with credhub ma

Thanks for the clarification Iryna! I'll do some more studying and respond if I have further questions. Mike

Thanks for the heads up David. I have questions about the rotation process. Although all applications may remain up while re-deploying I imagine things like loggregator will stop working mid deploy wh

I come from more of a Java background so my answers are slanted that direction. Both options work in this case. Logging would be first choice but debugging can work also: * Logging: Most java applicat

This is some great work Shannon/Routing Team. I'm super excited for this revolution in the CF routing tier. Although I didn't actively volunteer my org for your recent call for HTTP/2 testing we may b

Yes, congratulations. Now to begin the process of moving our custom templating to cf-deployment. Sigh. :) Mike

Here is a thread from the past that might help: https://lists.cloudfoundry.org/g/cf-dev/message/4503 Mike

We do use the plan_id in the binding request. Usually to help look up credential config for parts of a service's credentials that are more static. But, we also don't have any services where updating t

This is great Stephen! I'm glad the PMs are beginning to discuss these ideas. I look forward to any proposals that may come out of the discussions. Also thanks for the ./profile tips. I'll consider th

It appears sidecars are the latest trend in the platform space and I think I'm sold. I can think of all kinds of great use cases for sidecars for my CF customers and would love to start investigating

I responded to the survey but wanted to bring up an option not presented. Why not just support every Ubuntu LTS until it is EOLed matching Ubuntu policy? Is it significantly harder to continually supp

We start with the goal of making every broker stateless. But end up making almost everyone stateful. Most of the system we integrate with using a service broker don't provide the api mechanisms necess

We migrated from Fuse to the NFS Volume release found here: https://github.com/cloudfoundry/nfs-volume-release That repo might be a good starting point to find more about Volume support in cf. Mike wr

Thanks Alexander! Mike wrote:

Thanks Dieu, these updates sent to the list are great! Mike

Thanks Matt. These are some great updates. I assume the CC will need to be updated to support this version of the spec? Has that work started? Thanks, Mike

Excellent update. It is great to start seeing v3 features becoming a reality! Mike wrote:

So, this proposal essentially documents how CF and brokers will be able to store credentials in CredHub and still provide applications with a backwards compatible VCAP_SERVICES environment variable th