Currently the e2e's running in this repo are not installing experimental CRDs onto a K8s cluster which means new changes going in -> which by default are to the experimental channel are not getting tested.
@tssurya: The label(s) area/ci cannot be applied, because the repository doesn't have them.
In response to [this](https://github.com/kubernetes-sigs/network-policy-api/issues/192#issuecomment-1943370410):
>/area ci
Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
Describe the issue:
Currently the e2e's running in this repo are not installing experimental CRDs onto a K8s cluster which means new changes going in -> which by default are to the experimental channel are not getting tested.
See https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_network-policy-api/185/pull-network-policy-api-crd-e2e/1757506183540772864
We should fix this and change
crd-e2e.sh
to install both channelsAlso CI is running 1.25 kube which is so old, we should be testing against latest kube-apiserver, change that too