opened
XJangel
/kind documentation

**What this PR does / why we need it**:
update the configuration steps

**Which issue(s) this PR fixes**:
<!-- 
*Automatically closes linked issue when PR is merged.
Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.
_If PR is about `failing-tests or flakes`, please post the related issues/tests in a comment and do not use `Fixes`_*
-->
Fixes #

**Special notes for your reviewer**:

**Does this PR introduce a user-facing change?**:
<!--
If no, just write "NONE" in the release-note block below.
If yes, a release note is required:
Enter your extended release note in the block below. If the PR requires additional action from users switching to the new release, include the string "action required".
-->
```release-note

```
update the doc kubeedge_configure
issue
created
fisherxu
/lgtm
comment
created
XJangel
For the deployment of single CloudCore, the default advertise-address is just the IP address of CloudCore. So I didn't mention it here. Maybe we can do it  in the documentation of HA CloudCore.
comment
created
fisherxu
The `advertise address` is not only used in ha mode. If edgecore connect to cloudnode through a public(floating) IP, we should set the floating ip in the config file. And the floating Ip can't be  automatically acquired. :)
comment
created
XJangel
Get it! I will modify it right now.
comment
created
fisherxu
Here you don't need explain ha, as long as you explain all the addresses(like floating ip) exposed to the edge node should be added to `advertise address`.
comment
created
XJangel
yep~
comment
created
fisherxu
/lgtm
comment
created
fisherxu
/approve
comment
New changes are detected. LGTM label has been removed.
This message directly preceded comment from bot *kubeedge-bot* by author *XJangel*:
yep~
[APPROVALNOTIFIER] This PR is **NOT APPROVED**

This pull-request has been approved by: *<a href="https://github.com/kubeedge/kubeedge/pull/1656#issuecomment-627707604" title="Approved">fisherxu</a>*
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: **skdwriting**

If they are not already assigned, you can assign the PR to them by writing `/assign @skdwriting` in a comment when ready.

The full list of commands accepted by this bot can be found [here](https://go.k8s.io/bot-commands?repo=kubeedge%2Fkubeedge).

The pull request process is described [here](https://git.k8s.io/community/contributors/guide/owners.md#the-code-review-process)

<details open>
Needs approval from an approver in each of these files:

- **[OWNERS](https://github.com/kubeedge/kubeedge/blob/master/OWNERS)**

Approvers can indicate their approval by writing `/approve` in a comment
Approvers can cancel approval by writing `/approve cancel` in a comment
</details>
<!-- META={"approvers":["skdwriting"]} -->
This message directly preceded comment from bot *kubeedge-bot* by author *fisherxu*:
/approve
This message directly preceded comment from bot *kubeedge-bot* by author *XJangel*:
yep~
This message directly preceded comment from bot *kubeedge-bot* by author *fisherxu*:
/approve