kubernetes: Kubectl skew tests are failing

Which jobs are failing:

• ci-kubernetes-e2e-gce-new-master-gci-kubectl-skew
• ci-kubernetes-e2e-gce-stable1-beta-gci-kubectl-skew

https://storage.googleapis.com/k8s-gubernator/triage/index.html?text=Kubectl&job=skew

Which test(s) are failing:

Steadily failing tests making signal from the skew jobs unusable:

• [sig-cli] Kubectl client Kubectl rolling-update should support rolling-update to same image [Conformance]
• [sig-cli] Kubectl client Kubectl run rc should create an rc from an image [Conformance]
• [sig-cli] Kubectl alpha client Kubectl run CronJob should create a CronJob
• [sig-cli] Kubectl client Kubectl run deployment should create a deployment from an image [Conformance]
• [sig-cli] Kubectl client Kubectl run job should create a job from an image when restart is OnFailure [Conformance]
• [sig-cli] Kubectl client Kubectl run default should create an rc or deployment from an image [Conformance]
• [sig-cli] Kubectl client Simple pod should support inline execution and attach
• [sig-cli] Kubectl client Update Demo should do a rolling update of a replication controller [Conformance]
• [sig-cli] Kubectl client Simple pod should return command exit codes

Flaking tests:

• [sig-cli] Kubectl client Guestbook application should create and stop a working application [Conformance]
• [sig-cli] Kubectl client Kubectl replace should update a single-container pod's image [Conformance]
• [sig-cli] Kubectl client Kubectl patch should add annotations for pods in rc [Conformance]
• [sig-cli] Kubectl client Simple pod should support port-forward
• [sig-cli] Kubectl client Kubectl client-side validation should create/apply a CR with unknown fields for CRD with no validation schema
• [sig-cli] Kubectl client Kubectl client-side validation should create/apply a valid CR for CRD with validation schema

Testgrid link:

Reason for failure:

Anything else we need to know:

The skew jobs are what tell us if we’ve broken compatibility with prior kubectl releases. I’m surprised they aren’t considered release blocking, but they should be a high priority for sig-cli to fix regardless.

/sig cli /priority critical-urgent /cc @soltysh @seans3