Closed brandond closed 1 month ago
hey @bruth are you able to take a look at the CI failures here, when running the Kubernetes sig-api-machinery e2e tests against a cluster using kine+nats-embedded? It appears to be failing on some pretty basic stuff: https://github.com/kubernetes/kubernetes/blob/v1.29.4/test/e2e/apimachinery/apply.go#L248
[nats-embedded] • [FAILED] [0.397 seconds]
[nats-embedded] [sig-api-machinery] ServerSideApply [It] should work for subresources [sig-api-machinery]
[nats-embedded] k8s.io/kubernetes/test/e2e/apimachinery/apply.go:165
[nats-embedded]
[nats-embedded] Timeline >>
[nats-embedded] STEP: Creating a kubernetes client @ 05/08/24 23:35:41.137
[nats-embedded] May 8 23:35:41.137: INFO: >>> kubeConfig: /root/.kube/config
[nats-embedded] STEP: Building a namespace api object, basename apply @ 05/08/24 23:35:41.138
[nats-embedded] STEP: Waiting for a default service account to be provisioned in namespace @ 05/08/24 23:35:41.146
[nats-embedded] STEP: Waiting for kube-root-ca.crt to be provisioned in namespace @ 05/08/24 23:35:41.148
[nats-embedded] [FAILED] in [It] - k8s.io/kubernetes/test/e2e/apimachinery/apply.go:248 @ 05/08/24 23:35:41.169
[nats-embedded] << Timeline
[nats-embedded]
[nats-embedded] [FAILED] Failed to Apply Status using Apply patch: pods "test-pod" not found
[nats-embedded] In [It] at: k8s.io/kubernetes/test/e2e/apimachinery/apply.go:248 @ 05/08/24 23:35:41.169
@brandond Hey, sorry for the late response. I was traveling last week. I will take a look at it this week.
Changes: