Disable ListFromCacheSnapshot in ci-kubernetes-network-kind-alpha-beta-features

[serathius]

/assign @wojtek-t @aojea

Fixes kubernetes/kubernetes#131011

[aojea]

we don't want different cluster behaviors depending on which features are enabled, the goal of this jobs is to ensure our cluster behavior is consistent

/hold

[aojea]

also, this is going to be enabled in more jobs, I don't like the idea of start modifying all the jobs, can we think in a better solution before trying this?

[serathius]

I think just disabling an alpha feature is better than changing conformance test during code freeze.

[aojea]

then please add a comment explaining this and a TODO , we should fix this in 1.34

Please also modify these jobs #34584 , I've realized we were not running these tests on release informing and we missed this

/hold cancel

[aojea]

@serathius disable the test, not the feature

Servers with support for API chunking should support continue listing from the last key if the original version has been compacted away, though the list is inconsistent 

[aojea]

# ListFromCacheSnapshot does not implement the Conformance behavior defined in this test so it flakes
# Ref: https://issues.k8s.io/131011
- name: SKIP
  value: "Servers.with.support.for.API.chunking.should.support.continue.listing.from.the.last.key.if.the.original.version has.been.compacted.away"

[serathius]

Thanks.

[aojea]

/lgtm
/approve

Thanks, I notice we have some inconsistencies in the regex but that is for later for me

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

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

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• config/OWNERS [aojea]

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 sig-network-kind.yaml using file config/jobs/kubernetes/sig-network/sig-network-kind.yaml
• key kubernetes-kind.yaml using file config/jobs/kubernetes/sig-testing/kubernetes-kind.yaml

Details

In response to this:

/assign @wojtek-t @aojea

Fixes kubernetes/kubernetes#131011

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.

[BenTheElder]

We need to make sure when we do this that we have a tracking issue and active discussion about driving resolution, we cannot leave permanently disabling conformance features, this is a risk for graduating features and defeats the purpose of ensuring that alpha/beta features do not break stable APIs / conformance by way of running these jobs.

kubernetes/kubernetes#131011 (comment)