Files
kubernetes/hack
Patrick Ohly 808659cc42 pin-dependencies.sh: support switching repos
Sometimes it is useful to fork a dependency in a different repo and
then use that forked code in Kubernetes. Normally one would do `go mod
edit -replace ...=/local/path` but that has drawbacks:

- repos under staging are not updated
- sharing the modified Kubernetes with others is harder, for example
  in a WIP or RFC PR

The revised pin-dependencies.sh supports this with an optional
=<replacement> part in the dependency parameter.

Determining the revision upfront with `go mod download` also makes the
script simpler.
2021-08-09 16:54:30 +02:00
..
2021-03-07 15:27:45 -08:00
2021-02-28 15:17:29 -08:00
2021-07-14 08:53:33 -04: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-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.