Authentication was removed from /healthz in 2013 apparently (and the Gorouter README wasn't updated). I just discovered last week that the healthcheck endpoint doesn't require auth. We'll add

Those sound useful. I'll have to look into re-enabling the health check. We removed it because we were having some trouble with the authentication of the status endpoint from our custom health

I have a question about the SSL termination epic[1], whose goal IIUC is to provide the ability for operators to have multiple TLS certificates: it seems only shared domains are being considered

I figured that we can set different admin password in 'oauth-clients.xml'. With this approach, I can pretty much use APIs to create new clients and further oAuth related operations. Thanks

Thanks for the feedback, Mike. Do you recall what kind of problems you had with the /heathz endpoint? Here's few enhancements we've made recently that are healthcheck-related, and eliminate

We used to use the /healthz path but ran into some problems with it. We eventually decided to stop using this endpoint and instead simply check to see if gorouter is listening on 80. It was unclear

Hi Madhura, Thanks for the response. But to use that API we need admin bearer access token which essentially requires that admin user be created. So my question is how do I start provisioning such

For a very long time, the /healthz endpoint has been documented as deprecated. The recommended method of healthchecking Gorouter has been to send a User-Agent http header. We recently merged a PR

Hello all, We would like to share the official End of Life timeline for the DEA backend in Cloud Foundry. Details can be found here [1] or in the attached pdf. At a high level, the plan is to

Hi Yogesh, You can add users directly via the API. Here is the documentation for the API: http://docs.cloudfoundry.org/api/uaa/#create61 Madhura

Hi, I am planning to use UAA to implement SSO for my java based micro services. Our infrastructure does not let me use any other tools (like ruby based tools like uaac or cf) apart from java based. Is

Hi Vinod, Yes, it is supported. Firehose pulls log data from loggregator, Cloud Foundry's logging subsystem. I recommend logsearch (http://www.logsearch.io/) with an extension for Cloud Foundry

Thanks for quick response, Michael. But I am using DEA CF 235 only. Is this supported on non-Diego version of CF ? Regards, Vinod wrote:

Hi Vinod, You can't do this using this approach indeed but Cloud Foundry provides the Firehose component with all logs from all applications as a stream you can use to feed you ELK stack. The easiest

Hi All, We are redirecting the application logs to ELK system from Cloud Foundry deployment. The issue is : we have to create a user provided service instance in each space of each user's org to

Hello Nick, Thank you for your kind response. I've made up a collection of information related behaviors with

Two small corrections to the above note: - The latest version of the installer and binary is 6.21.1 - The Windows binary and installer did not require re-signing to rotate the

Thanks, that was super helpful. On a similar project, I overcame some of the difficulties you described with a small shell script and use of `jq`. Essentially one got around the i18n4go problem by

Hello! The CF CLI team has recently been asked about where to find any information regarding CF CLI plugin development. Here are a few pointers to help you along: 1. If you'd like an example on HOW

The workflow is available here: https://github.com/cloudfoundry/cli/blob/master/CONTRIBUTING.md#i18n i18n4go, goi18n, bin/generate-language-resources are the three things that need to be executed