Patrick Ohly 0bd901afea e2e framework: better error messages when pod has failed or completed ...

Getting a message about "pod ran to completion" is confusing when the pod
hasn't been able to start at all. The failed state now has a different message.

To address the previous ambiguity, the success state is described as "ran to
completion successfully".

2022-09-16 09:12:51 +02:00

..

cmd

Merge pull request #111093 from brianpursley/k-110097

2022-08-24 07:42:03 -07:00

conformance

Fix 1.17 to 1.7

2022-09-14 09:14:28 +12:00

e2e

e2e framework: better error messages when pod has failed or completed

2022-09-16 09:12:51 +02:00

e2e_kubeadm

Custom reporter of Junit report is no longer needed

2022-07-08 10:46:11 +08:00

e2e_node

Revert "promote LocalStorageCapacityIsolationFSQuotaMonitoring to beta"

2022-08-26 16:25:00 -05:00

fixtures

Switching everything to use pause:3.8

2022-07-21 14:53:15 -07:00

fuzz

hack/update-bazel.sh

2021-02-28 15:17:29 -08:00

images

Update Go version in test Makefile to 1.19.1

2022-09-07 22:13:58 +05:30

instrumentation

clean-up apiserver metrics and use subsystem

2022-07-29 12:51:32 -07:00

integration

Feat: unify the status handle when return in bindingCycle (#112103)

2022-09-09 08:31:23 -07:00

kubemark

Move from k8s.gcr.io to registry.k8s.io

2022-05-31 10:16:53 -04:00

list

Remove KubeDescribe

2021-03-04 07:54:53 +01:00

soak/serve_hostnames

fix typos

2022-06-15 13:38:48 +09:00

typecheck

Check in OWNERS modified by update-yamlfmt.sh

2021-12-09 21:31:26 -05:00

utils

e2e: reduce built time for framework

2022-09-10 17:56:23 +02:00

OWNERS

OWNERS cleanup - Jan 2021 Week 1

2022-01-10 08:14:29 -05:00