Files
kubernetes/hack
Patrick Ohly 0b5456c13b hack/verify-e2e-suites.sh: non-zero exit code when there were errors
The script correctly reported errors, but did not return a non-zero exit
code. Therefore errors would have been overlooked during pull-kubernetes-verify
runs.
2024-04-17 19:35:22 +02:00
..
2024-01-04 21:06:52 -05:00
2024-02-29 00:22:06 -08:00
2023-02-01 16:34:23 -05:00
2023-05-31 12:53:11 +03:00
2023-05-11 16:43:38 +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.