3 ms·

One of the features of their stack is live single-click or even auto-update of you technology stack while your application keeps running. While that doesn't nec

One of the features of their stack is live single-click or even auto-update of you technology stack while your application keeps running. While that doesn't necessarily mean that you will keep your stack up-to-date, it makes patching security issues considerably easier and less painful, which means it's far less likely that you will be running a known-vulnerable version. So it's not entirely BS, even though why CoreOS helps security isn't spelled out here. I happen to have watched a talk where Alex Polvi did spell this out just last night, which is the only reason I know this. But yes, the rhetoric is a bit heavy-handed.

oso2k 9y ago
This is built-in functionality of Kubernetes (& OpenShift) called Rolling Update [0]/Rolling Deployments [1] and Image Triggers [2]. [0] https://kubernetes.io/docs/tasks/run-application/rolling-update-replication-controller/ https://kubernetes.io/docs/tasks/run-application/rolling-upd... [1] https://docs.openshift.com/container-platform/3.6/dev_guide/deployments/deployment_strategies.html#rolling-strategy https://docs.openshift.com/container-platform/3.6/dev_guide/... [2] https://docs.openshift.com/container-platform/3.6/dev_guide/builds/triggering_builds.html#image-change-triggers https://docs.openshift.com/container-platform/3.6/dev_guide/...