kubernetes (update-demo-page)$ kubectl describe deployment/update-demo
Name:
Namespace:
CreationTimestamp:
Labels:
Selector:
Replicas:
StrategyType:
MinReadySeconds:
RollingUpdateStrategy:
OldReplicasets:
NewReplicaset:
Events:
FirstSeen
52m
44m
44m
5m
5m
49m
16s
16s
44m
15s
15s
11s
update-deno
default
Tue, 22 Mar 2016 13:37:39 -0700
name=update-demo
name=update-demo
4 updated | 4 total | 4 available | 0 unavailable
RollingUpdate
8
1 max unavailable, 1 max surge
<none>
update-demo-3583349194 (4/4 replicas created)
LastSeen
52m
44m
44m
5m
5m
5m
16s
16s
16s
15s
15s
11s
Count From
1
1
1
1
1
2
1
1
2
1
1
1
{deployment-controller }
{deployment-controller}
{deployment-controller}
{deployment-controller }
{deployment-controller}
{deployment-controller }
{deployment-controller }
{deployment-controller }
{deployment-controller }
{deployment-controller }
{deployment-controller }
{deployment-controller}
SubobjectPath Type
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Reason
ScalingReplicaset
ScalingReplicaset
ScalingReplicaset
ScalingReplicaset
DeploymentRollback
ScalingReplicaset
ScalingReplicaset
ScalingReplicaset
ScalingReplicaset
ScalingReplicaset
ScalingReplicaset
ScalingReplicaset
Message
Scaled up replica set update-demo-3459158784 to 1
Scaled up replica set update-demo-1326485872 to 2
Scaled up replica set update-demo-1326485872 το 1
Scaled down replica set update-demo-1326485872 το ο
Rolled back deployment "update-demo" to revision 1
Scaled up replica set update-demo-3459158784 το 4
Scaled up replica set update-demo-3583349194 to 1
Scaled up replica set update-demo-3583349194 to 2
Scaled down replica set update-demo-3459158704 το 3
Scaled down replica set update-demo-3459158764 το 1
Scaled up replica set update-demo-3583349194 το 4
Scaled down replica set update-demo-3459158784 το θ
Explanation
This image shows the output of the `kubectl describe deployment/update-demo` command. The command returns information about the update-demo deployment in the default namespace. The output shows that the deployment is using a RollingUpdate strategy and has 4 replicas. The events section shows the scaling and rollback events that have occurred for the deployment.