Files
kubernetes/hack
Ed Bartosh 81b6e1d3a3 local-up-cluster: start containerd before Docker
Configure and start containerd before starting Docker, ensuring that
Docker detects and uses the running containerd instance instead of
launching its own. This allows us to customize containerd’s
configuration, such as enabling CDI support, which is not possible when
Docker manages containerd itself.

Set root and state paths for containerd to make it working the same way
as when Docker runs it.
2025-07-10 15:30:56 +02:00
..
2021-02-28 15:17:29 -08:00
2025-07-04 08:55:57 +02:00
2025-07-04 08:55:57 +02:00
2023-02-01 16:34:23 -05:00
2022-07-08 10:46:11 +08:00
2025-06-10 20:05:40 -07: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.