Files
kubernetes/hack
Patrick Ohly 460f796bb7 e2e: fix ginkgo parameter setup
This is a fix for 104aab81a4: because
the default was not set for E2E_TEST_DEBUG_TOOL, all parameters were always
also passed to the E2E suite.

That wasn't wrong for the parameters so far, but breaks when using something
like --output-dir which is only understood by the CLI.
2022-12-20 07:56:27 +01:00
..
2022-02-14 10:55:35 -07:00
2022-06-21 17:33:46 +08:00
2022-06-26 09:21:05 +05:30
2022-07-08 10:46:11 +08:00
2022-12-20 07:56:27 +01:00
2022-10-10 13:43:03 -04:00
2022-10-19 17:27:25 +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.