bottlerocket-os · piyush-jena · Apr 14, 2026 · Feb 18, 2026 · Feb 18, 2026 · Feb 18, 2026
diff --git a/.github/workflows/hugo.yaml b/.github/workflows/hugo.yaml
@@ -32,7 +32,7 @@ jobs:
     runs-on: ubuntu-latest
     env:
       # based on known good environment
-      HUGO_VERSION: 0.123.8
+      HUGO_VERSION: 0.156.0
     steps:
       - name: Install Hugo CLI
         run: |

diff --git a/Makefile b/Makefile
@@ -2,17 +2,17 @@
 
 preview:
 	docker run --rm -it \
-		-v "${PWD}":/src \
+		-v "${PWD}":/project \
 		-p 1313:1313 \
-		hugomods/hugo:exts-0.123.8 \
-		hugo server -w --bind=0.0.0.0
+		ghcr.io/gohugoio/hugo:v0.156.0 \
+		server -w --bind=0.0.0.0
 
 preview_finch:
 	finch run --rm -it \
-		-v "${PWD}":/src \
+		-v "${PWD}":/project \
 		-p 1313:1313 \
-		hugomods/hugo:exts-0.123.8 \
-		hugo server -w --bind=0.0.0.0 --poll 700ms
+		ghcr.io/gohugoio/hugo:v0.156.0 \
+		server -w --bind=0.0.0.0 --poll 700ms
 
 mdlint:
 	docker run --rm \

diff --git a/assets/scss/_variables_project.scss b/assets/scss/_variables_project.scss
@@ -43,7 +43,7 @@ $tan-link: #e96f00;
 $light: #fff;
 $light-text: #0a4158;
 $light-link: #e96f00;
-
+$yellow: #ffa630;
 /* replacement for black */
 $dark: #020e13;
 
@@ -58,7 +58,9 @@ $font-weight-bold: 600;
 
 $primary: $light;
 $body-color: $dark;
-
+// Restore bg-warning color avoiding docsy's bug where warning and danger
+// have the same colour
+$warning: $yellow;
 
 $td-sidebar-bg-color: $light;
 $td-sidebar-tree-root-color: $dark;

