Merge branch 'master' into docs-rel-4-8-0

Author: addetz

.github/workflows/pull_request.yaml

@@ -109,11 +109,6 @@ jobs:
 
       - run: npm ci
 
-      - name: Versions on Release Branch Only
-        if: ${{ startsWith(github.head_ref, 'docs-rel-') }}
-        run: |
-          make versions
-
       - name: Build
         run: |
           touch .env

.github/workflows/release.yaml

@@ -72,7 +72,6 @@ jobs:
         run: |
           echo "CURRENT_STEP=Build" >> $GITHUB_ENV
           touch .env
-          make versions-ci
           make build-ci
 
       - name: Build with cached packs
@@ -139,7 +138,6 @@ jobs:
         run: |
           echo "CURRENT_STEP=Build" >> $GITHUB_ENV
           touch .env
-          make versions-ci
           make build-ci
       
       - name: Build with cached packs

Makefile

@@ -55,7 +55,8 @@ deep-clean: ## Clean all artifacts
 clean-logos: ## Clean logos
 	rm -rf static/img/packs
 
-clean-versions: ## Clean Docusarus content versions
+## Bundled versioning has been removed, but keeping the clean steps for now to allow people to clean up local artifacts.
+clean-versions: ## Clean Docusaurus content versions
 	@echo "cleaning versions"
 	rm -rf api_versions.json versions.json versioned_docs versioned_sidebars api_versioned_sidebars api_versioned_docs versioned_partials
 	git checkout -- docusaurus.config.js static/robots.txt
@@ -183,17 +184,6 @@ build-ci: ## Run npm build in CI environment
 			exit 1; \
 		fi; \
 	}
-	
-
-versions: ## Create Docusarus content versions
-	@echo "creating versions"
-	./scripts/versions.sh $(TMPDIR)
-
-
-versions-ci: ## Create Docusarus content versions in a GitHub Actions CI environment
-	@echo "creating versions"
-	./scripts/versions.sh $$RUNNER_TEMP
-
 
 api: ## Generate API docs
 	@echo "generating api docs"

README.md

@@ -606,8 +606,7 @@ component will automatically display the badge in the correct color based on the
 
 This is a custom component that creates a grid of simple text cards with two columns, styled according to our color
 scheme. The rows of cards are dynamically created according to the list of specified cards. This component uses the
