Files
kubernetes/hack
Danielle Lancashire 9e5fac5bb2 make: test-e2e-node: default to containerd
Since removing dockershim, `make test-e2e-node` will fail by default as
there is no provided container runtime endpoint.

This commit defaults us to using containerd's default socket path as the
local test target, rather than failing hard.
2022-02-01 16:36:06 +01:00
..
2021-02-28 15:17:29 -08: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
2022-01-10 08:14:29 -05: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
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.