• 开发

  • 在修改密码和添加用户时报错

网络超时了 本地连接一下看看通不通

    6 个月 后

    kubectl delete validatingwebhookconfigurations.admissionregistration.k8s.io users.iam.kubesphere.io
    解决了 用这个就行

      valiner 检查一下对应的 webhook 为什么不通 ，不是删了admission webhook 问题就解决了，看看 pod 状态、网络都是否正常

          hongming 没有安装redis服务，只有3个打了node标签的节点和这个有关系吗

            1 年 后

            按网上提供的方案, 更改 ks-controller-manager pod hostNetwork: true 依然无法成功.

            在YAML 里更改端口为非 8080 端口无效.

            W0927 23:22:18.495218 1 client_config.go:615] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work.

            I0927 23:22:18.496499 1 server.go:202] setting up manager

            I0927 23:22:18.520026 1 deleg.go:130] controller-runtime/metrics "msg"="metrics server is starting to listen" "addr"=":8080"

            E0927 23:22:18.520266 1 deleg.go:144] controller-runtime/metrics "msg"="metrics server failed to listen. You may want to disable the metrics server or use another port if it is due to conflicts" "error"="error listening on :8080: listen tcp :8080: bind: address already in use"

            F0927 23:22:18.520279 1 server.go:207] unable to set up overall controller manager: error listening on :8080: listen tcp :8080: bind: address already in use

            issue fixed with

            1. set ks-controller-manage hostNetwork: true

            2. change node-local-dns ConfigMap, set health monitoring port to another port rather than 8080 (only if you have conflict with node-local-dns 8080 port)