-
Notifications
You must be signed in to change notification settings - Fork 31
Move air gap bundle info to the relevant install topics #2721
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
Conversation
✅ Deploy Preview for replicated-docs-upgrade ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for replicated-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
|
||
| [View a larger version of this image](/images/release-history-link.png) | ||
|
|
||
| 1. On the **Release history** page, click **Build** to build the `.airgap` bundle. |
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.
^ Previously, I was leaning pretty heavily on ".airgap" to talk about the release air gap bundle as opposed to the Admin Console or kURL bundles. Now that the EC bundle also uses the .airgap extension, felt like it would be better to spell out which bundle we are talking about in each case
|
Note from convo with Alex this morning:
|
| 'vendor/releases-share-download-portal', | ||
| 'vendor/releases-configvalues', | ||
| ], | ||
| }, |
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.
^ removed this section.
- releases-download-airgap-bundles was deleted
- licenses-download was moved to the Customer Licenses section
- releases-share-download-portal was moved to the Channels and Releases section
- releases-configvalues was moved to the CLI install section (the only workflow where vendors need it)
This PR removes the preexisting topic on "how to download air gap bundles" in favor of putting that info directly in the relevant air gap installation topics. The reasoning for this change is because:
The solution was to do the following: