### kubectl rolling-update: < v1.4.0 client vs >=v1.4.0 cluster

Old version kubectl's rolling-update command is compatible with Kubernetes 1.4 and higher only if you specify a new replication controller name. You will need to update to kubectl 1.4 or higher to use the rolling update command against a 1.4 cluster if you want to keep the original name, or you'll have to do two rolling updates.

-73.891517639160156 40.746650695800781 -73.751426696777344 40.707618713378906 1 12.43 36.5 0.5 0.5 1 0 38.5 1 1 83 122 green 0.00 0.0 0.0 58 42 8.95 1294 265 4 Queens 026500 4026500 E QN50 Elmhurst-Maspeth 4109 679 510 4 Queens 051000 4051000 I QN07 Hollis 4112 3389431 2 2014-03-22 20:57:40 2014-03-22 21:05:37 N 1 -73.891510009765625 40.746646881103516 -73.896446228027344 40.729728698730469 1 1.54 7.5 0.5 0.5 0 0 8.5 2 1 83 157 green 0.00 0.0 0.0 63 41 6.93 1294 265 4 Queens 026500 4026500 E QN50 Elmhurst-Maspeth...

  - [stable] `kubectl apply` is now able to delete resources you no longer need with `--prune` ([kubernetes/features#128](https://github.com/kubernetes/enhancements/issues/128))
  - [beta] Deployments that cannot make progress in rolling out the newest version will now indicate via the API they are blocked ([docs](http://kubernetes.io/docs/user-guide/deployments/#failed-deployment)) ([kubernetes/features#122](https://github.com/kubernetes/enhancements/issues/122))

startup probe passes (which has a 1s poll interval), # and doesn't spam the readiness endpoint too much # # If the probe is disabled, it is recommended to have delay=1s,period=2s,failureThreshold=30. # This ensures the startup is reasonable fast (polling every 2s). 1s delay is used since the startup is not often ready instantly. startupProbe: enabled: true failureThreshold: 600 # 10 minutes # Resources for the sidecar. resources: requests: cpu: 100m memory: 128Mi limits: cpu: 2000m memory: 1024Mi...