diff --git a/content/en/brupop/1.3.x/setup/configure/index.markdown b/content/en/brupop/1.3.x/setup/configure/index.markdown
@@ -16,7 +16,7 @@ If you choose to not use helm, refer to the {{< github-link-at-version url="http
 
 ### Label nodes
 
-{{% alert title="Warning" color="warning" %}}
+{{% alert title="Warning" color="danger" %}}
 You can fully install Brupop but if you do not apply the proper node labels the operator will not update your nodes.
 {{% /alert %}}
 

diff --git a/content/en/faqitems/6_3-troubleshooting-nvidia-bug-report.markdown b/content/en/faqitems/6_3-troubleshooting-nvidia-bug-report.markdown
@@ -0,0 +1,16 @@
++++
+question = "How do I collect NVIDIA GPU diagnostics on Bottlerocket?"
+group = "Troubleshooting"
++++
+
+The admin container includes a patched version of NVIDIA's `nvidia-bug-report.sh` that works on Bottlerocket.
+You must be running a GPU-enabled variant (e.g. `aws-k8s-*-nvidia` or `aws-ecs-*-nvidia`).
+
+Enter the admin container and run the script:
+
+```bash
+sudo nvidia-bug-report.sh
+```
+
+The script automatically detects Bottlerocket, installs needed tools, and collects GPU diagnostics.
+The output is saved as `nvidia-bug-report.log.gz` in the current directory.
diff --git a/content/en/os/1.14.x/login/regaining-access/index.markdown b/content/en/os/1.14.x/login/regaining-access/index.markdown
@@ -13,7 +13,7 @@ In some cases where both the admin and control containers are disabled, it is st
 
 In general, the solution is to mount the [API client](https://github.com/bottlerocket-os/bottlerocket/blob/develop/sources/api/apiclient/README.md) and API socket into a container on the Bottlerocket node and use the API client to re-enable the admin container, control container, or both.
 
-{{% alert title="Warning" color="warning" %}}
+{{% alert title="Warning" color="danger" %}}
 The solutions on this page provide a minimal overview.
 It involves mounting critical resources into containers with elevated privileges.
 Use carefully, only run as long as necessary, and clean up afterwards.

diff --git a/content/en/os/1.15.x/api/settings/boot/_index.markdown b/content/en/os/1.15.x/api/settings/boot/_index.markdown
@@ -5,7 +5,7 @@ toc_hide=true
 description="Settings related to kernel boot config (`settings.boot.*`)"
 +++
 
-{{% alert title="Warning" color="warning" %}}
+{{% alert title="Warning" color="danger" %}}
 Bottlerocket only allows boot configuration for `kernel` and `init`.
 If you specify any other boot config key the settings generation will fail.
 {{% /alert %}}

diff --git a/content/en/os/1.15.x/login/regaining-access/index.markdown b/content/en/os/1.15.x/login/regaining-access/index.markdown
@@ -13,7 +13,7 @@ In some cases where both the admin and control containers are disabled, it is st
 
 In general, the solution is to mount the [API client](https://github.com/bottlerocket-os/bottlerocket/blob/develop/sources/api/apiclient/README.md) and API socket into a container on the Bottlerocket node and use the API client to re-enable the admin container, control container, or both.
 
-{{% alert title="Warning" color="warning" %}}
+{{% alert title="Warning" color="danger" %}}
 The solutions on this page provide a minimal overview.
 It involves mounting critical resources into containers with elevated privileges.
 Use carefully, only run as long as necessary, and clean up afterwards.

diff --git a/content/en/os/1.16.x/api/settings/boot/_index.markdown b/content/en/os/1.16.x/api/settings/boot/_index.markdown
@@ -5,7 +5,7 @@ toc_hide=true
 description="Settings related to kernel boot config (`settings.boot.*`)"
 +++
 
-{{% alert title="Warning" color="warning" %}}
+{{% alert title="Warning" color="danger" %}}
 Bottlerocket only allows boot configuration for `kernel` and `init`.
 If you specify any other boot config key the settings generation will fail.
 {{% /alert %}}

diff --git a/content/en/os/1.16.x/login/regaining-access/index.markdown b/content/en/os/1.16.x/login/regaining-access/index.markdown
@@ -13,7 +13,7 @@ In some cases where both the admin and control containers are disabled, it is st
 
 In general, the solution is to mount the [API client](https://github.com/bottlerocket-os/bottlerocket/blob/develop/sources/api/apiclient/README.md) and API socket into a container on the Bottlerocket node and use the API client to re-enable the admin container, control container, or both.
 
-{{% alert title="Warning" color="warning" %}}
+{{% alert title="Warning" color="danger" %}}
 The solutions on this page provide a minimal overview.
 It involves mounting critical resources into containers with elevated privileges.
 Use carefully, only run as long as necessary, and clean up afterwards.

diff --git a/content/en/os/1.17.x/api/settings/boot/_index.markdown b/content/en/os/1.17.x/api/settings/boot/_index.markdown
@@ -5,7 +5,7 @@ toc_hide=true
 description="Settings related to kernel boot config (`settings.boot.*`)"
 +++
 
-{{% alert title="Warning" color="warning" %}}
+{{% alert title="Warning" color="danger" %}}
 Bottlerocket only allows boot configuration for `kernel` and `init`.
 If you specify any other boot config key the settings generation will fail.
 {{% /alert %}}

diff --git a/content/en/os/1.17.x/login/regaining-access/index.markdown b/content/en/os/1.17.x/login/regaining-access/index.markdown
@@ -13,7 +13,7 @@ In some cases where both the admin and control containers are disabled, it is st
 
 In general, the solution is to mount the [API client](https://github.com/bottlerocket-os/bottlerocket/blob/develop/sources/api/apiclient/README.md) and API socket into a container on the Bottlerocket node and use the API client to re-enable the admin container, control container, or both.
 
-{{% alert title="Warning" color="warning" %}}
+{{% alert title="Warning" color="danger" %}}
 The solutions on this page provide a minimal overview.
 It involves mounting critical resources into containers with elevated privileges.
 Use carefully, only run as long as necessary, and clean up afterwards.

diff --git a/content/en/os/1.18.x/api/settings/boot/_index.markdown b/content/en/os/1.18.x/api/settings/boot/_index.markdown
@@ -5,7 +5,7 @@ toc_hide=true
 description="Settings related to kernel boot config (`settings.boot.*`)"
 +++
 
-{{% alert title="Warning" color="warning" %}}
+{{% alert title="Warning" color="danger" %}}
 Bottlerocket only allows boot configuration for `kernel` and `init`.
 If you specify any other boot config key the settings generation will fail.
 {{% /alert %}}

diff --git a/content/en/os/1.18.x/login/regaining-access/index.markdown b/content/en/os/1.18.x/login/regaining-access/index.markdown
@@ -13,7 +13,7 @@ In some cases where both the admin and control containers are disabled, it is st
 
 In general, the solution is to mount the [API client](https://github.com/bottlerocket-os/bottlerocket/blob/develop/sources/api/apiclient/README.md) and API socket into a container on the Bottlerocket node and use the API client to re-enable the admin container, control container, or both.
 
-{{% alert title="Warning" color="warning" %}}
+{{% alert title="Warning" color="danger" %}}
 The solutions on this page provide a minimal overview.
 It involves mounting critical resources into containers with elevated privileges.
 Use carefully, only run as long as necessary, and clean up afterwards.

diff --git a/content/en/os/1.19.x/api/settings/boot/_index.markdown b/content/en/os/1.19.x/api/settings/boot/_index.markdown
@@ -5,7 +5,7 @@ toc_hide=true
 description="Settings related to kernel boot config (`settings.boot.*`)"
 +++
 
-{{% alert title="Warning" color="warning" %}}
+{{% alert title="Warning" color="danger" %}}
 Bottlerocket only allows boot configuration for `kernel` and `init`.
 If you specify any other boot config key the settings generation will fail.
 {{% /alert %}}

diff --git a/content/en/os/1.19.x/login/regaining-access/index.markdown b/content/en/os/1.19.x/login/regaining-access/index.markdown
@@ -13,7 +13,7 @@ In some cases where both the admin and control containers are disabled, it is st
 
 In general, the solution is to mount the [API client](https://github.com/bottlerocket-os/bottlerocket/blob/develop/sources/api/apiclient/README.md) and API socket into a container on the Bottlerocket node and use the API client to re-enable the admin container, control container, or both.
 
-{{% alert title="Warning" color="warning" %}}
+{{% alert title="Warning" color="danger" %}}
 The solutions on this page provide a minimal overview.
 It involves mounting critical resources into containers with elevated privileges.
 Use carefully, only run as long as necessary, and clean up afterwards.

diff --git a/content/en/os/1.20.x/api/settings/boot/_index.markdown b/content/en/os/1.20.x/api/settings/boot/_index.markdown
@@ -5,7 +5,7 @@ toc_hide=true
 description="Settings related to kernel boot config (`settings.boot.*`)"
 +++
 
-{{% alert title="Warning" color="warning" %}}
+{{% alert title="Warning" color="danger" %}}
 Bottlerocket only allows boot configuration for `kernel` and `init`.
 If you specify any other boot config key the settings generation will fail.
 {{% /alert %}}

diff --git a/content/en/os/1.20.x/login/regaining-access/index.markdown b/content/en/os/1.20.x/login/regaining-access/index.markdown
@@ -13,7 +13,7 @@ In some cases where both the admin and control containers are disabled, it is st
 
 In general, the solution is to mount the [API client](https://github.com/bottlerocket-os/bottlerocket/blob/develop/sources/api/apiclient/README.md) and API socket into a container on the Bottlerocket node and use the API client to re-enable the admin container, control container, or both.
 
-{{% alert title="Warning" color="warning" %}}
+{{% alert title="Warning" color="danger" %}}
 The solutions on this page provide a minimal overview.
 It involves mounting critical resources into containers with elevated privileges.
 Use carefully, only run as long as necessary, and clean up afterwards.

diff --git a/content/en/os/1.21.x/api/settings/boot/_index.markdown b/content/en/os/1.21.x/api/settings/boot/_index.markdown
@@ -5,7 +5,7 @@ toc_hide=true
 description="Settings related to kernel boot config (`settings.boot.*`)"
 +++
 
-{{% alert title="Warning" color="warning" %}}
+{{% alert title="Warning" color="danger" %}}
 Bottlerocket only allows boot configuration for `kernel` and `init`.
 If you specify any other boot config key the settings generation will fail.
 {{% /alert %}}

diff --git a/content/en/os/1.21.x/login/regaining-access/index.markdown b/content/en/os/1.21.x/login/regaining-access/index.markdown
@@ -13,7 +13,7 @@ In some cases where both the admin and control containers are disabled, it is st
 
 In general, the solution is to mount the [API client](https://github.com/bottlerocket-os/bottlerocket/blob/develop/sources/api/apiclient/README.md) and API socket into a container on the Bottlerocket node and use the API client to re-enable the admin container, control container, or both.
 
-{{% alert title="Warning" color="warning" %}}
+{{% alert title="Warning" color="danger" %}}
 The solutions on this page provide a minimal overview.
 It involves mounting critical resources into containers with elevated privileges.
 Use carefully, only run as long as necessary, and clean up afterwards.

diff --git a/content/en/os/1.22.x/api/settings/boot/_index.markdown b/content/en/os/1.22.x/api/settings/boot/_index.markdown
@@ -5,7 +5,7 @@ toc_hide=true
 description="Settings related to kernel boot config (`settings.boot.*`)"
 +++
 
-{{% alert title="Warning" color="warning" %}}
+{{% alert title="Warning" color="danger" %}}
 Bottlerocket only allows boot configuration for `kernel` and `init`.
 If you specify any other boot config key the settings generation will fail.
 {{% /alert %}}

diff --git a/content/en/os/1.22.x/login/regaining-access/index.markdown b/content/en/os/1.22.x/login/regaining-access/index.markdown
@@ -13,7 +13,7 @@ In some cases where both the admin and control containers are disabled, it is st
 
 In general, the solution is to mount the [API client](https://github.com/bottlerocket-os/bottlerocket/blob/develop/sources/api/apiclient/README.md) and API socket into a container on the Bottlerocket node and use the API client to re-enable the admin container, control container, or both.
 
-{{% alert title="Warning" color="warning" %}}
+{{% alert title="Warning" color="danger" %}}
 The solutions on this page provide a minimal overview.
 It involves mounting critical resources into containers with elevated privileges.
 Use carefully, only run as long as necessary, and clean up afterwards.

diff --git a/content/en/os/1.23.x/api/settings/boot/_index.markdown b/content/en/os/1.23.x/api/settings/boot/_index.markdown
@@ -5,7 +5,7 @@ toc_hide=true
 description="Settings related to kernel boot config (`settings.boot.*`)"
 +++
 
-{{% alert title="Warning" color="warning" %}}
+{{% alert title="Warning" color="danger" %}}
 Bottlerocket only allows boot configuration for `kernel` and `init`.
 If you specify any other boot config key the settings generation will fail.
 {{% /alert %}}

diff --git a/content/en/os/1.23.x/login/regaining-access/index.markdown b/content/en/os/1.23.x/login/regaining-access/index.markdown
@@ -13,7 +13,7 @@ In some cases where both the admin and control containers are disabled, it is st
 
 In general, the solution is to mount the [API client](https://github.com/bottlerocket-os/bottlerocket/blob/develop/sources/api/apiclient/README.md) and API socket into a container on the Bottlerocket node and use the API client to re-enable the admin container, control container, or both.
 
-{{% alert title="Warning" color="warning" %}}
+{{% alert title="Warning" color="danger" %}}
 The solutions on this page provide a minimal overview.
 It involves mounting critical resources into containers with elevated privileges.
 Use carefully, only run as long as necessary, and clean up afterwards.

diff --git a/content/en/os/1.24.x/api/settings/boot/_index.markdown b/content/en/os/1.24.x/api/settings/boot/_index.markdown
@@ -5,7 +5,7 @@ toc_hide=true
 description="Settings related to kernel boot config (`settings.boot.*`)"
 +++
 
-{{% alert title="Warning" color="warning" %}}
+{{% alert title="Warning" color="danger" %}}
 Bottlerocket only allows boot configuration for `kernel` and `init`.
 If you specify any other boot config key the settings generation will fail.
 {{% /alert %}}

diff --git a/content/en/os/1.24.x/login/regaining-access/index.markdown b/content/en/os/1.24.x/login/regaining-access/index.markdown
@@ -13,7 +13,7 @@ In some cases where both the admin and control containers are disabled, it is st
 
 In general, the solution is to mount the [API client](https://github.com/bottlerocket-os/bottlerocket/blob/develop/sources/api/apiclient/README.md) and API socket into a container on the Bottlerocket node and use the API client to re-enable the admin container, control container, or both.
 
-{{% alert title="Warning" color="warning" %}}
+{{% alert title="Warning" color="danger" %}}
 The solutions on this page provide a minimal overview.
 It involves mounting critical resources into containers with elevated privileges.
 Use carefully, only run as long as necessary, and clean up afterwards.

diff --git a/content/en/os/1.25.x/api/settings/boot/_index.markdown b/content/en/os/1.25.x/api/settings/boot/_index.markdown
@@ -5,7 +5,7 @@ toc_hide=true
 description="Settings related to kernel boot config (`settings.boot.*`)"
 +++
 
-{{% alert title="Warning" color="warning" %}}
+{{% alert title="Warning" color="danger" %}}
 Bottlerocket only allows boot configuration for `kernel` and `init`.
 If you specify any other boot config key the settings generation will fail.
 {{% /alert %}}

diff --git a/content/en/os/1.25.x/login/regaining-access/index.markdown b/content/en/os/1.25.x/login/regaining-access/index.markdown
@@ -13,7 +13,7 @@ In some cases where both the admin and control containers are disabled, it is st
 
 In general, the solution is to mount the [API client](https://github.com/bottlerocket-os/bottlerocket/blob/develop/sources/api/apiclient/README.md) and API socket into a container on the Bottlerocket node and use the API client to re-enable the admin container, control container, or both.
 
-{{% alert title="Warning" color="warning" %}}
+{{% alert title="Warning" color="danger" %}}
 The solutions on this page provide a minimal overview.
 It involves mounting critical resources into containers with elevated privileges.
 Use carefully, only run as long as necessary, and clean up afterwards.

diff --git a/content/en/os/1.26.x/api/settings/boot/_index.markdown b/content/en/os/1.26.x/api/settings/boot/_index.markdown
@@ -5,7 +5,7 @@ toc_hide=true
 description="Settings related to kernel boot config (`settings.boot.*`)"
 +++
 
-{{% alert title="Warning" color="warning" %}}
+{{% alert title="Warning" color="danger" %}}
 Bottlerocket only allows boot configuration for `kernel` and `init`.
 If you specify any other boot config key the settings generation will fail.
 {{% /alert %}}

diff --git a/content/en/os/1.26.x/login/regaining-access/index.markdown b/content/en/os/1.26.x/login/regaining-access/index.markdown
@@ -13,7 +13,7 @@ In some cases where both the admin and control containers are disabled, it is st
 
 In general, the solution is to mount the [API client](https://github.com/bottlerocket-os/bottlerocket/blob/develop/sources/api/apiclient/README.md) and API socket into a container on the Bottlerocket node and use the API client to re-enable the admin container, control container, or both.
 
-{{% alert title="Warning" color="warning" %}}
+{{% alert title="Warning" color="danger" %}}
 The solutions on this page provide a minimal overview.
 It involves mounting critical resources into containers with elevated privileges.
 Use carefully, only run as long as necessary, and clean up afterwards.

diff --git a/content/en/os/1.27.x/api/settings/boot/_index.markdown b/content/en/os/1.27.x/api/settings/boot/_index.markdown
@@ -5,7 +5,7 @@ toc_hide=true
 description="Settings related to kernel boot config (`settings.boot.*`)"
 +++
 
-{{% alert title="Warning" color="warning" %}}
+{{% alert title="Warning" color="danger" %}}
 Bottlerocket only allows boot configuration for `kernel` and `init`.
 If you specify any other boot config key the settings generation will fail.
 {{% /alert %}}

diff --git a/content/en/os/1.27.x/login/regaining-access/index.markdown b/content/en/os/1.27.x/login/regaining-access/index.markdown
@@ -13,7 +13,7 @@ In some cases where both the admin and control containers are disabled, it is st
 
 In general, the solution is to mount the [API client](https://github.com/bottlerocket-os/bottlerocket/blob/develop/sources/api/apiclient/README.md) and API socket into a container on the Bottlerocket node and use the API client to re-enable the admin container, control container, or both.
 
-{{% alert title="Warning" color="warning" %}}
+{{% alert title="Warning" color="danger" %}}
 The solutions on this page provide a minimal overview.
 It involves mounting critical resources into containers with elevated privileges.
 Use carefully, only run as long as necessary, and clean up afterwards.

diff --git a/content/en/os/1.28.x/api/settings/boot/_index.markdown b/content/en/os/1.28.x/api/settings/boot/_index.markdown
@@ -5,7 +5,7 @@ toc_hide=true
 description="Settings related to kernel boot config (`settings.boot.*`)"
 +++
 
-{{% alert title="Warning" color="warning" %}}
+{{% alert title="Warning" color="danger" %}}
 Bottlerocket only allows boot configuration for `kernel` and `init`.
 If you specify any other boot config key the settings generation will fail.
 {{% /alert %}}

diff --git a/content/en/os/1.28.x/login/regaining-access/index.markdown b/content/en/os/1.28.x/login/regaining-access/index.markdown
@@ -13,7 +13,7 @@ In some cases where both the admin and control containers are disabled, it is st
 
 In general, the solution is to mount the [API client](https://github.com/bottlerocket-os/bottlerocket/blob/develop/sources/api/apiclient/README.md) and API socket into a container on the Bottlerocket node and use the API client to re-enable the admin container, control container, or both.
 
-{{% alert title="Warning" color="warning" %}}
+{{% alert title="Warning" color="danger" %}}
 The solutions on this page provide a minimal overview.
 It involves mounting critical resources into containers with elevated privileges.
 Use carefully, only run as long as necessary, and clean up afterwards.

diff --git a/content/en/os/1.29.x/api/settings/boot/_index.markdown b/content/en/os/1.29.x/api/settings/boot/_index.markdown
@@ -5,7 +5,7 @@ toc_hide=true
 description="Settings related to kernel boot config (`settings.boot.*`)"
 +++
 
-{{% alert title="Warning" color="warning" %}}
+{{% alert title="Warning" color="danger" %}}
 Bottlerocket only allows boot configuration for `kernel` and `init`.
 If you specify any other boot config key the settings generation will fail.
 {{% /alert %}}

diff --git a/content/en/os/1.29.x/login/regaining-access/index.markdown b/content/en/os/1.29.x/login/regaining-access/index.markdown
@@ -13,7 +13,7 @@ In some cases where both the admin and control containers are disabled, it is st
 
 In general, the solution is to mount the [API client](https://github.com/bottlerocket-os/bottlerocket/blob/develop/sources/api/apiclient/README.md) and API socket into a container on the Bottlerocket node and use the API client to re-enable the admin container, control container, or both.
 
-{{% alert title="Warning" color="warning" %}}
+{{% alert title="Warning" color="danger" %}}
 The solutions on this page provide a minimal overview.
 It involves mounting critical resources into containers with elevated privileges.
 Use carefully, only run as long as necessary, and clean up afterwards.

diff --git a/content/en/os/1.30.x/api/settings/boot/_index.markdown b/content/en/os/1.30.x/api/settings/boot/_index.markdown
@@ -5,7 +5,7 @@ toc_hide=true
 description="Settings related to kernel boot config (`settings.boot.*`)"
 +++
 
-{{% alert title="Warning" color="warning" %}}
+{{% alert title="Warning" color="danger" %}}
 Bottlerocket only allows boot configuration for `kernel` and `init`.
 If you specify any other boot config key the settings generation will fail.
 {{% /alert %}}

diff --git a/content/en/os/1.30.x/login/regaining-access/index.markdown b/content/en/os/1.30.x/login/regaining-access/index.markdown
@@ -13,7 +13,7 @@ In some cases where both the admin and control containers are disabled, it is st
 
 In general, the solution is to mount the [API client](https://github.com/bottlerocket-os/bottlerocket/blob/develop/sources/api/apiclient/README.md) and API socket into a container on the Bottlerocket node and use the API client to re-enable the admin container, control container, or both.
 
-{{% alert title="Warning" color="warning" %}}
+{{% alert title="Warning" color="danger" %}}
 The solutions on this page provide a minimal overview.
 It involves mounting critical resources into containers with elevated privileges.
 Use carefully, only run as long as necessary, and clean up afterwards.

diff --git a/content/en/os/1.31.x/api/settings/boot/_index.markdown b/content/en/os/1.31.x/api/settings/boot/_index.markdown
@@ -5,7 +5,7 @@ toc_hide=true
 description="Settings related to kernel boot config (`settings.boot.*`)"
 +++
 
-{{% alert title="Warning" color="warning" %}}
+{{% alert title="Warning" color="danger" %}}
 Bottlerocket only allows boot configuration for `kernel` and `init`.
 If you specify any other boot config key the settings generation will fail.
 {{% /alert %}}