-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Day-2 operations for profile variables #2911
Merged
Merged
Changes from 1 commit
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
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
71 changes: 71 additions & 0 deletions
71
docs/docs-content/clusters/edge/local-ui/cluster-management/update-cluster.md
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 |
---|---|---|
@@ -0,0 +1,71 @@ | ||
--- | ||
sidebar_label: "Update Local Cluster" | ||
title: "Update Local Cluster" | ||
description: "Instructions for updating a locally manageg cluster in Edge Host Management Console." | ||
hide_table_of_contents: false | ||
sidebar_position: 40 | ||
tags: ["edge"] | ||
--- | ||
|
||
You can update existing local clusters from the local UI by uploading a new cluster profile version. This guide explains | ||
how to update an existing cluster in local UI. | ||
|
||
:::preview | ||
|
||
::: | ||
|
||
## Prerequisites | ||
|
||
- Network access to the Edge device’s IP and port where the local UI is exposed. The default port is 5080. | ||
|
||
- Credentials to log into the local UI. Any OS user can be used to log in to the local UI. | ||
|
||
- A local cluster created in local UI. For more information, refer to [Create Local Cluster](create-cluster.md). | ||
|
||
## Update Local Cluster | ||
|
||
1. Log into the local UI by visiting the 5080 port of your Edge device's IP address or domain name. For more | ||
information, refer to [Access Local UI](../host-management/access-console.md). | ||
|
||
2. From the left **Main Menu**, select **Cluster**, and then select the **Configuration** tab. | ||
|
||
3. In the upper-right corner, select **Upload Configuration**. | ||
|
||
4. In the **Upload Configuration** wizard, browse or drag and drop the new cluster profile version **.tgz** file. Once | ||
the upload finishes, select **Review Changes**. | ||
|
||
To learn more about how to export a cluster profile and import it during this step, refer to | ||
[Export Cluster Definition](./export-cluster-definition.md). | ||
|
||
5. Local UI displays the **Review Changes** modal, where you can review the update summary and verify all incoming | ||
changes to the cluster profile variables. Your current configuration is displayed on the left, and the incoming | ||
changes are displayed on the right. | ||
|
||
For more information on cluster profile variables, refer to | ||
[Define and Manage Profile Variables](../../../../profiles/cluster-profiles/create-cluster-profiles/define-profile-variables.md). | ||
|
||
6. Click each profile variable and review the changes. You can specify values for new profile variables, override the | ||
incoming default values, or leave the incoming changes as is, depending on your local cluster configuration. | ||
|
||
:::info | ||
|
||
If your current cluster configuration overrides the default profile variable values, local UI will preserve your | ||
configuration in case the update introduces new defaults. To use the new default values, click **Use default** in the | ||
respective profile variable field. | ||
|
||
::: | ||
|
||
7. Once all incoming changes have the **Reviewed** status, click **Confirm Changes**. | ||
|
||
8. Review all profile variables on the **Configuration** tab to make sure that the cluster configuration matches your | ||
expectations. | ||
|
||
9. In the bottom-left corner, click **Update**. | ||
|
||
## Validate | ||
|
||
1. Log in to the local UI. | ||
|
||
2. From the left **Main Menu**, select **Cluster**. | ||
|
||
3. Verify that your cluster is in the **Running** status. |
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
Oops, something went wrong.
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.
when there are this many
..
i would just use absolute path. This way if anything moves this link won't bother you. No need to change it now but just something i do to make my life easier.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.
@lenny we can't use absolute paths, we have to use relative paths otherwise it breaks versioning.
https://docusaurus.io/docs/markdown-features/links
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.
GitHub did me dirty 😓