Files
kubernetes/hack
Clayton Coleman 2d361d4306 e2e: Flag questionable durations in container status on termination
The e2e that create/deletes pods rapidly and verifies their status
was reporting a very long timing:

timings total=12.211347385s t=491ms run=2s execute=450402h8m25s

in a few scenarios. Add error checks that clarify when this happens
and why. Report p50/75/90/99 latencies on teardown as observed from
the test for baseline for future changes.
2021-05-24 11:48:42 -04:00
..
2021-03-07 15:27:45 -08:00
2021-02-28 15:17:29 -08:00
2021-02-28 15:17:29 -08:00
2021-03-07 13:10:43 -08:00
2021-03-09 10:29:11 -05:00
2019-02-22 10:00:10 -08:00
2019-01-22 08:39:55 +08:00
2019-01-22 08:39:55 +08:00
2020-01-29 09:27:51 +09:00
2020-09-14 09:06:38 -04:00
2020-01-16 10:12:18 +08:00
2020-01-28 09:27:40 +09:00
2020-05-29 09:56:00 +08:00
2021-04-30 07:59:19 -07:00
2020-11-10 14:17:17 -08:00
2021-03-07 12:51:33 -08:00
2020-09-03 23:29:07 +00:00

Kubernetes hack GuideLines

This document describes how you can use the scripts from hack directory and gives a brief introduction and explanation of these scripts.

Overview

The hack directory contains many scripts that ensure continuous development of kubernetes, enhance the robustness of the code, improve development efficiency, etc. The explanations and descriptions of these scripts are helpful for contributors. For details, refer to the following guidelines.

Key scripts

  • verify-all.sh: This script is a vestigial redirection, Please do not add "real" logic. It is equivalent to make verify.
  • update-all.sh: This script is a vestigial redirection, Please do not add "real" logic. The true target of this makerule is hack/make-rules/update.sh.It is equivalent to make update.

Attention

Note that all scripts must be run from the Kubernetes root directory. We should run hack/verify-all.sh before submitting a PR and if anything fails run hack/update-all.sh.