Deployment status

[bgrant0607]

Status:

• Number of pods of each version
• Number ready/not ready (should add to RC also)

cc @nikhiljindal @janetkuo @ironcladlou @ncdc

[bgrant0607]

And we still need to add a /status subresource.
https://github.com/kubernetes/kubernetes/blob/master/pkg/master/master.go

[0xmichalis]

And we still need to add a /status subresource.

There is already one

kubernetes/pkg/master/master.go

Line 610 in 912e54e

storage["deployments/status"] = deploymentStorage.Status

kubernetes/pkg/registry/deployment/etcd/etcd.go

Lines 104 to 116 in 912e54e

	// StatusREST implements the REST endpoint for changing the status of a deployment
	type StatusREST struct {
	store *etcdgeneric.Etcd
	}
	func (r *StatusREST) New() runtime.Object {
	return &extensions.Deployment{}
	}
	// Update alters the status subset of an object.
	func (r *StatusREST) Update(ctx api.Context, obj runtime.Object) (runtime.Object, bool, error) {
	return r.store.Update(ctx, obj)
	}

[0xmichalis]

Why do we need to have the number of each version in the deployment status?

[bgrant0607]

@Kargakis I agree that the number of pods of the latest revision is good enough, at least for now.

We also have available/unavailable.

We can make changes or add more based on user feedback.

Closing.