我暴露gateway端口后，不小心获取了token
，我现在访问http://localhost:8000/使用默认的用户名和密码登陆显示账号和密码错误，我该怎么操作。

版本：2.1
模块：DevOps
复现方法：修改流水线参数，删除一部分，增加一部分
相关截图：

/assign @leoendless
/area devops

功能描述:
浏览器中记录用户最近访问的 集群、企业空间、 项目、 DevOps工程。在用户开启访问记录的页面时可以快速切换之前访问的层级资源

原型地址:
zpl://screen?pid=5cbe7fbc2f55d8b73f56811b&sid=5e09a8be734c3d972510a296

官方的Lego-UI文档打算开源么？？

在部署服务或者deploy的时候容器添加并没有initcontainer，感觉部署带有initcontainer的服务很不方便

Describe the bug(描述下问题)
我在测试灰度发布功能时，不小心把镜像名后面的空格也复制了并粘贴到了设置窗口中，然后就review v2服务就一直起不来，只能进集群查看replicaset才能发现问题。镜像名后面多一个空格本来就是一个错误，希望前端在接受用户输入时把镜像名前后的空格都去掉

Versions used(KubeSphere/Kubernetes的版本)
KubeSphere: 2.1.0
Kubernetes: 1.15.7

Environment(环境的硬件配置)
1 masters: 4cpu/16g
3 nodes: 4cpu/16g

• When no backend service of KubeSphere is configured, it throws internal error. It should never throw such error to end user.
  

/kind bug
/milestone 2.1.1
/cc @leoendless

运行后localhost后的用户名和密码默认是啥？无法登陆啊

/kind bug
/milestone 2.1.1
/assign @minghaoye

报警规则和通知规则 不能修改

1、login kubesphere system with admin account
2、open devtools about chrome
3、open mail setting page
excepted result ： cannot find mail password
actual result： can find mail password

设计稿
zpl://screen?sid=5dd24a47c5060b624f9ac5ff&pid=5cbd3e2d21c1ba7ba1eb412a

/area console
/kind design
/milestone 2.1.1

KubeSphere: 2.1.0
Kubernetes: 1.13.7
To Reproduce(复现步骤)
1.使用GitHub上前端代码编译替换之前的前端镜像发现
2.进入企业空间的项目/服务/资源状态 点击更多操作，点击编辑外网访问/编辑配置文件 无法打开对话框

Prototype Link
zpl://screen?sid=5dc5218250731722a4c2f30c&pid=5cbe7fbc2f55d8b73f56811b

flow
https://kpl2mk.axshare.com

content

• Initialize the login Settings
• Registration process
• Forget Password
• Login

/area console
/kind design
/milestone 3.0.0

使用的是doc/development-with-docker.md进行部署的。

General remarks

Please delete this section including header before submitting
也可以使用中文

This form is to report bugs. For general usage questions refer to our Slack channel
KubeSphere-users

Describe the bug(描述下问题)
在全局日志里查询日志，开启实时后，顺序混乱。如下图，时间顺序 11:36:53 -> 11:36:08 -> 11:37:08

Versions used(KubeSphere/Kubernetes的版本)
KubeSphere: v2.1.0
Kubernetes: (If KubeSphere installer used, you can skip this)

Expected behavior(预期行为)
日志顺序统一

提供一个类似kibana 可以把 搜索条件 保存为一个试图，下次登陆可以继续查看日志。
这里的条件如果不能保存，我每次进来都要 重新选择一轮？

Reproduce steps：
1、select a node and add a Taint
2、select the node and click [Taint Management] button
Actual result：the taint in step is common taint
Expected result：the taint in step1 is node taint

// src/utils/object.mapper.js
const getApplicationStatus = item => {
  const conditions = get(item, 'status.conditions', [])

  for (let index = 0; index < conditions.length; index++) {
    const condition = conditions[index]
    if (condition.type === 'Error' && condition.status === 'True') {
      return 'Error'
    }
    if (condition.type === 'Ready' && condition.status === 'True') {
      return 'Ready'
    }
  }

  return 'Updating'
}

if application's status.conditions is empty, app status should appear as Ready not Updateing.

vscode执行的时候，已经在我的电脑中配置了yarn的环境变量
yarn start然后报错如下：

