Files
kubernetes/hack
Sascha Grunert 7b9d7fd953 Propose seccomp/apparmor protobuf type definitions for CRI graduation
With the graduation of the Container Runtime Interface (CRI) we will
have a unique chance to change the protobuf protocol. We now use native
types for seccomp and AppArmor to make the API more clear and concise to
be used.

Signed-off-by: Sascha Grunert <sgrunert@suse.com>
2020-11-03 20:17:17 +01:00
..
2019-11-03 19:36:59 -05:00
2020-01-29 09:27:51 +09:00
2020-09-14 09:06:38 -04:00
2020-01-16 10:12:18 +08:00
2020-01-28 09:27:40 +09:00
2020-05-29 09:56:00 +08:00
2020-09-03 23:29:07 +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.