asianux

能否提供config.yaml配置的详细示例

2

### Your current KubeKey version _No response_ ### Describe this feature config-sample.yaml中的配置示例比较简单，对于etcd、container、kubelet、ingress、cilium、hubble等等这些集群组件的参数需要调整。 能否提供集群核心组件如何在config-sample.yaml 中如何定义参数的详细说明文档。 另外registry.cn-beijing.aliyuncs.com/kubesphereio/cilium:v1.11.7 镜像没有。 ### Describe the solution you'd like 希望能提供集群核心组件配置参数的样例说明 ### Additional information _No response_

kubekey 3.1.9 部署双栈集群，执行至添加节点时报token.go:223] [discovery] The cluster-info ConfigMap does not yet contain a JWS signature for token ID "xxx", will try again

2

### What is version of KubeKey has the issue? 3.1.9 ### What is your os environment? kylin v10sp3 ### KubeKey config file ```yaml apiVersion: kubekey.kubesphere.io/v1alpha2 kind: Cluster metadata: name: cluster-local...

新添加节点containerd服务没有读取/etc/containerd/config.toml里sandbox_image，而是依然下载registry.k8s.io/pause:3.8

2

openeuler 24.03 sp1 kubekey 3.1.9 1、containerd的配置/etc/containerd/config.toml里sandbox_image已经替换为registry.aliyuncs.com/google_containers/pause:3.9。 2、执行新添加节点执行过程没有报错，但是新添加节点pod一直处于pending状态。 3、排查新节点containerd服务报level=error msg="RunPodSandbox for &PodSandboxMetadata{Name:haproxy-worker-2,Namespace:kube-system,Attempt:0,} failed, error" error="failed to get sandbox image "registry.k8s.io/pause:3.8": failed to pull image "registry.k8s.io/pause:3.8": failed to pull and unpack image...

**What would you like to be added**: Add native support for Ascend 910B4-1 GPU in HAMi (Hybrid AI Management Interface), including device discovery, resource monitoring, job scheduling optimization, and compatibility...