API Groups follow-up

[mfojtik]

This issue attemps to track all possible breakages we might/will encounter after #12986 lands.

• generate clientsets
• Make sure all controller SA have rules updated to work with API groups
• Audit all admission controllers that they deal with grouped/non-grouped resources equally and prepare migration if they don't
• Fix ImagePolicy admission to deal with both legacy and grouped resources

[mfojtik]

@sttts @liggitt @deads2k @soltysh an follow-up issue tracker for the API groups.

[soltysh]

This is super important and needs to happen within 1.6 timeframe.

[liggitt]

(and before any production pushes from origin)

[deads2k]

Needs to be done before the next push to online.

…

On Thu, Mar 16, 2017 at 8:18 AM, Maciej Szulik ***@***.***> wrote: This is super important and needs to happen within 1.6 timeframe. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#13412 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AH2BSuR4KvL93r7AKT3WICV4ZShBeh6Fks5rmSiGgaJpZM4MfFe0> .

[mfojtik]

Closing this as all follow ups seems to be adressed now.