From 03d3d4f6e473bb5d88a1f218d77faef03319e84c Mon Sep 17 00:00:00 2001 From: Amber Alston Date: Fri, 29 Aug 2025 10:19:48 -0600 Subject: [PATCH 1/2] Making it clearer strict works with EC too --- docs/vendor/preflight-support-bundle-about.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/vendor/preflight-support-bundle-about.mdx b/docs/vendor/preflight-support-bundle-about.mdx index a5e3fb99aa..c200929c3f 100644 --- a/docs/vendor/preflight-support-bundle-about.mdx +++ b/docs/vendor/preflight-support-bundle-about.mdx @@ -77,7 +77,7 @@ For information about how to add preflight checks to your application, including ### Blocking Installation with Required (Strict) Preflights -For applications installed with KOTS, it is possible to block the deployment of a release if a preflight check fails. This is helpful when it is necessary to prevent an installation or upgrade from continuing unless a given requirement is met. +For applications installed with KOTS or Embedded Cluster, it is possible to block the deployment of a release if a preflight check fails. This is helpful when it is necessary to prevent an installation or upgrade from continuing unless a given requirement is met. You can add required preflight checks for an application by including `strict: true` for the target analyzer in the preflight specification. For more information, see [Block Installation with Required (Strict) Preflights](preflight-defining#strict) in _Define Preflight Checks_. @@ -148,4 +148,4 @@ For more information, see [Add and Customize Support Bundles](support-bundle-cus Users generate support bundles as `tar.gz` files from the command line, using the support-bundle kubectl plugin. Your customers can share their support bundles with your team by sending you the resulting `tar.gz` file. KOTS users can also generate and share support bundles from the KOTS Admin Console. -For more information, see [Generate Support Bundles](support-bundle-generating). \ No newline at end of file +For more information, see [Generate Support Bundles](support-bundle-generating). From aea50c69a13837cdf6e163e7941e891077337c77 Mon Sep 17 00:00:00 2001 From: Amber Alston Date: Fri, 29 Aug 2025 10:21:30 -0600 Subject: [PATCH 2/2] Update preflight-defining.mdx --- docs/vendor/preflight-defining.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/vendor/preflight-defining.mdx b/docs/vendor/preflight-defining.mdx index c5b5c77af8..5fa63d1a79 100644 --- a/docs/vendor/preflight-defining.mdx +++ b/docs/vendor/preflight-defining.mdx @@ -105,7 +105,7 @@ To view all the available analyzers, see the [Analyze](https://troubleshoot.sh/d ### Block Installation with Required (Strict) Preflights {#strict} -For applications installed with KOTS, you can set any preflight analyzer to `strict: true`. When `strict: true` is set, any `fail` outcomes for the analyzer block the deployment of the release. +For applications installed with KOTS or Embedded Cluster, you can set any preflight analyzer to `strict: true`. When `strict: true` is set, any `fail` outcomes for the analyzer block the deployment of the release. :::note Strict preflight analyzers are ignored if the `exclude` property is also included and evaluates to `true`. See [exclude](https://troubleshoot.sh/docs/analyze/#exclude) in the Troubleshoot documentation. @@ -113,4 +113,4 @@ Strict preflight analyzers are ignored if the `exclude` property is also include ### Examples -For common examples of collectors and analyzers used in preflight checks, see [Examples of Preflight Specs](/vendor/preflight-examples). \ No newline at end of file +For common examples of collectors and analyzers used in preflight checks, see [Examples of Preflight Specs](/vendor/preflight-examples).