mirror of
https://github.com/k3s-io/kubernetes.git
synced 2025-12-24 04:17:30 +00:00
4bb5fe68cc
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.
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 tomake verify.update-all.sh: This script is a vestigial redirection, Please do not add "real" logic. Thetruetarget of this makerule ishack/make-rules/update.sh.It is equivalent tomake 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.