telepresence –namespace kubesphere-system –also-proxy openldap.kubesphere-system.svc –swap-deployment ks-account –expose 9090:9090 –run go run ./cmd/ks-iam/apiserver.go –logtostderr=true –enable-multi-login=False –token-idle-timeout=40m –redis-url=redis://redis.kubesphere-system.svc:6379 –generate-kubeconfig=true
不报错了
T: Starting proxy with method ‘vpn-tcp’, which has the following limitations: All processes are affected, only one telepresence can
T: run per machine, and you can’t use other VPNs. You may need to add cloud hosts and headless services with –also-proxy. For a
T: full list of method limitations see https://telepresence.io/reference/methods.html
T: Volumes are rooted at $TELEPRESENCE_ROOT. See https://telepresence.io/howto/volumes.html for details.
T: Starting network proxy to cluster by swapping out Deployment ks-account with a proxy
T: Forwarding remote port 9090 to local port 9090.

T: Setup complete. Launching your command.
I0622 12:29:04.169332 19562 server.go:113] Server listening on 0.0.0.0:9090

但是管理台web无法登陆,报用户名密码错误

    你确认用户名密码无误的话,查看一下相关pod的日志

    ks-apigateway 日志
    10.233.99.12 22/Jun/2020:07:18:21 +0000 POST /kapis/iam.kubesphere.io/v1alpha2/login HTTP/1.1 200 200 86ms
    E0622 07:18:21.127107 1 authenticate.go:170] signature is invalid
    2020/06/22 07:18:21 Unauthorized,signature is invalid

    swap ks-accoount需要保证remote环境中的配置和本地一致,这里错误上看是 iam sercret 不一致,你确认一下

    谢谢,可以了
    是 secret 不对导致的

    1 个月 后

    问个弱弱的问题,我也出现了一样的问题,iam sercret不一致。。。这个该怎么解决啊-,-

    2 个月 后