[release-3.1] combine some feature fixes by cherry-pick

[zhu733756]

cherry-pick-to-release-3.1

The pr description updates as following:

• commit 1 update kubespheredev image addr to support kubeedge v1.6.1, from upgrade kubeedge version to v1.6.2 #1527 at branch master, which have conflicts with current pr, have added a commit to fix conficts.
• commit 2 support external prometheus stack, fix How to bring my own prometheus #1503 , from support external prometheus stack #1528 at branch master.
• commit 3 update kubedge offical image addr to support kubeedge v1.6.2. from Update the official mirror address for kubeedge v1.6.2 #1542 at branch master.

/cc @benjaminhuo @pixiake

[zryfish]

Please read this doc: https://github.com/kubesphere/community/blob/master/developer-guide/development/the-pr-author-guide-to-getting-through-code-review.md. And please add the original PR link here, and more description on which features are ported to release-3.1 and why we needed in release-3.1.

[zhu733756]

Please read this doc: https://github.com/kubesphere/community/blob/master/developer-guide/development/the-pr-author-guide-to-getting-through-code-review.md. And please add the original PR link here, and more description on which features are ported to release-3.1 and why we needed in release-3.1.

• commit 1 update kubespheredev image addr, from upgrade kubeedge version to v1.6.2 #1527 at branch master, which have conflicts with current pr, have added a commit to fix conficts above.
• commit 2 support external prometheus stack, fix How to bring my own prometheus #1503 , from support external prometheus stack #1528 at branch master.
• commit 3 update kubedge offical image addr to support kubeedge v1.6.2. from Update the official mirror address for kubeedge v1.6.2 #1542 at branch master.

[zryfish]

Please read this doc: https://github.com/kubesphere/community/blob/master/developer-guide/development/the-pr-author-guide-to-getting-through-code-review.md. And please add the original PR link here, and more description on which features are ported to release-3.1 and why we needed in release-3.1.

• commit 1 update kubespheredev image addr, from upgrade kubeedge version to v1.6.2 #1527 at branch master, which have conflicts with current pr, have added a commit to fix conficts above.
• commit 2 support external prometheus stack, fix How to bring my own prometheus #1503 , from support external prometheus stack #1528 at branch master.
• commit 3 update kubedge offical image addr to support kubeedge v1.6.2. from Update the official mirror address for kubeedge v1.6.2 #1542 at branch master.

Thanks, please add it to the PR description, easier to find.

[zhu733756]

Please read this doc: https://github.com/kubesphere/community/blob/master/developer-guide/development/the-pr-author-guide-to-getting-through-code-review.md. And please add the original PR link here, and more description on which features are ported to release-3.1 and why we needed in release-3.1.

• commit 1 update kubespheredev image addr, from upgrade kubeedge version to v1.6.2 #1527 at branch master, which have conflicts with current pr, have added a commit to fix conficts above.
• commit 2 support external prometheus stack, fix How to bring my own prometheus #1503 , from support external prometheus stack #1528 at branch master.
• commit 3 update kubedge offical image addr to support kubeedge v1.6.2. from Update the official mirror address for kubeedge v1.6.2 #1542 at branch master.

Thanks, please add it to the PR description, easier to find.

Ok, next time i will do better!

[pixiake]

/approve

[ks-ci-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: pixiake, zhu733756

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [pixiake]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[pixiake]

/lgtm