Files
kubernetes/hack
Patrick Ohly 4bb5fe68cc hack: use "latest" apidiff
Pinning apidiff to a specific version shouldn't be necessary because, if past
experience in klog holds true, the latest version just works. This way we don't
have to remember to bump up the revision.

The downside of using "latest" is that a compromise of that version would give
an attacker the ability to run code in the CI and on developer machines.
2024-04-23 15:03:22 +02:00
..
2021-02-28 15:17:29 -08:00
2024-01-04 21:06:52 -05:00
2024-04-23 15:03:22 +02:00
2023-02-01 16:34:23 -05:00
2024-04-23 15:03:22 +02:00
2022-06-26 09:21:05 +05:30
2022-07-08 10:46:11 +08: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.