thinkeng
thinkeng
我觉得，差个router 层吧 https://docs.phalcon.io/4.0/en/routing
老大 ent 版本更新一个可以跑通的呗
> This looks like a problem caused by the CNI plugin. The PR(#5196) fixed the the network issue. What version of the keadm are you using? Both v1.14.2 and v15.0...
> refer to [#5586 (comment)](https://github.com/kubeedge/kubeedge/issues/5586#issuecomment-2102583163) to set featureGates 😄 配置后部署 需要加载in-cluster conf 的时候（部署https://github.com/4paradigm/k8s-vgpu-scheduler ）， 会报下面的错误，然后 边缘节点的 node 会 NotReady 状态，cloudcore 所在的node 上没有部署 edgemesh-agent cloudcore 的错误日志如下： ``` I0515 10:58:22.649222 1 node_session.go:137]...
> CSR related clusterRoleBinding will be created when you using keadm init cloudcore and set `cloudCore.featureGates.requireAuthorization=true`. If you config the featureGates and then restart cloudcore, thie clusterRoleBinding will not be...
再问一下, 按照上面的方法开启后，配置 https://github.com/kubeedge/kubeedge/blob/master/manifests/charts/cloudcore/templates/rbac_cloudcore_feature.yaml 后，InClusterConfig 是可以获取到了，但是发现edgemesh 组网不通了，是缺少相关的权限配置，还是相互有影响？ ``` vim /etc/kubeedge/config/edgecore.yaml kind: EdgeCore featureGates: requireAuthorization: true modules: ``` https://edgemesh.netlify.app/zh/guide/edge-kube-api.html#%E9%85%8D%E7%BD%AE edgemesh 的错误日志 ``` I0516 18:43:58.206123 1 log.go:198] [INFO] 10.88.1.121:49484 - 61825 "AAAA IN...
> 3\. Enable GPU-related configurations in the edgecore configuration file. > ... > devicePluginEnabled: true > ... Enable GPU-related configurations in the edgecore configuration file. ... devicePluginEnabled: true ... 这配置需要加在那一行？
> 2\. so the pids-check-func in gpu-manager also need specially adapt 有详细一点的配置流程么？