Remove an e2e test specific to kubeup clusters - Part Two

[upodroid]

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

addon-manager has been deprecated for a long time and we should stop testing it. This is not available in kops.

Should fix this failing test https://testgrid.k8s.io/sig-cluster-lifecycle-kubeup-to-kops#ci-kubernetes-e2e-cos-gce-slow-canary&include-filter-by-regex=Addon.update

The docs at kubernetes.io no longer mention addon-manager or how to install it.

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

kubernetes/enhancements#4224

[k8s-ci-robot]

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

[upodroid]

/cc @aojea @hakman @dims

[hakman]

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 68014b7898c67b900121992ab7804ed8a3d3fd96

[hakman]

/assign @justinsb

[aojea]

/assign @BenTheElder

he has more historical context here

[upodroid]

/retest

[justinsb]

I suppose the challenge is that for the other kube-up tests, they still use the addon manager (kube-up is the only thing AFAIK). So if we broke the addon manager, we would know because the remaining kube-up tests would break. If this was the last kube-up test, 100% agreed. But we aren't really gaining anything from this test, other than maybe a bit more clarity if someone breaks the addon manager in the way this test verifies, so ....

/lgtm

[aojea]

/approve

the nice thing with git is that we can always revert it XD

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aojea, upodroid

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

The pull request process is described here

Needs approval from an approver in each of these files:

• test/e2e/cloud/gcp/OWNERS [aojea]

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