Files
kubernetes/hack
Benjamin Elder 94c0ec317b Don't assign DOCKER an array in hack/lib/util.sh
DOCKER is otherwise used to be the command name (perhaps podman), but we were conflating DOCKER_OPTS in kube::util::ensure_docker_daemon_connectivity.

Split out docker opts.

This fixes shellcheck warning that docker is assigned an array and then a string in some scripts.
2022-10-19 23:46:18 -07:00
..
2021-02-28 15:17:29 -08:00
2022-10-04 08:58:46 -07:00
2022-08-07 12:01:15 +08:00
2022-02-14 10:55:35 -07:00
2022-06-21 17:33:46 +08:00
2022-06-26 09:21:05 +05:30
2022-07-08 10:46:11 +08:00
2022-05-31 08:07:37 +02:00
2022-10-10 13:43:03 -04:00
2020-11-10 14:17:17 -08:00
2021-03-07 12:51:33 -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.