PS G:\代码例子\daima\console> yarn start
yarn run v1.21.1
$ concurrently -k --raw 'yarn dev:client' 'yarn dev:server'
''yarn' 不是内部或外部命令，也不是可运行的程序
或批处理文件。
文件名、目录名或卷标语法不正确。
''yarn' 不是内部或外部命令，也不是可运行的程序
或批处理文件。
文件名、目录名或卷标语法不正确。
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
PS G:\daima\console>

General remarks

Please delete this section including header before submitting
也可以使用中文

This form is to report bugs. For general usage questions refer to our Slack channel
KubeSphere-users

Describe the bug(描述下问题)
A clear and concise description of what the bug is.

For UI issues please also add a screenshot that shows the issue.

Versions used(KubeSphere/Kubernetes的版本)
KubeSphere:
Kubernetes: (If KubeSphere installer used, you can skip this)

Environment(环境的硬件配置)
How many nodes and their hardware configuration:

For example:
3 masters: 8cpu/8g
3 nodes: 8cpu/16g

(and other info are welcomed to help us debugging)

To Reproduce(复现步骤)
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior(预期行为)
A clear and concise description of what you expected to happen.

Total 12 records, first page 10 items, so next page should display left 2 items, but what i'got are 2 items displayed in prev. page.
(共有12条记录，分两页。第一页显示10-条，第二页显示2页，但点击第二页时，看到的却是在第一页上看到的记录)

General remarks

Please delete this section including header before submitting
也可以使用中文

This form is to report bugs. For general usage questions refer to our Slack channel
KubeSphere-users

Describe the bug(描述下问题)
A clear and concise description of what the bug is.

For UI issues please also add a screenshot that shows the issue.

需要检查 resource kapi，应该做了分页（默认 limit=10，page=1）。api 返回里写了 total_count=12）。没有处理分页，所以只展示了10个item，而不是全部监控目标

Versions used(KubeSphere/Kubernetes的版本)
KubeSphere: 2.1.0
Kubernetes: (If KubeSphere installer used, you can skip this)

Environment(环境的硬件配置)
How many nodes and their hardware configuration:

For example:
3 masters: 8cpu/8g
3 nodes: 8cpu/16g

(and other info are welcomed to help us debugging)

To Reproduce(复现步骤)
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior(预期行为)
A clear and concise description of what you expected to happen.

2.1.0分支最新代码，本地Node版本1.13.7，yarn版本1.21.1。不知道是不是我的环境哪里有问题，请帮忙看下下面的错误，谢谢

$ yarn start
yarn run v1.21.1
$ concurrently -k --raw 'yarn dev:client' 'yarn dev:server'
$ cross-env NODE_ENV=development webpack-dev-server --config scripts/webpack.dev.js -w
$ cross-env NODE_ENV=development nodemon -w ./common -w ./server -e js,yaml server/server.js
[nodemon] 1.18.11
[nodemon] to restart at any time, enter `rs`
[nodemon] watching: ./common /Users/wupeng/work/console_360/server/**/*
[nodemon] starting `node server/server.js`
Dashboard app running at port 8000
Happy[jsx]: Version: 5.0.1. Threads: 3
ℹ ｢wds｣: Project is running at http://0.0.0.0:8001/
ℹ ｢wds｣: webpack output is served from /
ℹ ｢wds｣: Content not from webpack is served from /Users/wupeng/work/console_360
Happy[jsx]: All set; signaling webpack to proceed.
✔ success webpack compiled in 581ms
✖ ｢wdm｣: Hash: 36f497e885671ccb4706
Version: webpack 4.41.4
Time: 667ms
Built at: 02/06/2020 5:54:37 PM
    Asset      Size  Chunks             Chunk Names
  main.js  33.5 KiB    main  [emitted]  main
