24c8bdef44
This required some small adjustments to the produciton code to make it more feasible to test. The new test takes an existing agent pod and terminates the `sleep` process, causing the pod to go into an `Error` status. The agent controllers _should_ respond to this by deleting and recreating that failed pod, but the current code just gets stuck. This is meant to replicate the situation when a cluster is suspended and resumed, which also causes the agent pod to be in this terminal error state. Signed-off-by: Matt Moyer <moyerm@vmware.com> |
||
---|---|---|
.. | ||
cli_test.go | ||
client_test.go | ||
concierge_api_serving_certs_test.go | ||
concierge_availability_test.go | ||
concierge_credentialissuerconfig_test.go | ||
concierge_credentialrequest_test.go | ||
concierge_kubecertagent_test.go | ||
concierge_kubectl_test.go | ||
e2e_test.go | ||
kube_api_discovery_test.go | ||
kubeclient_test.go | ||
supervisor_discovery_test.go | ||
supervisor_healthz_test.go | ||
supervisor_login_test.go | ||
supervisor_secrets_test.go | ||
supervisor_storage_garbage_collection_test.go | ||
supervisor_storage_test.go | ||
supervisor_upstream_test.go |