hanweisen

/assign

In addatation, when **op has no ResourceSelectors**, we create deployment first, then create pp, finally we create op. op will take effect. At this time we modify op, The new...

I had the same problem in multicluster. Even you use member cluster console create user you can not login from member cluster. I created 3 cluster and use one node...

I can not login console but I can access member cluster with command like this `curl -u 'username:password' ip:port/kapis/resources.kubesphere.io/v1alpha3/statefulsets`

Is this issue intentionally designed this way, or is it a bug?. If it's a bug I'd like to try to fix it @FeynmanZhou

This problem can resolve by add some line in member cluster's configmap kubesphere-config and restart ks-apiserver ``` authentication: oauthOptions: accessTokenMaxAge: 0 clients: - name: kubesphere secret: kubesphere redirectURIs: - '*'...

This is a ks-install problem, I create a pull request https://github.com/kubesphere/ks-installer/pull/1932

I suggest we use *-storage for module name, repository name and image name, use * as the plugin registration name without "-storage".