Way to describe dependency/definition content from kubectl

[pigmej]

Currently we can just get objects that were created using 3rd party resource. For better UX we should be able to describe them too.

This issue is not strictly bound to AppController itself, but it really improves UX of it.

It requires improvements in kubectl for 3rd party resources.

[bgrant0607]

Is there a reason why you chose to use ThirdPartyResource rather than annotations?

[pigmej]

@bgrant0607 Initially we wanted to use annotations but then we discovered that 3rd party resources are better for us. The reason is simple, to separate deps from k8s object definitions. It allows to modify deps without touching k8s object definition. It adds some complexity obviously. The more complex scenario the more natural that separation is. It also makes unified UX for existing and new objects.

[nebril]

@bgrant0607 the problem with annotations is that it requires an object to annotate. If we created a pod, it would be too late to annotate it with it's dependencies, because it would already be created and running.

[pigmej]

kubernetes/community#122