events.action: opened
events.author: XJangel
events.text: /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
  
  ```
events.title: update the doc kubeedge_configure
events.type: issue
events.action: created
events.author: fisherxu
events.text: /lgtm
events.type: comment
events.action: created
events.author: XJangel
events.text: 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.
events.type: comment
events.action: created
events.author: fisherxu
events.text: 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. :)
events.type: comment
events.action: created
events.author: XJangel
events.text: Get it! I will modify it right now.
events.type: comment
events.action: created
events.author: fisherxu
events.text: 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`.
events.type: comment
events.action: created
events.author: XJangel
events.text: yep~
events.type: comment
events.action: created
events.author: fisherxu
events.text: /lgtm
events.type: comment
events.action: created
events.author: fisherxu
events.text: /approve
events.type: comment
data_with_bots.bot: New changes are detected. LGTM label has been removed.
data_with_bots.meta: This message directly preceded comment from bot *kubeedge-bot* by author *XJangel*:
data_with_bots.text: yep~
data_with_bots.bot: [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"]} -->
data_with_bots.meta: This message directly preceded comment from bot *kubeedge-bot* by author *fisherxu*:
data_with_bots.text: /approve
data_without_bots.meta: This message directly preceded comment from bot *kubeedge-bot* by author *XJangel*:
data_without_bots.text: yep~
data_without_bots.meta: This message directly preceded comment from bot *kubeedge-bot* by author *fisherxu*:
data_without_bots.text: /approve