From acaf1ff106763bd55c0508b86711a318566ff211 Mon Sep 17 00:00:00 2001 From: jaradtke-aws Date: Mon, 22 Jul 2024 10:25:04 -0400 Subject: [PATCH] Added verbiage about infra-specific commands --- .../en/docs/troubleshooting/troubleshooting.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/content/en/docs/troubleshooting/troubleshooting.md b/docs/content/en/docs/troubleshooting/troubleshooting.md index 6baf6e289446..dd7195e699d9 100755 --- a/docs/content/en/docs/troubleshooting/troubleshooting.md +++ b/docs/content/en/docs/troubleshooting/troubleshooting.md @@ -33,6 +33,18 @@ More information on troubleshooting EKS Anywhere is available from the [AWS Know ## General troubleshooting +### Infrastructure-specific commands and output (vSphere vs Bare Metal, for example) + +You may need to adapt the commands in the troubleshooting examples provided on this page for the infrastructure you are using. +Here are examples of what you may see depending on which infrastrurcture you are deploying to: + +* capi-system (General) +* capv-system (vSphere) +* capc-system (CloudStack) +* capv-system (Nutanix) +* capd-system (Docker) +* capt-system (Tinkerbell) + ### Increase eksctl anywhere output If you’re having trouble running `eksctl anywhere` you may get more verbose output with the `-v 6` option. The highest level of verbosity is `-v 9` and the default level of logging is level equivalent to `-v 0`.