Rick
Please take the following steps: * run command `ks -n kubesphere-system edit cm kubesphere-config` then change `authentication.multipleLogin` to true * restart ks-apiserver
Below is an example of docker registry as secret in KubeSphere project: ``` apiVersion: v1 data: .dockerconfigjson: eyJhdXRocyI6eyJodHRwczovL2RvY2tlci5pbyI6eyJ1c2VybmFtZSI6InN1cmVucGkiLCJwYXNzd29yZCI6IjEyMzQ1NiIsImVtYWlsIjoiIiwiYXV0aCI6ImMzVnlaVzV3YVRveE1qTTBOVFk9In19fQ== kind: Secret metadata: annotations: kubesphere.io/creator: admin creationTimestamp: "2021-03-09T01:07:50Z" name: "22" namespace: b2i...
Below is an example of a project: ``` apiVersion: v1 kind: Namespace metadata: annotations: kubesphere.io/creator: admin finalizers: - finalizers.kubesphere.io/namespaces labels: kubesphere.io/namespace: b2i kubesphere.io/workspace: test name: b2i ownerReferences: - apiVersion: tenant.kubesphere.io/v1alpha1...
## Username & Password ``` apiVersion: v1 data: password: YXNkZg== username: YXNkZg== kind: Secret metadata: annotations: credential.devops.kubesphere.io/autosync: "true" credential.devops.kubesphere.io/datahash: 848fbcbc7d credential.devops.kubesphere.io/syncstatus: successful credential.devops.kubesphere.io/synctime: 2021-03-08 16:45:31.889544672 +0800 CST m=+6505.581589688 kubesphere.io/creator: admin...
Some images will be loaded during the runtime instead of the installation phase of KubeSphere. It's very reasonable. But for the users, might need to wait for a while before...
This is an example of usage: `kubectl ks com reset --version nightly`
It's very useful in some cases: * Run some quick tests against Pipeline
The usage could be like this: `kubectl ks install` see also https://github.com/kubesphere/ks-installer#to-start-deploying-kubesphere