vendor.js  1.31 MiB  vendor  [emitted]  vendor
Entrypoint main = vendor.js main.js
[0] multi (webpack)-dev-server/client?http://0.0.0.0:8001 (webpack)/hot/dev-server.js react-hot-loader/patch ./src/core/index.js 64 bytes {main} [built]
[./node_modules/react-hot-loader/dist/react-hot-loader.development.js] 97.1 KiB {vendor} [built]
[./node_modules/react-hot-loader/patch.js] 229 bytes {vendor} [built]
[./node_modules/webpack-dev-server/client/index.js?http://0.0.0.0:8001] (webpack)-dev-server/client?http://0.0.0.0:8001 4.29 KiB {vendor} [built]
[./node_modules/webpack-dev-server/client/overlay.js] (webpack)-dev-server/client/overlay.js 3.51 KiB {vendor} [built]
[./node_modules/webpack-dev-server/client/socket.js] (webpack)-dev-server/client/socket.js 1.53 KiB {vendor} [built]
[./node_modules/webpack-dev-server/client/utils/createSocketUrl.js] (webpack)-dev-server/client/utils/createSocketUrl.js 2.89 KiB {vendor} [built]
[./node_modules/webpack-dev-server/client/utils/log.js] (webpack)-dev-server/client/utils/log.js 964 bytes {vendor} [built]
[./node_modules/webpack-dev-server/client/utils/reloadApp.js] (webpack)-dev-server/client/utils/reloadApp.js 1.59 KiB {vendor} [built]
[./node_modules/webpack-dev-server/client/utils/sendMessage.js] (webpack)-dev-server/client/utils/sendMessage.js 402 bytes {vendor} [built]
[./node_modules/webpack-dev-server/node_modules/strip-ansi/index.js] (webpack)-dev-server/node_modules/strip-ansi/index.js 161 bytes {vendor} [built]
[./node_modules/webpack/hot sync ^\.\/log$] (webpack)/hot sync nonrecursive ^\.\/log$ 170 bytes {main} [built]
[./node_modules/webpack/hot/dev-server.js] (webpack)/hot/dev-server.js 1.59 KiB {vendor} [built]
[./node_modules/webpack/hot/emitter.js] (webpack)/hot/emitter.js 75 bytes {vendor} [built]
[./src/core/index.js] 881 bytes {main} [built] [failed] [1 error]
    + 46 hidden modules

ERROR in ./src/core/index.js
Module build failed (from ./node_modules/happypack/loader.js):
TypeError: Cannot read property 'concat' of undefined
    at findPath (/Users/wupeng/work/console_360/node_modules/babel-plugin-recharts/lib/index.js:55:26)
    at /Users/wupeng/work/console_360/node_modules/babel-plugin-recharts/lib/index.js:126:17
    at Array.forEach (<anonymous>)
    at Object.<anonymous> (/Users/wupeng/work/console_360/node_modules/babel-plugin-recharts/lib/index.js:118:21)
    at Module._compile (internal/modules/cjs/loader.js:1151:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1171:10)
    at Module.load (internal/modules/cjs/loader.js:1000:32)
    at Function.Module._load (internal/modules/cjs/loader.js:899:14)
    at Module.require (internal/modules/cjs/loader.js:1040:19)
    at require (internal/modules/cjs/helpers.js:72:18)
 @ multi react-hot-loader/patch ./src/core/index.js main[1]
ℹ ｢wdm｣: Failed to compile.

yarn

yarn install v1.22.0
[1/5] 🔍 Validating package.json...
[2/5] 🔍 Resolving packages...
[3/5] 🚚 Fetching packages...
[4/5] 🔗 Linking dependencies...
warning " > [email protected]" has unmet peer dependency "@types/react@^15.0.0 || ^16.0.0".
warning " > [email protected]" has unmet peer dependency "babel-core@^6.0.0 || ^7.0.0-0".
[5/5] 🔨 Building fresh packages...
success Saved lockfile.
$ rimraf .cache-loader
✨ Done in 72.88s.

yarn lego

yarn run v1.22.0
$ webpack -p --config scripts/webpack.lego.js
✔ success webpack compiled in 1s 455ms
Hash: a928e222abddf0e99f13
Version: webpack 4.41.6
Time: 1460ms
Built at: 02/13/2020 8:30:31 AM
Asset Size Chunks Chunk Names
lego.css 370 KiB 0 [emitted] [big] lego
lego.js 932 bytes 0 [emitted] lego
Entrypoint lego [big] = lego.css lego.js
[0] ./src/scss/lego.theme.scss 39 bytes {0} [built]
+ 1 hidden module
Child mini-css-extract-plugin node_modules/cache-loader/dist/cjs.js!node_modules/css-loader/index.js??ref--4-2!node_modules/postcss-loader/src/index.js??postcss!node_modules/sass-loader/dist/cjs.js!src/scss/lego.theme.scss:
Entrypoint mini-css-extract-plugin = *
[0] ./node_modules/cache-loader/dist/cjs.js!./node_modules/css-loader??ref--4-2!./node_modules/postcss-loader/src??postcss!./node_modules/sass-loader/dist/cjs.js!./src/scss/lego.theme.scss 370 KiB {0} [built]
+ 1 hidden module
✨ Done in 2.32s.

yarn start

yarn run v1.22.0
$ concurrently -k --raw 'yarn dev:client' 'yarn dev:server'
$ cross-env NODE_ENV=development nodemon -w ./common -w ./server -e js,yaml server/server.js
$ cross-env NODE_ENV=development webpack-dev-server --config scripts/webpack.dev.js -w
[nodemon] 1.19.4
[nodemon] to restart at any time, enter rs
[nodemon] watching dir(s): common server/**/*
[nodemon] watching extensions: js,yaml
[nodemon] starting node server/server.js
Dashboard app running at port 8000
Happy[jsx]: Version: 5.0.1. Threads: 3
ℹ ｢wds｣: Project is running at http://0.0.0.0:8001/
ℹ ｢wds｣: webpack output is served from /
ℹ ｢wds｣: Content not from webpack is served from /Users/ym-10458/Documents/devops/kubesphere.io/console
Happy[jsx]: All set; signaling webpack to proceed.
✔ success webpack compiled in 605ms
✖ ｢wdm｣: Hash: 7eec6b63eb20fd752509
Version: webpack 4.41.6
Time: 694ms
Built at: 02/13/2020 8:30:40 AM
Asset Size Chunks Chunk Names
main.js 33.5 KiB main [emitted] main
vendor.js 1.3 MiB vendor [emitted] vendor
Entrypoint main = vendor.js main.js
[0] multi (webpack)-dev-server/client?http://0.0.0.0:8001 (webpack)/hot/dev-server.js react-hot-loader/patch ./src/core/index.js 64 bytes {main} [built]
[./node_modules/react-hot-loader/dist/react-hot-loader.development.js] 97.1 KiB {vendor} [built]
[./node_modules/react-hot-loader/patch.js] 229 bytes {vendor} [built]
[./node_modules/webpack-dev-server/client/index.js?http://0.0.0.0:8001] (webpack)-dev-server/client?http://0.0.0.0:8001 4.29 KiB {vendor} [built]
[./node_modules/webpack-dev-server/client/overlay.js] (webpack)-dev-server/client/overlay.js 3.51 KiB {vendor} [built]
[./node_modules/webpack-dev-server/client/socket.js] (webpack)-dev-server/client/socket.js 1.53 KiB {vendor} [built]
[./node_modules/webpack-dev-server/client/utils/createSocketUrl.js] (webpack)-dev-server/client/utils/createSocketUrl.js 2.91 KiB {vendor} [built]
[./node_modules/webpack-dev-server/client/utils/log.js] (webpack)-dev-server/client/utils/log.js 964 bytes {vendor} [built]
[./node_modules/webpack-dev-server/client/utils/reloadApp.js] (webpack)-dev-server/client/utils/reloadApp.js 1.59 KiB {vendor} [built]
[./node_modules/webpack-dev-server/client/utils/sendMessage.js] (webpack)-dev-server/client/utils/sendMessage.js 402 bytes {vendor} [built]
[./node_modules/webpack-dev-server/node_modules/strip-ansi/index.js] (webpack)-dev-server/node_modules/strip-ansi/index.js 161 bytes {vendor} [built]
[./node_modules/webpack/hot sync ^./log$] (webpack)/hot sync nonrecursive ^./log$ 170 bytes {main} [built]
[./node_modules/webpack/hot/dev-server.js] (webpack)/hot/dev-server.js 1.59 KiB {vendor} [built]
[./node_modules/webpack/hot/emitter.js] (webpack)/hot/emitter.js 75 bytes {vendor} [built]
[./src/core/index.js] 952 bytes {main} [built] [failed] [1 error]
+ 44 hidden modules

ERROR in ./src/core/index.js
Module build failed (from ./node_modules/happypack/loader.js):
TypeError: Cannot read property 'concat' of undefined
at findPath (/Users/ym-10458/Documents/devops/kubesphere.io/console/node_modules/babel-plugin-recharts/lib/index.js:55:26)
at /Users/ym-10458/Documents/devops/kubesphere.io/console/node_modules/babel-plugin-recharts/lib/index.js:126:17
at Array.forEach ()
at Object. (/Users/ym-10458/Documents/devops/kubesphere.io/console/node_modules/babel-plugin-recharts/lib/index.js:118:21)
at Module._compile (internal/modules/cjs/loader.js:1144:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1164:10)
at Module.load (internal/modules/cjs/loader.js:993:32)
at Function.Module._load (internal/modules/cjs/loader.js:892:14)
at Module.require (internal/modules/cjs/loader.js:1033:19)
at require (internal/modules/cjs/helpers.js:72:18)
@ multi react-hot-loader/patch ./src/core/index.js main[1]
ℹ ｢wdm｣: Failed to compile.

KubeSphere: 2.1.1
Kubernetes: 1.13.7
To Reproduce(复现步骤)
1.使用GitHub上前端代码编译替换之前的前端镜像发现
2.右下角工具箱有时候无法进入到终端，报错如下图

3.就算进入点击X按钮也无法退出，截图如下

4.编译的log
yarn run v1.19.1
$ rimraf dist
$ yarn build:client && yarn build:server
$ yarn lego && webpack -p --config scripts/webpack.prod.js --display errors-only
$ webpack -p --config scripts/webpack.lego.js
✔ success webpack compiled in 779ms
Hash: 0f19b80ca984b9617454
Version: webpack 4.30.0
Time: 788ms
Built at: 2019-12-10 07:51:11
Asset Size Chunks Chunk Names
lego.css 370 KiB 0 [emitted] [big] lego
lego.js 932 bytes 0 [emitted] lego
Entrypoint lego [big] = lego.css lego.js
[0] ./src/scss/lego.theme.scss 39 bytes {0} [built]
+ 1 hidden module
Child mini-css-extract-plugin node_modules/cache-loader/dist/cjs.js!node_modules/css-loader/index.js??ref--4-2!node_modules/postcss-loader/src/index.js??postcss!node_modules/sass-loader/lib/loader.js!src/scss/lego.theme.scss:
Entrypoint mini-css-extract-plugin = *
[0] ./node_modules/cache-loader/dist/cjs.js!./node_modules/css-loader??ref--4-2!./node_modules/postcss-loader/src??postcss!./node_modules/sass-loader/lib/loader.js!./src/scss/lego.theme.scss 370 KiB {0} [built]
+ 1 hidden module
Happy[jsx]: Version: 5.0.1. Threads: 3
Happy[jsx]: All set; signaling webpack to proceed.

✔ success webpack compiled in 1m 24s 913ms
Webpack Bundle Analyzer saved report to /mnt/dist/report.html

SMP ⏱
General output time took 1 min, 32.53 secs

SMP ⏱ Plugins
WebpackBarPlugin took 17.026 secs
MiniCssExtractPlugin took 10.11 secs
OptimizeCssAssetsWebpackPlugin took 9.57 secs
BundleAnalyzerPlugin took 7.6 secs
CopyPlugin took 0.89 secs
ChunksRenamePlugin took 0.484 secs
DefinePlugin took 0.477 secs
HappyPlugin took 0.191 secs

SMP ⏱ Loaders
cache-loader took 1 min, 9.27 secs
module count = 3087
happypack took 1 min, 0.825 secs
module count = 1097
mini-css-extract-plugin, and
cache-loader, and
css-loader, and
postcss-loader, and
fast-sass-loader took 56.4 secs
module count = 491
cache-loader, and
css-loader, and
postcss-loader, and
fast-sass-loader took 51.55 secs
module count = 491
cache-loader, and
@svgr/webpack, and
url-loader took 4.53 secs
module count = 9
mini-css-extract-plugin, and
cache-loader, and
css-loader took 2.79 secs
module count = 3
modules with no loaders took 1.56 secs
module count = 5
cache-loader, and
css-loader took 1.4 secs
module count = 3
file-loader took 0.274 secs
module count = 18

$ webpack -p --config scripts/webpack.server.js --display errors-only
Done in 122.89s.

Describe the bug(描述下问题)
如下图，当我开始编辑这个流水线时，我能拖动任务进行排序但是鼠标松开后就恢复到原来顺序了。第二次再要拖动时，那里已经固定无法操作了。

Versions used(KubeSphere/Kubernetes的版本)
KubeSphere: 2.1.0
Kubernetes: 1.15.7

Environment(环境的硬件配置)
1 masters: 4cpu/16g
3 nodes: 4cpu/16g

/kind bug
/assign @minghaoye
/milestone 2.1.1

2.1.1 将允许镜像名称包含 scheme，具体来说，镜像仓库密钥地址包含以下两种情况。

1. 不带scheme
   例如： dockerhub.qingcloud.com
   在这种情况下前端无需特殊处理，镜像名称可能为 dockerhub.qingcloud.com/runzexia/hello:latest
2. https/http
   例如 https://dockerhub.qingcloud.com
   在这种情况下前端需要去除镜像仓库地址中的scheme
   错误示例： https://dockerhub.qingcloud.com/runzexia/hello:latest
http://dockerhub.qingcloud.com/runzexia/hello:latest
   正确示例:
   dockerhub.qingcloud.com/runzexia/hello:latest

KubeSphere: 2.1.0
Kubernetes: 1.13.7
To Reproduce(复现步骤)
1.点击工作负载，选择一个工作负载，点击更多操作，选择弹性伸缩，填入CPU百分比和最大副本数，点击确认（不要填入内存限制数）
2.点击弹性伸缩，修改最大副本数，发现如下报错，提示一定要输入内存限制数

For UI issues please also add a screenshot that shows the issue.

To Reproduce(复现步骤)
Steps to reproduce the behavior:

1. Go to 'Deployment'
2. Click on 'Create' button
3. add a sample image, for example, tomcat,
4. Config env variable for this container

Expected behavior(预期行为)
Providing a cm/secret setup link if no proper cm/secret is listed.

General remarks

Please delete this section including header before submitting
也可以使用中文

This form is to report bugs. For general usage questions refer to our Slack channel
KubeSphere-users

Describe the bug(描述下问题)
A clear and concise description of what the bug is.

For UI issues please also add a screenshot that shows the issue.

这一处来源于告警模块：

这一处来源于 resource kapi:

应以后者为准。建议是前面的屏蔽监控目标一列？或者用 resource kapi 替换？

这是个workaround，本质原因来源于监控算法（算法是正确的，只是不能做到 null 数据时返回0），导致告警模块返回的数量不正确。

Versions used(KubeSphere/Kubernetes的版本)
KubeSphere:
Kubernetes: (If KubeSphere installer used, you can skip this)

Environment(环境的硬件配置)
How many nodes and their hardware configuration:

For example:
3 masters: 8cpu/8g
3 nodes: 8cpu/16g

(and other info are welcomed to help us debugging)

To Reproduce(复现步骤)
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior(预期行为)
A clear and concise description of what you expected to happen.

Describe the bug(描述下问题)
在多master集群部署kubesphere后无法登陆，提示用户名或密码错误。

看了下kubesphere项目的login函数并测试了一下，err = conn.Bind(dn, password)会去openldap认证当前登录用户，这里传入的密码应该是用户的未加密密码，测试时发现传入的密码是加密后的。
再看了下前端代码，在handlerLogin函数的如下代码段中

      if (params.encrypt) {
        params.password = decryptPassword(params.encrypt, ctx.session.salt)
        delete params.encrypt
      }

ctx.session.salt参数打印是undefined，怀疑问题出在这里，没有成功对密码进行解密。不清楚这个salt参数为undefined是偶然还是必然。请帮忙确认下，谢谢

For UI issues please also add a screenshot that shows the issue.

Versions used(KubeSphere/Kubernetes的版本)
KubeSphere: 2.1.1
Kubernetes: 1.15.10

Environment(环境的硬件配置)
How many nodes and their hardware configuration:

3 masters: 8cpu/8g
1 nodes: 8cpu/16g

(and other info are welcomed to help us debugging)

To Reproduce(复现步骤)
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior(预期行为)
页面可以登录

feature request

https://kubesphere.com.cn/forum/d/537

文案有小错误。

Describe the bug(描述下问题)
在浏览器页面上下翻动时，往上翻页下一页按钮和工具按钮很容易混在一起，往下翻页下一页按钮就跑到页面底部看不到了。导致很难点击下一页按钮。希望能优化下，谢谢

Versions used(KubeSphere/Kubernetes的版本)
KubeSphere: 2.1.0
Kubernetes: 1.15.7

Environment(环境的硬件配置)
How many nodes and their hardware configuration:

For example:
1 masters: 4cpu/16g
3 nodes: 4cpu/16g

RT;
Prototype Link
zpl://screen?pid=5cbe7fbc2f55d8b73f56811b&sid=5dd6358bc380610b76120a7e

/area console
/kind design
/milestone 2.1.1

/assign @minghaoye

请问是否可以添加换主题的功能呢？

虽然提供的有variables.scss、lego.theme.scss、lego.custom.scss等样式文件
但是项目中还是有很多零散的样式
想要改主题色还需要手动去搜索更改
并且涉及的文件还是挺多的

后续可否在现有基础上统一样式添加换主题的功能呢？

Describe the bug(描述下问题)
A clear and concise description of what the bug is.

provide an option to enable or disable menu auto-hide, maybe could be located in the user account setting page.

版本：2.1

操作：

1，创建示例应用 bookinfo
2，在服务中创建【外部服务】

查看不到第一步中创建的应用。

尝试的方法：

1，刷新页面，无法出现列表
2，反复点击应用列表，可以看到 bookinfo 应用

预期：

创建外部服务时，点击高级设置，能查看当前项目下的完整应用列表。

/area console
/assign @leoendless

General remarks

Please delete this section including header before submitting
也可以使用中文

This form is to report bugs. For general usage questions refer to our Slack channel
KubeSphere-users

Describe the bug(描述下问题)
A clear and concise description of what the bug is.

For UI issues please also add a screenshot that shows the issue.

Versions used(KubeSphere/Kubernetes的版本)
KubeSphere: 2.1
Kubernetes: (If KubeSphere installer used, you can skip this)

Environment(环境的硬件配置)
How many nodes and their hardware configuration:

For example:
3 masters: 8cpu/8g
3 nodes: 8cpu/16g

(and other info are welcomed to help us debugging)

To Reproduce(复现步骤)
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior(预期行为)
A clear and concise description of what you expected to happen.

Describe the bug(描述下问题)
构建镜像功能中，选择条目进行删除，本来是要填写条目名然后确定删除，现在是在填写条目名时对话框迅速自动切换为确认框，完全没法填写条目，这种情况下，点击确认框的确认按钮，无反应。
我随后点击那个条目，进去后，在左上角下拉菜单里删除了这个条目

Versions used(KubeSphere/Kubernetes的版本)
KubeSphere: 2.1.0
Kubernetes: 1.15.7

Environment(环境的硬件配置)
How many nodes and their hardware configuration:

For example:
1 masters: 4cpu/16g
3 nodes: 4cpu/16g

General remarks
Describe the bug(描述下问题)
A clear and concise description of what the bug is.

For UI issues please also add a screenshot that shows the issue.

Versions used(KubeSphere/Kubernetes的版本)
KubeSphere: 2.1.1
The default storage class is nfs

To Reproduce(复现步骤)
Steps to reproduce the behavior:
As nfs limitation, there's no API provided from nfs to get mounted volume usage for each pv, but on KubeSphere console, it seems we always show it as '0%'.
This is very confusing to end-users.

Expected behavior(预期行为)
on the volume list page, if those volumes belong to nfs sc, just tell end-users that 'capacity usage is not supported for nfs'.

Suggestions: Disable creating of new ingresses, but allow editing existed ingresses.

General remarks

Please delete this section including header before submitting
也可以使用中文

This form is to report bugs. For general usage questions refer to our Slack channel
KubeSphere-users

Describe the bug(描述下问题)
A clear and concise description of what the bug is.

Click "create" button, get no response.

And an warning pops up when I expand "Add metadata"

Though metadata is filled, I still fail to creare

For UI issues please also add a screenshot that shows the issue.

Versions used(KubeSphere/Kubernetes的版本)
KubeSphere: 2.1.1-dev
Kubernetes: (If KubeSphere installer used, you can skip this)

Environment(环境的硬件配置)
How many nodes and their hardware configuration:

For example:
3 masters: 8cpu/8g
3 nodes: 8cpu/16g

(and other info are welcomed to help us debugging)

To Reproduce(复现步骤)
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior(预期行为)
A clear and concise description of what you expected to happen.