Files
kubernetes/hack
Davanum Srinivas 1168b11875 Stabilize local-up-cluster in our CI
- if binaries are already present skip building them
- install missing packages like nftables and kmod
- work better when cgroups v2 is present
- update to newer CNI version (v1.2.0)
- Ensure we wait for coredns to stabilize
- Grab docker log as well (this has containerd logs too)

Used tips from:
- https://kubernetes.io/docs/tasks/administer-cluster/dns-debugging-resolution/

Tested locally in an environment as close to CI as possible:
- https://gist.github.com/dims/3c83730c99f61e36b8dd2d61abe68fe7

Signed-off-by: Davanum Srinivas <davanum@gmail.com>
2023-05-12 09:16:19 -04:00
..
2021-02-28 15:17:29 -08:00
2023-03-30 20:26:07 -04:00
2023-02-01 16:34:23 -05:00
2022-06-26 09:21:05 +05:30
2022-07-08 10:46:11 +08:00
2023-01-22 15:16:23 -08:00
2023-04-21 16:15:21 -07:00
2022-10-19 17:27:25 +00:00
2023-01-12 11:20:41 +08:00
2021-03-07 12:51:33 -08:00
2023-01-12 11:20:41 +08: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.