Open zhaorendong opened 7 years ago
The rolling upgrade feature of the client should really be deprecated now - Kubernetes deployments will handle rolling upgrades for you in a much more consistent fashion.
OK,Thanks!If I don't use .withTimeout(rollingUpdateTimeout, TimeUnit.SECONDS),the rollingupate will acquiescently takes 30min,right?
When will the Kubernetes deployments apiversion from v1beta1 to v1?
That's a question for kubernetes community. Current version is quite stable though - I personally wouldn't be concerned about using it in production.
When I rollingupdate ReplicationController that used kubernetes-client 1.4.33 and kubernetes-client 2.1.0 with kubernetes1.5.1,it toke long time about 1 min to 2 min.
public ReplicationController replaceReplicationController(int clusterId, String namespace, String replicationControllerName, ReplicationController replicationController) { return getClient(clusterId).replicationControllers() .inNamespace(namespace).withName(replicationControllerName) .rolling().replace(replicationController); }