Upgrade addons to use apps/v1 instead of extensions/v1beta1

[reegnz]

extensions/v1beta1 are deprecated and will not be served with kubernetes 1.16
anymore.

For Deployment,DaemonSet and StatefulSet the apps/v1 api has been present
since kubernetes 1.9.

See following blog post for details:
https://kubernetes.io/blog/2019/07/18/api-deprecations-in-1-16/

[k8s-ci-robot]

Hi @reegnz. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[minikube-bot]

Can one of the admins verify this patch?

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: reegnz
To complete the pull request process, please assign sharifelgamal
You can assign the PR to them by writing /assign @sharifelgamal in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[reegnz]

Also I guess this means with this change minikube plugins won't support kubernetes <1.9 anymore.

[micw523]

/ok-to-test

[tstromberg]

@minikube-bot OK to test

[tstromberg]

Looks good (assuming tests pass)

[reegnz]

Tests are failing but I don't see anything that could have been caused by these changes. :(

[medyagh]

/retest this please

[medyagh]

this seems to consistantly break all the tests for :
for

      --- FAIL: TestFunctional/group/Registry (350.72s)
            fn_addons.go:211: waiting for registry-proxy pods: timed out waiting for the condition

[reegnz]

@medyagh it turns out labelselectors were not mandatory for deployments and daemonsets in extensions/v1beta1, that's what caused the failing test case.

I adjusted the selectors in some other parts as well that don't have any test assertions present.

[tstromberg]

Looks good. Thank you!