Remove kubemark 1.26 test

[serathius]

It's consistently failing and pinging scalability oncall.

cc @mborsz @jprzychodzen

[mborsz]

/lgtm
/approve

[serathius]

/assign @cici37

[cici37]

Would you mind sharing the failed job and the reason of failing as well?

We normally remove 1.26 related tests entirely after the end of support instead of deleting one job. And I believe 1.26 has reached the end of the support cycle. Maybe @xmudrii would know when it will be removed? :)

[xmudrii]

We should perhaps remove those jobs ASAP, given that 1.26 is EOL for a while now. I can look into that tomorrow. I don't have strong opinions on this PR, should be fine to proceed to avoid annoying folks, the whole file will be removed soon anyways.

[xmudrii]

We don't usually do this, but see #32628 (comment)
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mborsz, serathius, xmudrii

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:

• config/jobs/kubernetes/sig-release/OWNERS [xmudrii]

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

[k8s-ci-robot]

@serathius: Updated the job-config configmap in namespace default at cluster test-infra-trusted using the following files:

• key 1.26.yaml using file config/jobs/kubernetes/sig-release/release-branch-jobs/1.26.yaml

In response to this:

It's consistently failing and pinging scalability oncall.

cc @mborsz @jprzychodzen

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-sigs/prow repository.

[serathius]

Sure, but it's still pinging scalability, so if the release team didn't clean whole test suite, we will clean just our tests.