We have fully tested the 0.28 stemcell using the vSphere CPI with the following deployments/releases and everything appears to be fully functioning: cf-deployment logsearch-boshrelease logsearch-for-c

We have been waiting for some time for a solution for route integrity support on Windows and I wanted to check on the status and compare notes on what others are doing. We are still using the Windows

Just to close on this Microsoft has confirmed that this is expected for now, using IPSec along with WinNAT is not supported in 1709, 1803, or the upcoming Windows Server 2019. They are considering it

After further testing with both the 1709 and 1803 versions of Windows Server 2016 it does appear that the WinNAT component being used by the Host Network Service in Windows does not play well with IPS

We're testing out the new Windows version and everything appears to be working correctly with the exception of traffic from the routers to the containers via the NAT on the Windows cells. The IPSec se

This one-liner will grab all the certs out of the vars files used by the bosh-cli and print out the expiration dates which is useful for a quick check: openssl crl2pkcs7 -nocrl -certfile <(sed -n '/-B

It was a theoretical concern, there isn't a specific list of activities that I have. Right now we're depending on the functionality that logs the entire NATS stream in case there is something in it th

We are currently using this component to stream all NATS activity to syslog where it is then forwarded to our common logging infrastructure. We're required to log all system activity so if this were t

We're just starting a project to migrate a CF deployment onto a different cloud platform, including moving a new blobstore cluster (Swift to Swift), and wanted to see if there are any tips on the best

I've seen more than a few references over time to poor performance of TLS termination at GoRouter vs. HAProxy - is this no longer the case? It's probably the only reason I'd be concerned about taking

I've got a few customers using the Sourcey buildpack along with Perl/Mojolicious and we've found that it is non-functional when used on Diego cells. It continues to work fine on DEA. Has anyone been s

Just checking in to make sure this isn't forgotten - any update on plans to address this in the near future? Aaron -- View this message in context: http://cf-dev.70369.x6.nabble.com/Issue-with-crashin

It's been a week, are these going to be released soon? Aaron Huber Intel Corporation -- View this message in context: http://cf-dev.70369.x6.nabble.com/v231-release-notes-tp3986.html Sent from the CF

It will totally depend on the app/buildpack. For example, the static file buildpack and PHP buildpack just launch Nginx and then host the application inside it. As soon as the web server is up it will

I understand what you're trying to avoid, I just think that is actually the normal case for the port healthchecks. Nothing on the Linux or Docker side ever touches the app so it's entirely possible it

Based on this discussion, where are we on the priority of switching the current "port" check for the Windows lifecycle back to actually be a port check? I get the impression that the changes to suppor

Just as a reference you could look at some of the connection tests that Monit allows: https://mmonit.com/monit/documentation/monit.html#CONNECTION-TESTING Obviously there are quite a few there so it m

Yes, I agree that setting the specific URI to check would be necessary as well so that developers could avoid some of the other concerns. So the ones I can think of: * URI / endpoint * Expected status

My concern is that the HTTP check (mislabeled as "port") would still be the default and I'd have to expect users to opt out of it per app. It's confusing and not what users of the platform have come t

Just to clarify as well why I think this is so important - a majority of apps on our internal platforms require authentication and will return a 401 on the root page, making them unusable on Diego for