Document where to use versioned struct and where not

[discordianfish]

Hi,

I'm using client-go's NewSharedInformer to access ingresses but I'm not sure which expectedType to use.

I've started out using (k8s.io/client-go/pkg/apis/)extensions.Ingress which worked on my 1.7 clusters but another user reported their got the error expected type *extensions.Ingress, but watch event object had type *v1beta1.Ingress" component. If I use (k8s.io/client-go/pkg/apis/extensions/)v1beta1.Ingress it seems to work on all cluster but I couldn't find any authoritative information about The Right Way.

Please document which structs to use with NewSharedInformer, preferably in a way that still works when Ingress get moved out of beta.

[stibi]

FYI, I got the error also on 1.7 k8s cluster (1.7.2)

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

[discordianfish]

/remove-lifecycle stale

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[nikhita]

/remove-lifecycle stale

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[discordianfish]

/remove-lifecycle stale
/lifecycle freeze

[nikhita]

/lifecycle frozen