(ci) Two tests scenarios are not working well with kubernetes 1.33 ( curl pod to check metrics is not ready )

[camilamacedo86]

What broke? What's expected?

The following tests are not passing with kubernetes 1.33

Summarizing 2 Failures:
  [FAIL] kubebuilder plugin go/v4 [It] should generate a runnable project with metrics protected by network policies
  /home/prow/go/src/sigs.k8s.io/kubebuilder/test/e2e/v4/plugin_cluster_test.go:526
  [FAIL] kubebuilder plugin go/v4 [It] should generate a runnable project with the manager running as restricted and without webhooks
  /home/prow/go/src/sigs.k8s.io/kubebuilder/test/e2e/v4/plugin_cluster_test.go:526

We need to fix them
More info: https://storage.googleapis.com/kubernetes-ci-logs/pr-logs/pull/kubernetes-sigs_kubebuilder/4850/pull-kubebuilder-e2e-k8s-1-33-0/1929446098921852928/build-log.txt

Reproducing this issue

• Uncomment the tests commented (revert changes ): 🌱 (ci): Temporarily comment out tests failing on Kubernetes 1.33 to unblock CI and allow for a calmer investigation and fix #4856
• Ensure that you have a kind version running k8s 1.33 locally
• Then, you can run the tests and debug them. Example: https://github.com/kubernetes-sigs/kubebuilder/blob/master/CONTRIBUTING.md#running-e2e-tests-locally

[mateusoliveira43]

Not related to the problem, we could pass --ginkgo.no-color=true to E2E tests running in PROW CI to help visualization of tests log (I do not know where this change should be done).

[camilamacedo86]

Hi @mateusoliveira43 feel free to push a PR with this change 👍
Thank you

[mateusoliveira43]

where should the change be applied?

[arichtman]

Hi all - thanks for the fab work. I may have a related failure. My CRD applies fine against actual 1.33.0 and 1.32.3-eks-4096722 clusters, but make test fails applying the typedresources CRD.

The error's a bit verbose so I've put it, as well as reproduction commands in a gist here

Do let me know if you'd prefer a separate issue filed and thanks again for all your work on Kubebuilder!

[camilamacedo86]

Hi @arichtman

Our scenario is. We have a pod that we run with curl to validate the metrics.
The pod created in our tests is not being deployed when NP is enabled, despite having set the restricted label on the namespace.

It is likely to be specific to our tests (kubebuilder CLI/project tests not what is scaffolded).
It does not seems to be related to your scenario.