This sounds like a great solution to a very old nagging problem. I'm excited to see this issue moving forward. I assume that if the mTLS handshake fails then the router will try the next instance in

After weeks of exploration by the Routing, Networking, and Diego teams, we have a solution in mind and will begin implementation shortly. TL;DR We plan to install a proxy in every container to

Hi, Aren't space-scoped ASGs shared across all apps deployed in the same space? So if one app in a space has network access to a service, any other app in the same space would be able to reach it, at

Final reminder... see below. Zoom with us tomorrow at 8a PDT. Best, ------ dr.max ibm cloud labs silicon valley, ca maximilien.org

Garden does have (currently not very well documented) support for setting hard cpu maximums as well as the fair share limits described above. This is off by default but can be enabled via

John, management. CPU intensive applications can not affect other applications in the same space, org or cell. In the case of apps on the same cell, I would say that one CPU intensive application

I'll ask. Thanks. s.germanevtushenko(a)rakuten.com> wrote: -- Chip Childers CTO, Cloud Foundry Foundation 1.267.250.0815

Hi Dies, Due to some internal decisions, we are still in migration phase. Will it be possible to postpone the deletion of the plugin from community plugin repo? Thanks Ronak -- View this message

Hi George, Thanks! 1. So who "pay" :) when the application in CPU intensive ? if not other app in the cell ... 2. if there any documentation which can shad some additional lights on this topic it

Hey John, As Natalie mentioned before, Diego (the container scheduler) does not know about CF spaces. Diego does not treat applications in the same space differently. Further down the stack, Garden

Ok thanks, but for example does application with CPU intensive tasks can infulance on other application in the same space or even org, which mean that other application can be un-responsive during

Hi, Can anybody reach mailing list server admin and ask them to fix the hostname so that "Archived-At" has lists.cloudfoundry.org instead of localhost and (if possible) to add the same link to the

Hi community, The cf CLI team plans to discontinue support for the Diego-Enabler cf CLI plugin [1] from the end of this month. Details below. Please respond if you have any questions or

Hello Ketaki, This is a known issue. When a plan is disabled it becomes "invisible" to users. However, we don't remove existing service instances because this would break existing apps. Ideally a

There's no additional security risk, no. Diego (the container runtime engine) has no concept of spaces, so long running processes that happen to be in the same space from the Cloud Controller's

Nitin, you can always pack your own cf-release and deploy using that one. Looks like fog change was made in this

Thanks! Raunak, That's what I was thinking, so seems feature back porting isn't supported.

Suggest asking this question in the #cli channel on the cloudfoundry slack at cloudfoundry.slack.com Hope that helps! Dieu

Hi Steven, I like your tool. Just a quick question: how do you debug a plugin in cloud foundry? Thanks David

HI All, Any idea ? some reference ?