Closed goodspark closed 3 years ago
From https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/bazelbuild_rules_k8s/636/pull-rules-k8s-e2e/1363959740941471744#1:build-log.txt%3A31
++ FAIL: 1=bazel-bin/examples/hellogrpc/go/server/staging.create $ /usr/bin/kubectl --kubeconfig= --cluster=gke_rules-k8s_us-central1-f_testing --context=gke_rules-k8s_us-central1-f_testing --user= --namespace=build-1363959740941471744 create -f - error: unable to recognize "STDIN": no matches for kind "Deployment" in version "apps/v1beta1"
And based on the version info: https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/bazelbuild_rules_k8s/636/pull-rules-k8s-e2e/1363959740941471744#1:build-log.txt%3A65
I think the test tooling inadvertently got upgraded to using kubectl 1.18+ (where the apps/v1beta1 apiVersion was removed) without updates to the tests.
apps/v1beta1
I think the fix should be just changing the various k8s libsonnet files to use up-to-date apiVersions.
From https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/bazelbuild_rules_k8s/636/pull-rules-k8s-e2e/1363959740941471744#1:build-log.txt%3A31
And based on the version info: https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/bazelbuild_rules_k8s/636/pull-rules-k8s-e2e/1363959740941471744#1:build-log.txt%3A65
I think the test tooling inadvertently got upgraded to using kubectl 1.18+ (where the
apps/v1beta1
apiVersion was removed) without updates to the tests.I think the fix should be just changing the various k8s libsonnet files to use up-to-date apiVersions.