Removed equivalence cache tests

[akremsa]

What type of PR is this?

/kind cleanup

What this PR does / why we need it:
According to the discussion here #79600, these tests should be removed because they are not useful for the current code-base.

Does this PR introduce a user-facing change?:

NONE

/area conformance
/area test

@kubernetes/sig-architecture-pr-reviews
@kubernetes/cncf-conformance-wg
@kubernetes/sig-network-pr-reviews
@kubernetes/sig-scheduling-pr-reviews

[k8s-ci-robot]

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
• If you have done the above and are still having issues with the CLA being reported as unsigned, please log a ticket with the Linux Foundation Helpdesk: https://support.linuxfoundation.org/
• Should you encounter any issues with the Linux Foundation Helpdesk, send a message to the backup e-mail support address at: login-issues@jira.linuxfoundation.org

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. I understand the commands that are listed here.

[k8s-ci-robot]

Hi @akremsa. 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.

[k8s-ci-robot]

@akremsa: Reiterating the mentions to trigger a notification:
@kubernetes/sig-architecture-pr-reviews, @kubernetes/sig-network-pr-reviews, @kubernetes/sig-scheduling-pr-reviews

In response to this:

What type of PR is this?

/kind cleanup

What this PR does / why we need it:
According to the discussion here #79600, these tests should be removed because they are not useful for the current code-base.

Does this PR introduce a user-facing change?:

NONE

/area conformance
/area test

@kubernetes/sig-architecture-pr-reviews
@kubernetes/cncf-conformance-wg
@kubernetes/sig-network-pr-reviews
@kubernetes/sig-scheduling-pr-reviews

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.

[mgdevstack]

/ok-to-test
As there is no means to run effective E2E on kind cluster, and implementation is specific to GCE and GKE providers.

[akremsa]

/assign @johnbelamaric

[johnbelamaric]

This was discovered while trying to promote conformance tests but this isn't really a conformance PR. I also am not really the right one to approve these. So:

/remove-area conformance
/remove-sig architecture
/remove-sig network
/remove-sig testing
/priority important-longterm
/unassign
/assign @aleksandra-malinowska @k82cn

[akremsa]

@aleksandra-malinowska @bsalamat Please, review this PR in order to save an effort on regular rebasing.

[k82cn]

/lgtm

[akremsa]

@jszczepkowski @wasylkowski please review

[k8s-ci-robot]

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
• If you have done the above and are still having issues with the CLA being reported as unsigned, please log a ticket with the Linux Foundation Helpdesk: https://support.linuxfoundation.org/
• Should you encounter any issues with the Linux Foundation Helpdesk, send a message to the backup e-mail support address at: login-issues@jira.linuxfoundation.org

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. I understand the commands that are listed here.

[spiffxp]

/check-cla

[damemi]

bump, @akremsa could you please rebase this?

[ravisantoshgudimetla]

Thanks for the PR @akremsa

/lgtm
/approve

[soltysh]

The autoscaling part of the test is only adding error check which was previously missing.
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: akremsa, bsalamat, ravisantoshgudimetla, soltysh

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/autoscaling/OWNERS [soltysh]
• test/e2e/scheduling/OWNERS [bsalamat,ravisantoshgudimetla,soltysh]

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