Update VIP picture and IP address requirements #468
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
@@ -42,6 +42,16 @@ A three-node cluster is required to realize the multi-node features of Harvester | |||||||||||||||||
|
|
||||||||||||||||||
| Harvester nodes have the following network requirements for installation. | ||||||||||||||||||
|
|
||||||||||||||||||
| ### IP Address Requirements for Harvester Nodes | ||||||||||||||||||
|
|
||||||||||||||||||
| Harvester is built on top of Kubernetes, and each node needs an independent IP address. Harvester uses this IP address to identify a node identity, and it cannot change during the lifecycle of a Harvester cluster. | ||||||||||||||||||
|
There was a problem hiding this comment.
Suggested change
|
||||||||||||||||||
|
|
||||||||||||||||||
| ### IP Address Requirements for Harvester Cluster | ||||||||||||||||||
|
|
||||||||||||||||||
| The Harvester cluster needs an additional IP address called Virtual IP (VIP). It uses it as the management IP for the whole cluster. | ||||||||||||||||||
|
|
||||||||||||||||||
| Please refer to [Management Address](./management-address.md) for more details. | ||||||||||||||||||
|
Comment on lines
+49
to
+53
There was a problem hiding this comment.
Suggested change
|
||||||||||||||||||
|
|
||||||||||||||||||
| ### Port Requirements for Harvester Nodes | ||||||||||||||||||
|
|
||||||||||||||||||
| Harvester nodes require the following port connections or inbound rules. Typically, all outbound traffic is allowed. | ||||||||||||||||||
|
|
||||||||||||||||||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
@@ -13,12 +13,18 @@ Description: The Harvester provides a virtual IP as the management address. | |||||||||||||
|
|
||||||||||||||
| Harvester provides a fixed virtual IP (VIP) as the management address, VIP must be different from any Node IP. You can find the management address on the console dashboard after the installation. | ||||||||||||||
|
|
||||||||||||||
| The VIP is configured while the **first Node** of the cluster is installed. | ||||||||||||||
|
There was a problem hiding this comment.
Suggested change
|
||||||||||||||
|
|
||||||||||||||
| e.g.  | ||||||||||||||
|
There was a problem hiding this comment.
Suggested change
|
||||||||||||||
|
|
||||||||||||||
| :::note | ||||||||||||||
|
|
||||||||||||||
| If you selected the IP address to be configured via DHCP, you will need to configure static MAC-to-IP address mapping on your DHCP server in order to have a persistent Virtual IP | ||||||||||||||
|
|
||||||||||||||
| ::: | ||||||||||||||
|
|
||||||||||||||
| After the Node starts successfully, both of the VIP and Node IP are shown on the console. | ||||||||||||||
|
There was a problem hiding this comment.
Suggested change
|
||||||||||||||
|
|
||||||||||||||
|  | ||||||||||||||
|
|
||||||||||||||
| ## How to get the VIP MAC address | ||||||||||||||
|
|
@@ -34,8 +40,17 @@ Example of output: | |||||||||||||
| ``` | ||||||||||||||
|
|
||||||||||||||
| ## Usages | ||||||||||||||
|
|
||||||||||||||
| The management address: | ||||||||||||||
|
|
||||||||||||||
| - Allows the access to the Harvester API/UI via `HTTPS` protocol. | ||||||||||||||
| - Allows other nodes to join the cluster. | ||||||||||||||
|  | ||||||||||||||
|
|
||||||||||||||
| :::note | ||||||||||||||
|
|
||||||||||||||
| After the first Node of the Harvester cluster is installed, user may configure the [ssl-certificates](../advanced/settings.md#ssl-certificates), then the cluster can be accessed via VIP and FQDN. | ||||||||||||||
|
|
||||||||||||||
| The following installed Node can also join the cluster by both VIP and FQDN. When using FQDN, please note a known issue [Unable to join the new node](https://github.com/harvester/harvester/issues/4511) and workaround: https://github.com/harvester/harvester/issues/4511#issuecomment-1761047115 | ||||||||||||||
|
Comment on lines
+52
to
+54
There was a problem hiding this comment.
Suggested change
|
||||||||||||||
|
|
||||||||||||||
| ::: | ||||||||||||||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
@@ -42,6 +42,16 @@ A three-node cluster is required to realize the multi-node features of Harvester | |||||||||||||||||
|
|
||||||||||||||||||
| Harvester nodes have the following network requirements for installation. | ||||||||||||||||||
|
|
||||||||||||||||||
| ### IP Address Requirements for Harvester Nodes | ||||||||||||||||||
|
|
||||||||||||||||||
| Harvester is built on top of Kubernetes, and each node needs an independent IP address. Harvester uses this IP address to identify a node identity, and it cannot change during the lifecycle of a Harvester cluster. | ||||||||||||||||||
|
There was a problem hiding this comment.
Suggested change
|
||||||||||||||||||
|
|
||||||||||||||||||
| ### IP Address Requirements for Harvester Cluster | ||||||||||||||||||
|
|
||||||||||||||||||
| The Harvester cluster needs an additional IP address called Virtual IP (VIP). It uses it as the management IP for the whole cluster. | ||||||||||||||||||
|
|
||||||||||||||||||
| Please refer to [Management Address](./management-address.md) for more details. | ||||||||||||||||||
|
Comment on lines
+49
to
+53
There was a problem hiding this comment.
Suggested change
|
||||||||||||||||||
|
|
||||||||||||||||||
| ### Port Requirements for Harvester Nodes | ||||||||||||||||||
|
|
||||||||||||||||||
| Harvester nodes require the following port connections or inbound rules. Typically, all outbound traffic is allowed. | ||||||||||||||||||
|
|
||||||||||||||||||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.