Good talk. Couple of comments. "Greater freedom and control over infrastructure bindings, network designs" Depending on the level of granularity you need, this can also be achieved via isolation segments in CF. The overhead of doing so is probably not worth it if you are talking about segmenting by team or product, but if you want to segment by a particular multi-team function or aggregation of closely-related applications, it would work just fine. Also, 1 of the key reasons for using Kubernetes alongside CF is for vendored applications that come pre-packaged/configured as a container. Most off-the-shelf solutions we buy and use won't come packaged as code, buildpack, and instructions for setting up a database.
Very clear simple and detailed explanations.
Thanks Sanjay.
I like the way he make jokes to keep things simple
Instablaster.
clear talk. thank you!
Good talk.
Couple of comments.
"Greater freedom and control over infrastructure bindings, network designs"
Depending on the level of granularity you need, this can also be achieved via isolation segments in CF. The overhead of doing so is probably not worth it if you are talking about segmenting by team or product, but if you want to segment by a particular multi-team function or aggregation of closely-related applications, it would work just fine.
Also, 1 of the key reasons for using Kubernetes alongside CF is for vendored applications that come pre-packaged/configured as a container. Most off-the-shelf solutions we buy and use won't come packaged as code, buildpack, and instructions for setting up a database.