-`VersionedLink` under the covers. URLs should be specified as discussed in the [Internal Links](#internal-links)
-section.
+`VersionedLink` under the covers.
 
 ```js
 <SimpleCardGrid
@@ -754,25 +753,6 @@ The snippet above will work with the example partial we have in our repository,
 Note that the `message` field corresponds to the `{props.message}` reference in the `_partials/_partial_example.mdx`
 file.
 
-### Internal Links
-
-Due to the complexities of Docusaurus plugin rendering, links do not support versioning in `*.mdx` files. If you want to
-add an internal link you will have to use the `VersionedLink` component inside the `*.mdx` file.
-
-```mdx
----
-partial_category: public-cloud
-partial_name: palette-setup
----
-
-This is how you set up Palette in {props.cloud}.
-
-This is an <VersionedLink text="Internal Link" url="/getting-started/additional-capabilities"/>.
-```
-
-The path of the link should be the path of the destination file from the root directory, without any back operators
-`..`. External links can be referenced as usual.
-
 ## Palette/VerteX URLs
 
 A special component has been created to handle the generation of URLs for Palette and VerteX. The component is called
@@ -1000,30 +980,9 @@ The packs component will always display the top-level tab content, so if you add
 new `TabItem` component is the first in the list. If a new pack version does not have a respective tag, the latest
 version content will be displayed automatically.
 
-#### Links
-
-When authoring additional details content, you must use the `<VersionedLink />` component to link to other documentation
-pages. The component is required to ensure that the links are versioned correctly. Refer to the
-[Internal Links](#internal-links) section for more information.
-
-If you want to link to a heading inside the pack component, you must also use the `<VersionedLink />` and include the
-path to the component followed by the heading id. The following is an example of how to link to a heading inside the
-pack component. Take note of the `#` symbol followed by the heading id.
-
-```mdx
-<VersionedLink
-  text="Change Cluster DNS Service Domain"
-  url="/integrations/packs/?pack=kubernetes-eks#change-cluster-dns-service-domain"
-/>
-```
-
-Omit the `version=xxxx&parent=xxxx` value that is part of the query string. If you include the `version` and `parent`
-values, the link will not work as expected.
-
 ### Link to a Pack
 
 You must use the `<VersionedLink />` component to link to a pack. The following is an example of how to link to a pack.
-For more information, refer to the [Internal Links](#internal-links) section.
 
 ```mdx
 <VersionedLink text="Change Cluster DNS Service Domain" url="/integrations/packs/?pack=kubernetes-eks" />
@@ -1258,61 +1217,6 @@ new release tag is created.
 > Do not use `feat`,`perf`, `fix`, or other semantic-release key words that trigger a version change. Use the commit
 > message prefix `docs: yourMessageHere` for regular documentation commits.
 
-## Versioning
-
-> [!NOTE]
->
-> Detailed documentation for versioning can be found in the internal
-> [Versioning](https://spectrocloud.atlassian.net/wiki/spaces/DE/pages/1962639377/Versioning) guide.
-
-All versioned content belongs to a specific version branch. The version branch name follows the naming convention
-`version-X-X`. The version branch is used to generate versioned content.
-
-There are three files that are used for generating versioned content:
-
-- [`versions.sh`](./scripts/versions.sh) - A bash script that loops through all the version branches and generates the
-  versionioned content.
-
-- [`update_docusaurs_config.js`](./docsearch.config.json) - A node script that updates the `docusaurus.config.js` file
-  with all the required vesioning parameters.
-
-- [`versionsOverride.json`](./versionsOverride.json) - A JSON file that contains the versioning overrides. These values
-  are used to update the `docusaurus.config.js` file with non-default values.
-
-### Build Versioned Content Locally
-
-To build versioned content locally, use the following steps:
-
-1. Issue the following command to generate the versioned content.
-
-```shell
-make versions
-```
-
-2. Start a local development server to view the versioned content.
-
-```shell
-make start
-```
-
-3. Compile the versioned content to ensure a successful build.
-
-```shell
-make build
-```
-
-4. Remove the `versions.json` file and discard the changes to the `docusaurus.config.js` file. Use the following command
-   to remove all version artifacts.
-
-```shell
-make clean-versions
-```
-
-> [!WARNING]
->
-> The `docusaurus.config.js` file is updated by the [`update_docusaurus_config.js`](./docusaurus.config.js) script. DO
-> NOT commit this file with the updated changes.
-
 ## Exit Codes
 
 Librarium provides the following exit codes. These exit codes are returned by both the `npm run start` and

_partials/self-hosted/management-appliance/_installation-steps-prereqs.mdx

@@ -22,7 +22,7 @@ partial_name: installation-steps-prereqs
 
   - Two disks per node.
 
-    - The first disk must be at least 250 GB and is used for the {props.version} ISO stack. You specify the device in the `stylus_config.yaml` file during the initial Install {props.version} steps.
+    - The first disk must be 300 GB minimum and 500 GB is recommended. This disk is used for the {props.version} ISO stack. You specify the device in the `stylus_config.yaml` file as guided during the **Install {props.version}** steps.
 
       If the device is not specified, the default value is `auto`. This means the installer selects the largest available drive, which may not be the desired behavior, especially in multi-drive environments.
 

archiveVersions.json

@@ -1,4 +1,6 @@
 {
+  "v4.7.x": "https://version-4-7.legacy.docs.spectrocloud.com",
+  "v4.6.x": "https://version-4-6.legacy.docs.spectrocloud.com",
   "v4.5.x": "https://version-4-5.legacy.docs.spectrocloud.com",
   "v4.4.x": "https://version-4-4.legacy.docs.spectrocloud.com",
   "v4.3.x": "https://version-4-3.legacy.docs.spectrocloud.com",

docs/docs-content/clusters/public-cloud/aws/eks-hybrid-nodes/prepare-environment/prepare-edge-hosts.md

@@ -831,7 +831,7 @@ required Edge artifacts.
 15. Provision your edge hosts using the installer ISO created in the `build` directory. You can use the following
     sections to help you:
 
-    - [Provision Virtual Machines](/tutorials/clusters/edge/deploy-cluster/#provision-virtual-machines)
+    - [Provision Virtual Machines](/tutorials/clusters/edge/deploy-cluster/#provision-edge-virtual-machines)
     - [Installation on Bare Metal](../../../../edge/site-deployment/stage.md)
 
 Ensure your edge hosts are fully provisioned, configured, and active before performing [validation](#validate-1).