bkeadm Configuration Parameters ​

Quick Reference for Common Configuration Scenarios ​

Table 1 Quick reference for common configuration scenarios

bkeadm ​

bkeadm Command Overview ​

Table 2 bkeadm command overview configuration table

bke init Configuration Items ​

Table 3 bke init configuration items table

Note: The local system package source service corresponding to --yumRepoPort has different names in different configuration locations but is actually the same service (default port 40080):

Configuration Location	Name
bke init CLI	--yumRepoPort
Cluster CRD	spec.clusterConfig.cluster.httpRepo.port
Documentation	"HTTP repo" / "http repo" / "system package source"

Where "yum" refers to the consumer side (this service also serves as the node's yum/apt system package source), and "http" refers to the transport side (currently provides file distribution via HTTP protocol); in offline deployment, --otherSource points to this service.

Port relationships and conflict checking: --imageRepoPort, --chartRepoPort, and --yumRepoPort are used for the local image repository, chart repo, and yum/http repo respectively, and are three independent service ports. When customizing any port, you must avoid the other two ports, as well as --kubernetesPort, --consolePort, and any ports already occupied by other processes on the host. The current initialization preflight checks whether a port is already occupied on the host and filters out ports of existing BKE management containers; however, it does not explicitly check whether these parameters are filled with the same port. If configured with duplicates, the preflight may pass, but subsequent service startup or port publishing will fail. You need to adjust them to different ports based on the port occupation information in the startup logs and retry.

bke cluster Configuration Items ​

Table 4 bke cluster configuration items table

bke build and Build YAML Configuration ​

Table 5 bke build and build YAML configuration items table

bke registry Configuration Items ​

Table 6 bke registry configuration items table

Examples:

Synchronizing a Single Image ​

   bke registry sync --source docker.io/library/busybox:1.35 --target 192.168.200.240:40443/library/busybox:1.35 --multi-arch

Success criteria: The output contains Sync image docker.io/library/busybox:1.35 to 192.168.200.240:40443/library/busybox:1.35 success, indicating that the source image has been copied to the target repository; if the source image is a multi-architecture image, you may also see process logs for synchronizing architecture-specific images first, followed by manifest creation.

Exception handling: When the output contains Sync image ... failed, by registry failed, or certificate, network, or authentication-related errors, first check whether the source/target repository addresses are accessible, whether the image tag exists, and whether the repository credentials are correct; in production environments, also confirm whether you need to explicitly add --src-tls-verify=true, --dest-tls-verify=true, and whether the target repository certificate chain is trusted.

Synchronizing Multiple Images ​

   cat > image-list.txt <<'EOF'
   busybox:1.28
   alpine:3.14
   EOF

   bke registry sync --source docker.io/library -f image-list.txt --target 192.168.200.240:40443/library

Success criteria: The output displays synchronization logs per image, and finally outputs Image list sync completed: total=2, success=2, failed=0. Here total indicates the number of images in the file, success indicates the number of successfully synchronized images, and failed=0 indicates that there are no failures.

Exception handling: If failed is greater than 0, it means at least one image in the list failed to synchronize; the output will also contain the corresponding Sync image ... failed for that image. You need to check each failed image to verify whether the name:tag in image-list.txt is correct, whether the source repository has that tag, whether the target repository has write permissions, and whether the network, TLS, and authentication configurations meet the requirements.

Viewing the Image List of the Current Image Repository ​

   bke registry view 192.168.200.240:40443 --prefix kubernetes --tags 3

Success criteria: The output displays image information in a table with column headers including IMAGE, TAGS, ARCHITECTURE, CREATE TIME, and SIZE. Being able to see image names, tags, architectures, creation times, and sizes matching --prefix kubernetes indicates that repository access and manifest parsing succeeded.

Exception handling: If the output is no repositories found, it means the repository is accessible but has no images to display; if View repositories ... failed, get tags failed, unmarshal tags failed, or view failed appears, you need to check whether the repository address is accessible, whether the repository supports the Docker Registry V2 API, whether --prefix filtered out the target images, and whether the authentication and network configurations are correct.

Note:
When viewing a local self-signed image repository, do not manually prepend https:// (e.g., https://127.0.0.1:40443), otherwise system certificate verification will be triggered and may report the certificate as unauthenticated. It is recommended to omit the protocol and use 127.0.0.1:40443 directly: the tool will automatically append https:// and skip certificate verification. --export exports to {architecture}_image-list.txt based on the architecture; a custom file name cannot be specified. For more command details, see Command Reference.

Repository-Level Synchronization ​

   bke registry sync  --source 192.168.200.240:40443  --target 192.168.200.245:40443  --sync-repo

Success criteria: The output first displays the synchronization process for each image, and finally outputs Repo sync completed: total=<count>, success=<count>, failed=0 and Sync repo 192.168.200.240:40443 to 192.168.200.245:40443 success. Here failed=0 indicates that there are no failed images in this repository-level synchronization.

Exception handling: If reading the repository catalog fails, Failed to get repo catalog, Failed to unmarshal repo catalog, or No repositories found will appear; if some images fail to synchronize, Failed to sync image ... will appear, and the failure count will be reflected in the summary. In this case, first confirm that the source repository /v2/_catalog is accessible, then check each failed image for tag, architecture image suffix, target repository write permissions, repository capacity, network connectivity, and TLS/authentication configuration.

bke start Configuration Items ​

Table 7 bke start configuration items table

bke reset Configuration Items ​

Table 8 bke reset configuration items table