Skip to content

Commit 1974ba4

Browse files
committed
xref edits
1 parent ee82863 commit 1974ba4

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

docs/vendor/replicated-onboarding.mdx

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -284,6 +284,7 @@ To set up the Admin Console Config screen for your application:
284284
For more information, see:
285285
* [Mapping User-Supplied Values](/vendor/config-screen-map-inputs)
286286
* [Tutorial: Set Helm Chart Values with KOTS](/vendor/tutorial-config-setup)
287+
* [Setting Helm Values with KOTS](/vendor/helm-optional-value-keys)
287288
* [`values`](/reference/custom-resource-helmchart-v2#values) in _HelmChart v2_
288289

289290
1. <CreateRelease/>
@@ -308,7 +309,7 @@ Before you begin this task, you can complete the [Add Preflight Checks to a Helm
308309

309310
To define preflight checks for your application:
310311

311-
1. In your Helm chart `templates` directory, add a Kubernetes Secret that includes a preflight spec. For more information, see [Defining Preflight Checks](/vendor/preflight-defining).
312+
1. In your Helm chart `templates` directory, add a Kubernetes Secret that includes a preflight spec. For more information, see [Defining Preflight Checks](/vendor/preflight-defining). For examples, see [Example Preflight Specs](/vendor/preflight-examples).
312313
:::note
313314
If your application is deployed as multiple Helm charts, add the Secret to the `templates` directory for the chart that is installed first.
314315
:::
@@ -356,7 +357,7 @@ To add the default support bundle spec to your application:
356357

357358
1. (Recommended) At a minimum, Replicated recommends that all support bundle specs include the `logs` collector. This collects logs from running Pods in the cluster.
358359

359-
For example:
360+
**Example:**
360361

361362
```yaml
362363
apiVersion: v1
@@ -383,7 +384,8 @@ To add the default support bundle spec to your application:
383384
```
384385

385386
For more information, see:
386-
* <a href="/vendor/support-bundle-customizing">Adding and Customizing Support Bundles</a>
387+
* [Adding and Customizing Support Bundles](/vendor/support-bundle-customizing)
388+
* [Example Support Bundle Specs](/vendor/support-bundle-examples)
387389
* [Pod Logs](https://troubleshoot.sh/docs/collect/logs/) in the Troubleshoot documentation.
388390

389391
1. (Recommended) Ensure that any preflight checks that you added are also include in your support bundle spec. This ensures that support bundles collect at least the same information collected when running preflight checks.
@@ -400,7 +402,7 @@ To add the default support bundle spec to your application:
400402

401403
For information about how to generate support bundles, see [Generating Support Bundles](/vendor/support-bundle-generating).
402404

403-
1. (Optional) Customize the support bundle spec by adding additional collectors and analyzers. You can also choose to do this later. See [Step 2: Customize the Spec](/vendor/support-bundle-customizing#customize-the-spec) in _Adding and Customizing Support Bundles_.
405+
1. (Optional) Customize the support bundle spec by adding additional collectors and analyzers.
404406

405407
### Task 9: Alias Replicated Endpoints with Your Own Domains
406408

0 commit comments

Comments
 (0)