Files
kubernetes/hack
Patrick Ohly 42e12c3673 apidiff: support trial builds of other projects
The intent is to check the real-world impact of an API change by
compiling controller-runtime with staging repos replaced by the
modified ones.

Such build checks must be requested explicitly with the new -b flag.
2024-10-02 16:54:49 +02:00
..
2021-02-28 15:17:29 -08:00
2024-06-26 01:07:24 +08:00
2024-09-11 15:34:37 -04:00
2023-02-01 16:34:23 -05:00
2022-07-08 10:46:11 +08:00
2023-05-11 16:43:38 +00:00
2020-01-16 10:12:18 +08:00
2020-01-28 09:27:40 +09:00
2024-09-27 22:43:28 -04:00
2024-07-22 18:09:34 +02: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.