Repository: spectrocloud/librarium
Pull request #6781: docs: Edge troubleshooting scripts
Author: login: svetlana-efimova
Labels: name: auto-backport
description: Enable backport
name: backport-version-4-2
description: Backport change to version 4.2
name: backport-version-4-3
description: Backport change to version 4.3
name: released
name: backport-version-4-4
description: Backport change to version 4.4
name: backport-version-4-5
description: Backport change to version 4.5
name: backport-version-4-6
description: Backport change to version 4.6
Created: 2025-05-13T17:52:15Z | Merged: 2025-05-13T21:59:00Z

## Describe the Change

<!-- Add a description of what the pull request is changing, adding, and any other relevant context.  -->

This PR adds a page with the information about the following scripts used to troubleshoot Edge clusters:
- `support-bundle-infra.sh`
- `support-bundle-edge.sh`

## Changed Pages

<!-- Add a link to the preview URL generated by Netlify. Include direct links to the pages affected by the PR. -->

💻 [Collect Support Bundles for Edge Cluster Troubleshooting](https://deploy-preview-6781--docs-spectrocloud.netlify.app/troubleshooting/edge/collect-support-bundles/)

## Jira Tickets

<!-- Add a link to the JIRA tickets (if applicable) -->

🎫 [Jira Ticket](https://spectrocloud.atlassian.net/browse/PE-6675)

## Backports

<!-- Add the relevant backport labels to reflect which versions of the docs your changes will affect. -->

Can this PR be backported?

- [x] Yes. _Remember to add the relevant backport labels to your PR._
- [ ] No. _Please leave a short comment below about why this PR cannot be backported._



Diff:
diff --git a/docs/docs-content/clusters/edge/edgeforge-workflow/palette-canvos/fips.md b/docs/docs-content/clusters/edge/edgeforge-workflow/palette-canvos/fips.md
index d708ee16d5e..fafd9760797 100644
--- a/docs/docs-content/clusters/edge/edgeforge-workflow/palette-canvos/fips.md
+++ b/docs/docs-content/clusters/edge/edgeforge-workflow/palette-canvos/fips.md
@@ -117,7 +117,7 @@ image with.
 When you create a cluster with an Edge host that operates the FIPS-compliant RHEL Operating System (OS), you may
 encounter an error where the `systemd-resolved.service` service enters the **failed** state. This prevents the
 nameserver from being configured, which will result in cluster deployment failure. Refer to
-[TroubleShooting](../../../../troubleshooting/edge.md#scenario---systemd-resolvedservice-enters-failed-state) for a
+[TroubleShooting](../../../../troubleshooting/edge/edge.md#scenario---systemd-resolvedservice-enters-failed-state) for a
 workaround.
 
 :::
diff --git a/docs/docs-content/clusters/edge/networking/vxlan-overlay.md b/docs/docs-content/clusters/edge/networking/vxlan-overlay.md
index a831c9f2e7b..508e57811c8 100644
--- a/docs/docs-content/clusters/edge/networking/vxlan-overlay.md
+++ b/docs/docs-content/clusters/edge/networking/vxlan-overlay.md
@@ -236,4 +236,4 @@ You can access a cluster with overlay network enabled in the following ways:
 ## Resources
 
 - [Publish Cluster Services with Kube-vip](kubevip.md)
-- [Troubleshooting - Edge](../../../troubleshooting/edge.md)
+- [Troubleshooting - Edge](../../../troubleshooting/edge/edge.md)
diff --git a/docs/docs-content/deployment-modes/agent-mode/install-agent-host.md b/docs/docs-content/deployment-modes/agent-mode/install-agent-host.md
index c0b0ae0f92b..a55609eb0c2 100644
--- a/docs/docs-content/deployment-modes/agent-mode/install-agent-host.md
+++ b/docs/docs-content/deployment-modes/agent-mode/install-agent-host.md
@@ -549,8 +549,8 @@ Palette. You will then create a cluster profile and use the registered host to d
 If using the FIPS version of Agent Mode on a Rocky Linux edge host, SELinux may incorrectly label the
 **kubeadm-flags.env** file during cluster deployment or when certain configurations are adjusted, preventing the Kubelet
 from accessing it and properly managing the cluster. Refer to the
-[Edge Troubleshooting Guide](../../troubleshooting/edge.md#scenario---kubelet-process-cannot-access-kubeadm-flags) for
-guidance.
+[Edge Troubleshooting Guide](../../troubleshooting/edge/edge.md#scenario---kubelet-process-cannot-access-kubeadm-flags)
+for guidance.
 
 :::
 
@@ -719,8 +719,8 @@ internet.
 If using the FIPS version of Agent Mode on a Rocky Linux edge host, SELinux may incorrectly label the
 **kubeadm-flags.env** file during cluster deployment or when certain configurations are adjusted, preventing the Kubelet
 from accessing it and properly managing the cluster. Refer to the
-[Edge Troubleshooting Guide](../../troubleshooting/edge.md#scenario---kubelet-process-cannot-access-kubeadm-flags) for
-guidance.
+[Edge Troubleshooting Guide](../../troubleshooting/edge/edge.md#scenario---kubelet-process-cannot-access-kubeadm-flags)
+for guidance.
 
 :::
 
diff --git a/docs/docs-content/release-notes/known-issues.md b/docs/docs-content/release-notes/known-issues.md
index a777b766516..cab6cbd418d 100644
--- a/docs/docs-content/release-notes/known-issues.md
+++ b/docs/docs-content/release-notes/known-issues.md
@@ -25,9 +25,9 @@ The following table lists all known issues that are currently active and affecti
 | [MAAS](../clusters/data-center/maas/maas.md) and [VMware vSphere](../clusters/data-center/vmware/vmware.md) clusters fail to provision on existing self-hosted Palette and VerteX environments deployed with Palette 4.2.13 or later. These installations have an incorrectly configured default image endpoint, which causes image resolution to fail. New self-hosted installations are not affected.                                                                                                                                                                                                             | Refer to [Troubleshooting](../troubleshooting/enterprise-install.md#scenario---maas-and-vmware-vsphere-clusters-fail-image-resolution-in-non-airgap-environments) for a workaround for non-airgap environments. For airgap environments, ensure that the images are downloaded to your environment. Refer to the [Additional OVAs](../downloads/self-hosted-palette/additional-ovas.md) page for further details.                                                                                                                                                                                                | February 16, 2025  | Self-Hosted, Clusters        |
 | <!-- prettier-ignore-start --> Performing a <VersionedLink text="MicroK8s" url="/integrations/packs/?pack=kubernetes-microk8s"/> `InPlaceUpgrade` from version 1.28 to 1.29 on active MAAS and AWS clusters with Cilium prevents new pods from being deployed on control plane nodes due to an [upstream issue](https://github.com/canonical/cluster-api-control-plane-provider-microk8s/issues/74) with Canonical. This issue also occurs when performing a MicroK8s `SmartUpgrade` from version 1.28 to 1.29 on active MAAS and AWS clusters with one control plane node and Cilium. <!-- prettier-ignore-end --> | Manually restart the Cilium pods on _each_ control plane node using the command `microk8s kubectl rollout restart daemonset cilium --namespace kube-system`.                                                                                                                                                                                                                                                                                                                                                                                                                                                     | February 16, 2025  | Clusters, Packs              |
 | For clusters deployed with [Virtual Machine Orchestrator (VMO)](../vm-management/vm-management.md), namespaces on the **Virtual Machine** tab cannot be viewed by users with any `spectro-vm` cluster role.                                                                                                                                                                                                                                                                                                                                                                                                         | Add the `spectro-namespace-list` cluster role to users who need to view virtual machines and virtual machine namespaces. Refer to the [Add Roles and Role Bindings](../vm-management/rbac/add-roles-and-role-bindings.md) guide for instructions on how to add roles for VMO clusters.                                                                                                                                                                                                                                                                                                                           | February 5, 2025   | Virtual Machine Orchestrator |
-| For clusters deployed with <VersionedLink text="Palette eXtended Kubernetes - Edge (PXK-E)" url="/integrations/packs/?pack=edge-k8s"/> and [agent mode](../deployment-modes/agent-mode/agent-mode.md), the contents of the `/opt/cni/bin` folder are not set correctly, causing cluster deployment issues because the cluster network cannot come up.                                                                                                                                                                                                                                                               | Refer to [Troubleshooting](../troubleshooting/edge.md#scenario---agent-mode-deployments-cni-folder-permission-issues) for a workaround.                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | January 30, 2025   | Palette agent                |
+| For clusters deployed with <VersionedLink text="Palette eXtended Kubernetes - Edge (PXK-E)" url="/integrations/packs/?pack=edge-k8s"/> and [agent mode](../deployment-modes/agent-mode/agent-mode.md), the contents of the `/opt/cni/bin` folder are not set correctly, causing cluster deployment issues because the cluster network cannot come up.                                                                                                                                                                                                                                                               | Refer to [Troubleshooting](../troubleshooting/edge/edge.md#scenario---agent-mode-deployments-cni-folder-permission-issues) for a workaround.                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | January 30, 2025   | Palette agent                |
 | Palette [workload clusters](../glossary-all.md#workload-cluster) deployed with Calico version 3.28.2, 3.29.0, or 3.29.1 are experiencing memory leaks due to an [upstream issue](https://github.com/projectcalico/calico/pull/9612) with Calico, which is caused by failing to close netlink handles.                                                                                                                                                                                                                                                                                                               | [Create a new profile version](../profiles/cluster-profiles/modify-cluster-profiles/version-cluster-profile.md) using Calico version 3.28.0 or 3.28.1 and [update your cluster](../clusters/cluster-management/cluster-updates.md#update-a-cluster).                                                                                                                                                                                                                                                                                                                                                             | January 27, 2025   | Clusters, Packs              |
-| For clusters deployed with <VersionedLink text="Palette eXtended Kubernetes - Edge (PXK-E)" url="/integrations/packs/?pack=edge-k8s"/> and [agent mode](../deployment-modes/agent-mode/agent-mode.md) on Palette agent version 4.5.14, adding a custom `stylus.path` to the **user-data** file causes cluster creation to fail as it cannot find [kubeadm](https://kubernetes.io/docs/reference/setup-tools/kubeadm/).                                                                                                                                                                                              | Review the [Edge Troubleshooting](../troubleshooting/edge.md) section for workarounds. Refer to [Identify the Target Agent Version](../clusters/edge/cluster-management/agent-upgrade-airgap.md#identify-the-target-agent-version) for guidance in retrieving your Palette agent version number.                                                                                                                                                                                                                                                                                                                 | January 19, 2025   | Edge                         |
+| For clusters deployed with <VersionedLink text="Palette eXtended Kubernetes - Edge (PXK-E)" url="/integrations/packs/?pack=edge-k8s"/> and [agent mode](../deployment-modes/agent-mode/agent-mode.md) on Palette agent version 4.5.14, adding a custom `stylus.path` to the **user-data** file causes cluster creation to fail as it cannot find [kubeadm](https://kubernetes.io/docs/reference/setup-tools/kubeadm/).                                                                                                                                                                                              | Review the [Edge Troubleshooting](../troubleshooting/edge/edge.md) section for workarounds. Refer to [Identify the Target Agent Version](../clusters/edge/cluster-management/agent-upgrade-airgap.md#identify-the-target-agent-version) for guidance in retrieving your Palette agent version number.                                                                                                                                                                                                                                                                                                            | January 19, 2025   | Edge                         |
 | For clusters deployed with <VersionedLink text="Palette eXtended Kubernetes - Edge (PXK-E)" url="/integrations/packs/?pack=edge-k8s"/> and [agent mode](../deployment-modes/agent-mode/agent-mode.md), upgrades to higher Kubernetes versions are not supported with Palette agent version 4.5.12 or earlier.                                                                                                                                                                                                                                                                                                       | No workaround available. Upgrades to higher Kubernetes versions are only supported from Palette agent version 4.5.14 and above for clusters deployed with PXK-E and agent mode. Refer to [Identify the Target Agent Version](../clusters/edge/cluster-management/agent-upgrade-airgap.md#identify-the-target-agent-version) for guidance in retrieving your Palette agent version number.                                                                                                                                                                                                                        | January 19, 2025   | Edge                         |
 | Transferring the management of a local Edge cluster to central management by Palette or VerteX is not supported for multi-node clusters.                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No workaround is available.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | January 19, 2025   | Edge                         |
 | Edits on the [Hybrid Profile](../clusters/public-cloud/aws/eks-hybrid-nodes/create-hybrid-node-pools.md#create-node-pool) of an [EKS Hybrid node pool](../clusters/public-cloud/aws/eks-hybrid-nodes/eks-hybrid-nodes.md) take effect as soon as you click the **Save** button on the **Configure Profile** tab, not when you click **Confirm** on the **Edit node pool** screen.                                                                                                                                                                                                                                   | No workaround available.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | January 19, 2025   | Clusters                     |
@@ -46,7 +46,7 @@ The following table lists all known issues that are currently active and affecti
 | The resource limits on Palette Virtual Clusters are too low and may cause the Palette agent to experience resource exhaustion. As a result, Palette pods required for Palette operations may experience Out-of-Memory (OOM) errors.                                                                                                                                                                                                                                                                                                                                                                                 | Refer to the [Apply Host Cluster Resource Limits to Virtual Cluster](../troubleshooting/palette-dev-engine.md#scenario---apply-host-cluster-resource-limits-to-virtual-cluster) guide for workaround steps.                                                                                                                                                                                                                                                                                                                                                                                                      | November 4, 2024   | Virtual Clusters             |
 | <!-- prettier-ignore-start --> Palette incorrectly modifies the indentation of the <VersionedLink text="Prometheus Operator" url="/integrations/packs/?pack=prometheus-operator"/> pack after it is configured as a cluster profile layer. The modified indentation does not cause errors, but you may observe changes to the pack **values.yaml**. <!-- prettier-ignore-end-->                                                                                                                                                                                                                                     | No workaround available.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | October 30, 2024   | Cluster Profiles, Pack       |
 | Palette does not correctly configure multiple search domains when provided during the self-hosted installation. The configuration file **resolve.conf** ends up containing incorrect values.                                                                                                                                                                                                                                                                                                                                                                                                                        | Connect remotely to each node in the Palette self-hosted instance and edit the **resolution.conf** configuration file.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | October 17, 2024   | Self-Hosted, PCG             |
-| Upgrading the RKE2 version from 1.29 to 1.30 fails due to [an upstream issue](https://github.com/rancher/rancher/issues/46726) with RKE2 and Cilium.                                                                                                                                                                                                                                                                                                                                                                                                                                                                | Refer to the [Troubleshooting section](../troubleshooting/edge.md#scenario---clusters-with-cilium-and-rke2-experiences-kubernetes-upgrade-failure) for the workaround.                                                                                                                                                                                                                                                                                                                                                                                                                                           | October 12, 2024   | Edge                         |
+| Upgrading the RKE2 version from 1.29 to 1.30 fails due to [an upstream issue](https://github.com/rancher/rancher/issues/46726) with RKE2 and Cilium.                                                                                                                                                                                                                                                                                                                                                                                                                                                                | Refer to the [Troubleshooting section](../troubleshooting/edge/edge.md#scenario---clusters-with-cilium-and-rke2-experiences-kubernetes-upgrade-failure) for the workaround.                                                                                                                                                                                                                                                                                                                                                                                                                                      | October 12, 2024   | Edge                         |
 | Kubernetes clusters deployed on MAAS with Microk8s are experiencing deployment issues when using the upgrade strategy `RollingUpgrade`. This issue is affecting new cluster deployments and node provisioning.                                                                                                                                                                                                                                                                                                                                                                                                      | Use the `InPlaceUpgrade` strategy to upgrade nodes deployed in MAAS.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | October 12, 2024   | Clusters, Pack               |
 | Clusters using Mircrok8s and conducting backup and restore operations using Velero with [restic](https://github.com/restic/restic) are encountering restic pods going into the `crashloopbackoff` state. This issue stems from an upstream problem in the Velero project. You can learn more about it in the GitHub issue [4035](https://github.com/vmware-tanzu/velero/issues/4035) page.                                                                                                                                                                                                                          | <!-- prettier-ignore -->  Refer to the <VersionedLink text="MicroK8s" url="/integrations/packs/?pack=kubernetes-microk8s" /> Additional Details section for troubleshooting workaround steps.                                                                                                                                                                                                                                                                                                                                                                                                                    | October 12, 2024   | Clusters                     |
 | <!-- prettier-ignore --> Clusters deployed with Microk8s cannot accept kubectl commands if the <VersionedLink text="Spectro Proxy" url="/integrations/packs/?pack=spectro-proxy" /> pack is added to the cluster's cluster profile. The reason behind this issue is Microk8s' lack of support for `certSANs`. This causes the Kubernetes API server to reject Spectro Proxy certificates. Check out GitHub issue [114](https://github.com/canonical/cluster-api-bootstrap-provider-microk8s/issues/114) in the MircoK8s cluster-api-bootstrap-provider-microk8s repository to learn more.                           | Use the [admin kubeconfig file](../clusters/cluster-management/kubeconfig.md#kubeconfig-files) to access the cluster API, as it does not use the Spectro Proxy server. This option may be limited to environments where you can access the cluster directly from a network perspective.                                                                                                                                                                                                                                                                                                                          | October 1, 2024    | Clusters, Pack               |
@@ -58,7 +58,7 @@ The following table lists all known issues that are currently active and affecti
 | Palette OVA import operations fail if the VMO cluster is using a storageClass with the volume bind method `WaitForFirstConsumer`.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Refer to the [OVA Imports Fail Due To Storage Class Attribute](../troubleshooting/vmo-issues.md#scenario---ova-imports-fail-due-to-storage-class-attribute) troubleshooting guide for workaround steps.                                                                                                                                                                                                                                                                                                                                                                                                          | September 13, 2024 | Palette CLI, VMO             |
 | Persistent Volume Claims (PVCs) metadata do not use a unique identifier for self-hosted Palette clusters. This causes incorrect Cloud Native Storage (CNS) mappings in vSphere, potentially leading to issues during node operations and cluster upgrades.                                                                                                                                                                                                                                                                                                                                                          | Refer to the [Troubleshooting section](../troubleshooting/enterprise-install.md#scenario---non-unique-vsphere-cns-mapping) for guidance.                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | September 13, 2024 | Self-hosted                  |
 | Third-party binaries downloaded and used by the Palette CLI may become stale and incompatible with the CLI.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Refer to the [Incompatible Stale Palette CLI Binaries](../troubleshooting/automation.md#scenario---incompatible-stale-palette-cli-binaries) troubleshooting guide for workaround guidance.                                                                                                                                                                                                                                                                                                                                                                                                                       | September 11, 2024 | CLI                          |
-| An issue with Edge hosts using [Trusted Boot](../clusters/edge/trusted-boot/trusted-boot.md) and encrypted drives occurs when TRIM is not enabled. As a result, Solid-State Drive and Nonvolatile Memory Express drives experience degraded performance and potentially cause cluster failures. This [issue](https://github.com/kairos-io/kairos/issues/2693) stems from [Kairos](https://kairos.io/) not passing through the `--allow-discards` flag to the `systemd-cryptsetup attach` command.                                                                                                                   | Check out the [Degraded Performance on Disk Drives](../troubleshooting/edge.md#scenario---degraded-performance-on-disk-drives) troubleshooting guide for guidance on workaround.                                                                                                                                                                                                                                                                                                                                                                                                                                 | September 4, 2024  | Edge                         |
+| An issue with Edge hosts using [Trusted Boot](../clusters/edge/trusted-boot/trusted-boot.md) and encrypted drives occurs when TRIM is not enabled. As a result, Solid-State Drive and Nonvolatile Memory Express drives experience degraded performance and potentially cause cluster failures. This [issue](https://github.com/kairos-io/kairos/issues/2693) stems from [Kairos](https://kairos.io/) not passing through the `--allow-discards` flag to the `systemd-cryptsetup attach` command.                                                                                                                   | Check out the [Degraded Performance on Disk Drives](../troubleshooting/edge/edge.md#scenario---degraded-performance-on-disk-drives) troubleshooting guide for guidance on workaround.                                                                                                                                                                                                                                                                                                                                                                                                                            | September 4, 2024  | Edge                         |
 | The AWS CSI pack has a [Pod Disruption Budget](https://kubernetes.io/docs/tasks/run-application/configure-pdb/) (PDB) that allows for a maximum of one unavailable pod. This behavior causes an issue for single-node clusters as well as clusters with a single control plane node and a single worker node where the control plane lacks worker capability. [Operating System (OS) patch](../clusters/cluster-management/os-patching.md) updates may attempt to evict the CSI controller without success, resulting in the node remaining in the un-schedulable state.                                            | If OS patching is enabled, allow the control plane nodes to have worker capability. For single-node clusters, turn off the OS patching feature.                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | September 4, 2024  | Cluster, Packs               |
 | On AWS IaaS Microk8s clusters, OS patching can get stuck and fail.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Refer to the [Troubleshooting](../troubleshooting/nodes.md#os-patch-fails-on-aws-with-microk8s-127) section for debug steps.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | August 17, 2024    | Palette                      |
 | When upgrading a self-hosted Palette instance from 4.3 to 4.4 the MongoDB pod may be stuck with the following error: `ReadConcernMajorityNotAvailableYet: Read concern majority reads are currently not possible.`                                                                                                                                                                                                                                                                                                                                                                                                  | Delete the PVC, PV and the pod manually. All resources will be recreated with the correct configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | August 17, 2024    | Self-Hosted Palette          |
@@ -69,7 +69,7 @@ The following table lists all known issues that are currently active and affecti
 | Single-node Private Cloud Gateway (PCG) clusters are experiencing an issue upgrading to 4.4.11. The vSphere CSI controller pod fails to start because there are no matching affinity rules.                                                                                                                                                                                                                                                                                                                                                                                                                         | Check out the [vSphere Controller Pod Fails to Start in Single Node PCG Cluster](../troubleshooting/pcg.md#scenario---vsphere-controller-pod-fails-to-start-in-single-node-pcg-cluster) guide for workaround steps.                                                                                                                                                                                                                                                                                                                                                                                              | July 20, 2024      | PCG                          |
 | When provisioning an Edge cluster, it's possible that some Operating System (OS) user credentials will be lost once the cluster is active. This is because the cloud-init stages from different sources merge during the deployment process, and sometimes, the same stages without distinct names overwrite each other.                                                                                                                                                                                                                                                                                            | Give each of your cloud-init stages in the OS pack and in the Edge installer **user-data** file a unique name. For more information about cloud-init stages and examples of cloud-init stages with names, refer to [Cloud-init Stages](../clusters/edge/edge-configuration/cloud-init.md).                                                                                                                                                                                                                                                                                                                       | July 17, 2024      | Edge                         |
 | When you use a content bundle to provision a new cluster without using the local Harbor registry, it's possible for the images to be pulled from external networks instead of from the content bundle, consuming network bandwidth. If your Edge host has no connection to external networks or if it cannot locate the image on a remote registry, some pods may enter the `ImagePullBackOff` state at first, but eventually the pods will be created using images from the content bundle.                                                                                                                        | For connected clusters, you can make sure that the remote images are not reachable by the Edge host, which will stop the Palette agent from downloading the image and consuming bandwidth, and eventually the cluster will be created using images from the content bundle. For airgap clusters, the `ImagePullBackOff` error will eventually resolve on its own and there is no action to take.                                                                                                                                                                                                                 | July 11, 2024      | Edge                         |
-| When you add a new VMware vSphere Edge host to an Edge cluster, the IP address may fail to be assigned to the Edge host after a reboot.                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Review the [Edge Troubleshooting](../troubleshooting/edge.md) section for workarounds.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | July 9, 2024       | Edge                         |
+| When you add a new VMware vSphere Edge host to an Edge cluster, the IP address may fail to be assigned to the Edge host after a reboot.                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Review the [Edge Troubleshooting](../troubleshooting/edge/edge.md) section for workarounds.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | July 9, 2024       | Edge                         |
 | When you install Palette Edge using an Edge Installer ISO with a RHEL 8 operating system on a Virtual Machine (VM) with insufficient video memory, the QR code in the registration screen does not display correctly.                                                                                                                                                                                                                                                                                                                                                                                               | Increase the video memory of your VM to 8 MB or higher. The steps to do this vary depending on the platform you use to deploy your VM. In vSphere, you can right click on the VM, click **Edit Settings** and adjust the video card memory in the **Video card** tab.                                                                                                                                                                                                                                                                                                                                            | July 9, 2024       | Edge                         |
 | Custom Certificate Authority (CA) is not supported for accessing Azure AKS clusters. Using a custom CA prevents the `spectro-proxy` pack from working correctly with Azure AKS clusters.                                                                                                                                                                                                                                                                                                                                                                                                                            | No workaround is available.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | July 9, 2024       | Packs, Clusters              |
 | Manifests attached to an Infrastructure Pack, such as OS, Kubernetes, Network, or Storage, are not applied to the Edge cluster. This issue does not impact the infrastructure pack's YAML definition, which is applied to the cluster.                                                                                                                                                                                                                                                                                                                                                                              | Specify custom configurations through an add-on pack or a custom manifest pack applied after the infrastructure packs.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | Jul 9, 2024        | Edge, Packs                  |
@@ -77,7 +77,7 @@ The following table lists all known issues that are currently active and affecti
 | [Sonobuoy](../clusters/cluster-management/compliance-scan.md#conformance-testing) scans fail to generate reports on airgapped Palette Edge clusters.                                                                                                                                                                                                                                                                                                                                                                                                                                                                | No workaround is available.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | June 24, 2024      | Edge                         |
 | Clusters configured with OpenID Connect (OIDC) at the Kubernetes layer encounter issues when authenticating with the [non-admin Kubeconfig file](../clusters/cluster-management/kubeconfig.md#cluster-admin). Kubeconfig files using OIDC to authenticate will not work if the SSL certificate is set at the OIDC provider level.                                                                                                                                                                                                                                                                                   | Use the admin Kubeconfig file to authenticate with the cluster, as it does not use OIDC to authenticate.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | June 21, 2024      | Clusters                     |
 | During the platform upgrade from Palette 4.3 to 4.4, Virtual Clusters may encounter a scenario where the pod `palette-controller-manager` is not upgraded to the newer version of Palette. The virtual cluster will continue to be operational, and this does not impact its functionality.                                                                                                                                                                                                                                                                                                                         | Refer to the [Controller Manager Pod Not Upgraded](../troubleshooting/palette-dev-engine.md#scenario---controller-manager-pod-not-upgraded) troubleshooting guide.                                                                                                                                                                                                                                                                                                                                                                                                                                               | June 15, 2024      | Virtual Clusters             |
-| Edge hosts with FIPS-compliant Red Hat Enterprise Linux (RHEL) and Ubuntu Operating Systems (OS) may encounter the error where the `systemd-resolved.service` service enters the **failed** state. This prevents the nameserver from being configured, which will result in cluster deployment failure.                                                                                                                                                                                                                                                                                                             | Refer to [TroubleShooting](../troubleshooting/edge.md#scenario---systemd-resolvedservice-enters-failed-state) for a workaround.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | June 15, 2024      | Edge                         |
+| Edge hosts with FIPS-compliant Red Hat Enterprise Linux (RHEL) and Ubuntu Operating Systems (OS) may encounter the error where the `systemd-resolved.service` service enters the **failed** state. This prevents the nameserver from being configured, which will result in cluster deployment failure.                                                                                                                                                                                                                                                                                                             | Refer to [TroubleShooting](../troubleshooting/edge/edge.md#scenario---systemd-resolvedservice-enters-failed-state) for a workaround.                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | June 15, 2024      | Edge                         |
 | The GKE cluster's Kubernetes pods are failing to start because the Kubernetes patch version is unavailable. This is encountered during pod restarts or node scaling operations.                                                                                                                                                                                                                                                                                                                                                                                                                                     | Deploy a new cluster and use a GKE cluster profile that does not contain a Kubernetes pack layer with a patch version. Migrate the workloads from the existing cluster to the new cluster. This is a breaking change introduced in Palette 4.4.0                                                                                                                                                                                                                                                                                                                                                                 | June 15, 2024      | Packs, Clusters              |
 | <VersionedLink text="Microk8s" url="/integrations/packs/?pack=kubernetes-microk8s" /> does not support multi-node control plane clusters. The upgrade strategy, `InPlaceUpgrade`, is the only option available for use.                                                                                                                                                                                                                                                                                                                                                                                             | No workaround is available.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | June 15, 2024      | Packs                        |
 | Clusters using <VersionedLink text="Microk8s" url="/integrations/packs/?pack=kubernetes-microk8s" /> as the Kubernetes distribution, the control plane node fails to upgrade when using the `InPlaceUpgrade` strategy for sequential upgrades, such as upgrading from version 1.25.x to version 1.26.x and then to version 1.27.x.                                                                                                                                                                                                                                                                                  | Refer to the [Control Plane Node Fails to Upgrade in Sequential MicroK8s Upgrades](../troubleshooting/pack-issues.md) troubleshooting guide for resolution steps.                                                                                                                                                                                                                                                                                                                                                                                                                                                | June 15, 2024      | Packs                        |
@@ -92,7 +92,7 @@ The following table lists all known issues that are currently active and affecti
 | Day-2 operations related to infrastructure changes, such as modifying the node size and count, when using MicroK8s are not taking effect.                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | No workaround is available.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | April 14, 2024     | Packs, Clusters              |
 | If a cluster that uses the Rook-Ceph pack experiences network issues, it's possible for the file mount to become and remain unavailable even after the network is restored.                                                                                                                                                                                                                                                                                                                                                                                                                                         | This a known issue disclosed in the [Rook GitHub repository](https://github.com/rook/rook/issues/13818). To resolve this issue, refer to <VersionedLink text="Rook-Ceph" url="/integrations/packs/?pack=csi-rook-ceph" /> pack documentation.                                                                                                                                                                                                                                                                                                                                                                    | April 14, 2024     | Packs, Edge                  |
 | Edge clusters on Edge hosts with ARM64 processors may experience instability issues that cause cluster failures.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ARM64 support is limited to a specific set of Edge devices. Currently, Nvidia Jetson devices are supported.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | April 14, 2024     | Edge                         |
-| During the cluster provisioning process of new edge clusters, the Palette webhook pods may not always deploy successfully, causing the cluster to be stuck in the provisioning phase. This issue does not impact deployed clusters.                                                                                                                                                                                                                                                                                                                                                                                 | Review the [Palette Webhook Pods Fail to Start](../troubleshooting/edge.md#scenario---palette-webhook-pods-fail-to-start) troubleshooting guide for resolution steps.                                                                                                                                                                                                                                                                                                                                                                                                                                            | April 14, 2024     | Edge                         |
+| During the cluster provisioning process of new edge clusters, the Palette webhook pods may not always deploy successfully, causing the cluster to be stuck in the provisioning phase. This issue does not impact deployed clusters.                                                                                                                                                                                                                                                                                                                                                                                 | Review the [Palette Webhook Pods Fail to Start](../troubleshooting/edge/edge.md#scenario---palette-webhook-pods-fail-to-start) troubleshooting guide for resolution steps.                                                                                                                                                                                                                                                                                                                                                                                                                                       | April 14, 2024     | Edge                         |
 
 ## Resolved Known Issues
 
diff --git a/docs/docs-content/troubleshooting/edge/_category_.json b/docs/docs-content/troubleshooting/edge/_category_.json
new file mode 100644
index 00000000000..c3912fd6a0e
--- /dev/null
+++ b/docs/docs-content/troubleshooting/edge/_category_.json
@@ -0,0 +1,3 @@
+{
+  "position": 41
+}
diff --git a/docs/docs-content/troubleshooting/edge/collect-support-bundles.md b/docs/docs-content/troubleshooting/edge/collect-support-bundles.md
new file mode 100644
index 00000000000..42ffb8db92a
--- /dev/null
+++ b/docs/docs-content/troubleshooting/edge/collect-support-bundles.md
@@ -0,0 +1,144 @@
+---
+sidebar_label: "Collect Support Bundles"
+title: "Collect Support Bundles for Edge Cluster Troubleshooting"
+description: "Learn how to deploy a Private Cloud Gateway (PCG) to an existing Kubernetes cluster."
+hide_table_of_contents: false
+sidebar_position: 1
+toc_min_heading_level: 2
+toc_max_heading_level: 3
+tags: ["edge", "troubleshooting", "support"]
+---
+
+When deploying or operating Edge clusters, you may encounter issues that require assistance from the Spectro Cloud
+support team, such as Edge hosts failing to register, pod failures, or provisioning errors. To help our team
+troubleshoot these issues more effectively, follow this guide to collect support bundles and attach them to your support
+ticket.
+
+## Prerequisites
+
+- The host you need to troubleshoot has an active internet connection to access the troubleshooting script.
+- You have connected to the host using SSH, direct terminal access, or another connection method.
+- The following tools are available on the host:
+  - `journalctl`
+  - `systemctl`
+- (Optional) The host has a valid `kubeconfig` file configured and `kubectl` installed (required for the full output of
+  `support-bundle-infra.sh`).
+
+## Run the Troubleshooting Scripts
+
+### Run the Script to Collect Cluster Logs
+
+The `support-bundle-infra.sh` script collects cluster-level diagnostics. Follow the steps below on a host with a valid
+`kubeconfig` and `kubectl` installed, typically a control plane node.
+
+1. Set the path to your `kubeconfig` file.
+
+   ```bash
+   export KUBECONFIG=/etc/kubernetes/admin.conf
+   ```
+
+2. Run the `support-bundle-infra.sh` script.
+
+   ```bash
+   curl --silent --show-error --location https://software.spectrocloud.com/scripts/support-bundle-infra.sh | bash
+   ```
+
+   If the script runs successfully, it creates a file in your home directory. The file name follows the pattern
+   `<cluster name>-<YYYY-MM-DD>_<HH_MM_SS>.tar.gz`. If the script is unable to determine the cluster name, it defaults
+   to `spectro-cluster`. One of the messages the terminal displays contains the name of the created file.
+
+   ```bash
+   Logs are archived in spectro-cluster-2025-05-13_16_50_50.tar.gz
+   ```
+
+3. Copy the file to your local computer. The command below serves as an example of how to copy the file
+   `spectro-cluster-2025-05-13_16_50_50.tar.gz` from the `kairos@10.10.150.150` host to your `Downloads` folder. Run the
+   command on the machine to which you want to copy the file.
+
+   ```bash
+   scp kairos@10.10.150.150:~/spectro-cluster-2025-05-13_16_50_50.tar.gz ~/Downloads/
+   ```
+
+### Run the Script to Collect Edge Host Logs
+
+The `support-bundle-edge.sh` script collects host-level diagnostics from an Edge node and, if available, includes
+Kubernetes data accessible locally on that host. Follow the steps below on every Edge host you want to troubleshoot.
+
+1. (Optional) Set the path to your `kubeconfig` file.
+
+   ```bash
+   export KUBECONFIG=/etc/kubernetes/admin.conf
+   ```
+
+   If you do not perform this step, the script defaults to using `/run/kubeconfig` if it exists.
+
+2. Run the `support-bundle-edge.sh` script as a user with root privileges.
+
+   ```bash
+   curl --silent --show-error --location https://software.spectrocloud.com/scripts/support-bundle-edge.sh | sudo bash
+   ```
+
+   The table below contains the optional flags you can use when running the script.
+
+   | **Full Flag Name**           | **Short Flag Name** | **Description**                                                                                  | **Example**                         |
+   | ---------------------------- | ------------------- | ------------------------------------------------------------------------------------------------ | ----------------------------------- |
+   | `--start-days-ago`           | `-s`                | Number of days in the past to start collecting journald logs.                                    | `-s 7`                              |
+   | `--end-days-ago`             | `-e`                | Number of days before now to stop collecting journald logs. The value must be smaller than `-s`. | `-e 5`                              |
+   | `--start-date`               | `-S`                | Start date for journald log collection.                                                          | `-S 2024-01-01`                     |
+   | `--end-date`                 | `-E`                | End date for journald log collection. Must be later than `-S`.                                   | `-E 2024-01-06`                     |
+   | `--namespaces`               | `-n`                | Additional namespaces to collect logs from.                                                      | `-n hello-universe,hello-world`     |
+   | `--resources-namespaced`     | `-r`                | Additional namespace-scoped resources to collect.                                                | `-r certificates.cert-manager.io`   |
+   | `--resources-cluster-scoped` | `-R`                | Additional cluster-scoped resources to collect.                                                  | `-R clusterissuers.cert-manager.io` |
+   | `--journald-services`        | `-j`                | Additional journald services to include in logs.                                                 | `-j cloud-init,systemd-resolved`    |
+
+   If the script runs successfully, it creates a file in the `/opt/spectrocloud/logs` directory. The file name follows
+   the pattern `<hostname>-<YYYY-MM-DD>_<HH_MM_SS>.tar.gz`. One of the messages the terminal displays contains the
+   created file's name and its path.
+
+   ```bash
+   Logs are archived in /opt/spectrocloud/logs/edge-e965384209c2d45078a29480e90bd275-2025-05-13_16_58_20.tar.gz
+   ```
+
+   :::info
+
+   The script collects only Helm release secrets from Spectro Cloud namespaces and excludes other Kubernetes secrets to
+   protect sensitive data.
+
+   :::
+
+3. Copy the file to your local computer. The command below serves as an example of how to copy the file
+   `edge-e965384209c2d45078a29480e90bd275-2025-05-13_16_58_20.tar.gz` from the `kairos@10.10.150.150` host to your
+   `Downloads` folder. Run the command on the machine to which you want to copy the file.
+
+   ```bash
+   scp kairos@10.10.150.150:/opt/spectrocloud/logs/edge-e965384209c2d45078a29480e90bd275-2025-05-13_16_58_20.tar.gz ~/Downloads/
+   ```
+
+## Validate
+
+Review the files you copied to the `Downloads` folder. The scripts archive the collected logs into compressed tarballs
+TAR.GAR.
+
+Extract the file named in the format `<cluster name>-<YYYY-MM-DD>_<HH_MM_SS>.tar.gz` and verify it contains the `k8s`
+folder with the following subfolders:
+
+- `cluster-info`
+- `cluster-resources`
+- `metrics`
+- `previous-pod-logs`
+
+Extract the file named in the format `<hostname>-<YYYY-MM-DD>_<HH_MM_SS>.tar.gz` and ensure it contains the following:
+
+- `console.log` file
+- `helm` folder
+- `journald` folder
+- `networking` folder
+- `oem` folder
+- `run` folder
+- `systeminfo` folder
+- `usr` folder
+- `var` folder
+
+## Next Steps
+
+After you have successfully collected support bundles, attach the TAR.GAR archives to the support ticket.
diff --git a/docs/docs-content/troubleshooting/edge.md b/docs/docs-content/troubleshooting/edge/edge.md
similarity index 91%
rename from docs/docs-content/troubleshooting/edge.md
rename to docs/docs-content/troubleshooting/edge/edge.md
index 6f23d0373e7..d1f9ef2c63c 100644
--- a/docs/docs-content/troubleshooting/edge.md
+++ b/docs/docs-content/troubleshooting/edge/edge.md
@@ -4,7 +4,7 @@ title: "Edge"
 description: "Troubleshooting steps for common Edge scenarios."
 icon: ""
 hide_table_of_contents: false
-sidebar_position: 40
+sidebar_position: 0
 tags: ["edge", "troubleshooting"]
 ---
 
@@ -14,15 +14,15 @@ The following are common scenarios that you may encounter when using Edge.
 
 <!-- prettier-ignore -->
 When attempting to deploy a cluster with <VersionedLink text="Palette eXtended Kubernetes - Edge (PXK-E)" url="/integrations/packs/?pack=edge-k8s" />
-and [agent mode](../deployment-modes/agent-mode/agent-mode.md) on Palette agent version 4.5.14, adding a custom `stylus.path` to
+and [agent mode](../../deployment-modes/agent-mode/agent-mode.md) on Palette agent version 4.5.14, adding a custom `stylus.path` to
 the **user-data** file causes cluster creation to fail as it cannot find
 [kubeadm](https://kubernetes.io/docs/reference/setup-tools/kubeadm/). A custom `stylus.path` can be added during the
-[Install Palette Agent](../deployment-modes/agent-mode/install-agent-host.md#install-palette-agent) steps.
+[Install Palette Agent](../../deployment-modes/agent-mode/install-agent-host.md#install-palette-agent) steps.
 
 :::tip
 
 Refer to
-[Identify the Target Agent Version](../clusters/edge/cluster-management/agent-upgrade-airgap.md#identify-the-target-agent-version)
+[Identify the Target Agent Version](../../clusters/edge/cluster-management/agent-upgrade-airgap.md#identify-the-target-agent-version)
 for guidance in retrieving your Palette agent version number.
 
 :::
@@ -54,7 +54,7 @@ pack configuration by following the debug steps below.
    ```
 
    Replace `<customStylusPath>` with the custom `stylus.path` you provided in the **user-data** file during the
-   [Install Palette Agent](../deployment-modes/agent-mode/install-agent-host.md#install-palette-agent) steps, as
+   [Install Palette Agent](../../deployment-modes/agent-mode/install-agent-host.md#install-palette-agent) steps, as
    demonstrated in the following example.
 
    ```yaml hideClipboard {7-13}
@@ -125,7 +125,7 @@ adjust the values of related environment variables in the KubeVip DaemonSet with
 ### Debug Steps
 
 1. Ensure you can access the cluster using kubectl. For more information, refer to
-   [Access Cluster with CLI](../clusters/cluster-management/palette-webctl.md).
+   [Access Cluster with CLI](../../clusters/cluster-management/palette-webctl.md).
 
 2. Issue the following command:
 
@@ -157,7 +157,7 @@ issues or not being available. Use the following steps to troubleshoot and resol
 ### Debug Steps
 
 1. Ensure you can access the Kubernetes cluster using kubectl. For more information, refer to
-   [Access Cluster with CLI](../clusters/cluster-management/palette-webctl.md).
+   [Access Cluster with CLI](../../clusters/cluster-management/palette-webctl.md).
 
 2. Open up a terminal session and issue the following command to check the status of the
    _palette-lite-controller-manager_ pods.
@@ -249,9 +249,9 @@ prevents the nameserver from being configured, which will result in cluster depl
 ## Scenario - Degraded Performance on Disk Drives
 
 If you are experiencing degraded performance on disk drives, such as Solid-State Drive or Nonvolatile Memory Express
-drives, and you have [Trusted Boot](../clusters/edge/trusted-boot/trusted-boot.md) enabled. The degraded performance may
-be caused by TRIM operations not being enabled on the drives. TRIM allows the OS to notify the drive which data blocks
-are no longer in use and can be erased internally. To enable TRIM operations, use the following steps.
+drives, and you have [Trusted Boot](../../clusters/edge/trusted-boot/trusted-boot.md) enabled. The degraded performance
+may be caused by TRIM operations not being enabled on the drives. TRIM allows the OS to notify the drive which data
+blocks are no longer in use and can be erased internally. To enable TRIM operations, use the following steps.
 
 ### Debug Steps
 
@@ -300,7 +300,7 @@ are no longer in use and can be erased internally. To enable TRIM operations, us
 
 6. Click on **Confirm Updates** to save the changes.
 
-7. Use the updated profile to create a [new Edge cluster](../clusters/edge/site-deployment/cluster-deployment.md) or
+7. Use the updated profile to create a [new Edge cluster](../../clusters/edge/site-deployment/cluster-deployment.md) or
    update an existing Edge cluster.
 
 ## Scenario - Clusters with Cilium and RKE2 Experiences Kubernetes Upgrade Failure
@@ -313,7 +313,7 @@ the Cilium DaemonSet.
 ### Debug Steps
 
 1. Connect to your cluster using kubectl. For more information, refer to
-   [Access Cluster with kubectl](../clusters/cluster-management/palette-webctl.md).
+   [Access Cluster with kubectl](../../clusters/cluster-management/palette-webctl.md).
 
 2. Issue the following command from the terminal edit the Cilium DaemonSet.
 
@@ -377,7 +377,7 @@ Palette agent:
 
 ## Scenario - Kubelet Process Cannot Access kubeadm-flags
 
-If using the FIPS version of [Agent Mode](../deployment-modes/agent-mode/install-agent-host.md) on a Rocky Linux edge
+If using the FIPS version of [Agent Mode](../../deployment-modes/agent-mode/install-agent-host.md) on a Rocky Linux edge
 host, SELinux may incorrectly label the **kubeadm-flags.env** file during cluster deployment or when certain
 configurations are adjusted, preventing the Kubelet from accessing it and properly managing the cluster. To resolve this
 issue, reset the SELinux context of the Kubelet environment variable to its default state based on SELinux policy rules.
@@ -451,4 +451,4 @@ incorrectly. This prevents the CNI that do not run as root, such as Cilium, from
    ```
 
 5. Save the changes as a new version of the cluster profile and update your agent mode cluster to use the updated
-   profile. For more information, refer to [Update a Cluster](../clusters/cluster-management/cluster-updates.md).
+   profile. For more information, refer to [Update a Cluster](../../clusters/cluster-management/cluster-updates.md).
diff --git a/docs/docs-content/troubleshooting/troubleshooting.md b/docs/docs-content/troubleshooting/troubleshooting.md
index be2ea8907e6..badee3022d1 100644
--- a/docs/docs-content/troubleshooting/troubleshooting.md
+++ b/docs/docs-content/troubleshooting/troubleshooting.md
@@ -15,7 +15,7 @@ support team by opening up a ticket through our [support page](http://support.sp
 
 - [Cluster Deployment](cluster-deployment.md)
 
-- [Edge](edge.md)
+- [Edge](edge/edge.md)
 
 - [Enterprise Install](enterprise-install.md)
 


Reviews:
user: login: github-actions[bot]
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-13T17:53:04Z
user: login: svetlana-efimova
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-13T17:54:45Z
user: login: svetlana-efimova
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-13T17:55:25Z
user: login: svetlana-efimova
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-13T17:56:01Z
user: login: github-actions[bot]
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-13T17:56:56Z
user: login: svetlana-efimova
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-13T18:06:20Z
user: login: svetlana-efimova
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-13T18:46:18Z
user: login: lennessyy
state: APPROVED
author_association: CONTRIBUTOR
submitted_at: 2025-05-13T20:41:43Z
user: login: github-actions[bot]
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-13T20:48:11Z

Review comments:
diff_hunk: @@ -0,0 +1,127 @@
+---
+sidebar_label: "Collect Support Bundles"
+title: "Collect Support Bundles for Edge Cluster Troubleshooting"
+description: "Learn how to deploy a Private Cloud Gateway (PCG) to an existing Kubernetes cluster."
+hide_table_of_contents: false
+sidebar_position: 1
+toc_min_heading_level: 2
+toc_max_heading_level: 3
+tags: ["edge", "troubleshooting", "support"]
+---
+When deploying or operating Edge clusters, you may encounter issues that require assistance from the SpectroCloud support team, such as Edge hosts failing to register, pod failures, or provisioning errors. To help our team troubleshoot these issues more effectively, follow this guide to collect support bundles and attach them to your support ticket.
path: docs/docs-content/troubleshooting/edge/collect-support-bundles.md
user: login: github-actions[bot]
body: 🚫 **[vale]** <sub>reported by [reviewdog](https://github.com/reviewdog/reviewdog) :dog:</sub><br>[spectrocloud-docs-internal.brand] Avoid using 'spectrocloud' outside of a URL format. Use 'Spectro Cloud' instead.
created_at: 2025-05-13T17:53:02Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,127 @@
+---
+sidebar_label: "Collect Support Bundles"
+title: "Collect Support Bundles for Edge Cluster Troubleshooting"
+description: "Learn how to deploy a Private Cloud Gateway (PCG) to an existing Kubernetes cluster."
+hide_table_of_contents: false
+sidebar_position: 1
+toc_min_heading_level: 2
+toc_max_heading_level: 3
+tags: ["edge", "troubleshooting", "support"]
+---
+When deploying or operating Edge clusters, you may encounter issues that require assistance from the SpectroCloud support team, such as Edge hosts failing to register, pod failures, or provisioning errors. To help our team troubleshoot these issues more effectively, follow this guide to collect support bundles and attach them to your support ticket.
+
+## Limitations
+
+- This guide applies only to connected installation mode, not airgap environments, since it requires internet access to run the troubleshooting script.
path: docs/docs-content/troubleshooting/edge/collect-support-bundles.md
user: login: github-actions[bot]
body: 🚫 **[vale]** <sub>reported by [reviewdog](https://github.com/reviewdog/reviewdog) :dog:</sub><br>[spectrocloud-docs-internal.ableism] Avoid using ableism terms. Use 'issue' instead of 'run'.
created_at: 2025-05-13T17:53:02Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,127 @@
+---
+sidebar_label: "Collect Support Bundles"
+title: "Collect Support Bundles for Edge Cluster Troubleshooting"
+description: "Learn how to deploy a Private Cloud Gateway (PCG) to an existing Kubernetes cluster."
+hide_table_of_contents: false
+sidebar_position: 1
+toc_min_heading_level: 2
+toc_max_heading_level: 3
+tags: ["edge", "troubleshooting", "support"]
+---
+When deploying or operating Edge clusters, you may encounter issues that require assistance from the SpectroCloud support team, such as Edge hosts failing to register, pod failures, or provisioning errors. To help our team troubleshoot these issues more effectively, follow this guide to collect support bundles and attach them to your support ticket.
+
+## Limitations
+
+- This guide applies only to connected installation mode, not airgap environments, since it requires internet access to run the troubleshooting script.
+
+## Prerequisites
+
+- You have connected to the host you need to troubleshoot, using SSH, direct terminal access, or another connection method.
+- The following tools are available on the host:
+    - `journalctl`
+    - `systemctl`
+    - (Optional) `kubectl` (required for the full output of `support-bundle-infra.sh`)
+- (Optional) A valid `kubeconfig` file is configured (required for the full output of `support-bundle-infra.sh`)
+
+## Run the Troubleshooting Scripts
path: docs/docs-content/troubleshooting/edge/collect-support-bundles.md
user: login: github-actions[bot]
body: 🚫 **[vale]** <sub>reported by [reviewdog](https://github.com/reviewdog/reviewdog) :dog:</sub><br>[spectrocloud-docs-internal.ableism] Avoid using ableism terms. Use 'issue' instead of 'Run'.
created_at: 2025-05-13T17:53:02Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,127 @@
+---
+sidebar_label: "Collect Support Bundles"
+title: "Collect Support Bundles for Edge Cluster Troubleshooting"
+description: "Learn how to deploy a Private Cloud Gateway (PCG) to an existing Kubernetes cluster."
+hide_table_of_contents: false
+sidebar_position: 1
+toc_min_heading_level: 2
+toc_max_heading_level: 3
+tags: ["edge", "troubleshooting", "support"]
+---
+When deploying or operating Edge clusters, you may encounter issues that require assistance from the SpectroCloud support team, such as Edge hosts failing to register, pod failures, or provisioning errors. To help our team troubleshoot these issues more effectively, follow this guide to collect support bundles and attach them to your support ticket.
+
+## Limitations
+
+- This guide applies only to connected installation mode, not airgap environments, since it requires internet access to run the troubleshooting script.
+
+## Prerequisites
+
+- You have connected to the host you need to troubleshoot, using SSH, direct terminal access, or another connection method.
+- The following tools are available on the host:
+    - `journalctl`
+    - `systemctl`
+    - (Optional) `kubectl` (required for the full output of `support-bundle-infra.sh`)
+- (Optional) A valid `kubeconfig` file is configured (required for the full output of `support-bundle-infra.sh`)
+
+## Run the Troubleshooting Scripts
+
+### Run the Script to Collect Cluster Logs
path: docs/docs-content/troubleshooting/edge/collect-support-bundles.md
user: login: github-actions[bot]
body: 🚫 **[vale]** <sub>reported by [reviewdog](https://github.com/reviewdog/reviewdog) :dog:</sub><br>[spectrocloud-docs-internal.ableism] Avoid using ableism terms. Use 'issue' instead of 'Run'.
created_at: 2025-05-13T17:53:02Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,127 @@
+---
+sidebar_label: "Collect Support Bundles"
+title: "Collect Support Bundles for Edge Cluster Troubleshooting"
+description: "Learn how to deploy a Private Cloud Gateway (PCG) to an existing Kubernetes cluster."
+hide_table_of_contents: false
+sidebar_position: 1
+toc_min_heading_level: 2
+toc_max_heading_level: 3
+tags: ["edge", "troubleshooting", "support"]
+---
+When deploying or operating Edge clusters, you may encounter issues that require assistance from the SpectroCloud support team, such as Edge hosts failing to register, pod failures, or provisioning errors. To help our team troubleshoot these issues more effectively, follow this guide to collect support bundles and attach them to your support ticket.
+
+## Limitations
+
+- This guide applies only to connected installation mode, not airgap environments, since it requires internet access to run the troubleshooting script.
+
+## Prerequisites
+
+- You have connected to the host you need to troubleshoot, using SSH, direct terminal access, or another connection method.
+- The following tools are available on the host:
+    - `journalctl`
+    - `systemctl`
+    - (Optional) `kubectl` (required for the full output of `support-bundle-infra.sh`)
+- (Optional) A valid `kubeconfig` file is configured (required for the full output of `support-bundle-infra.sh`)
+
+## Run the Troubleshooting Scripts
+
+### Run the Script to Collect Cluster Logs
+The `support-bundle-infra.sh` script collects cluster-level diagnostics. Follow the steps below on a host with a valid `kubeconfig` and `kubectl` installed, typically a control plane node.
+
+1. Set the path to your `kubeconfig` file.
+
+    ```bash
+    export KUBECONFIG=/etc/kubernetes/admin.conf
+    ```
+
+2. Run the `support-bundle-infra.sh` script.
path: docs/docs-content/troubleshooting/edge/collect-support-bundles.md
user: login: github-actions[bot]
body: 🚫 **[vale]** <sub>reported by [reviewdog](https://github.com/reviewdog/reviewdog) :dog:</sub><br>[spectrocloud-docs-internal.ableism] Avoid using ableism terms. Use 'issue' instead of 'Run'.
created_at: 2025-05-13T17:53:03Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,127 @@
+---
+sidebar_label: "Collect Support Bundles"
+title: "Collect Support Bundles for Edge Cluster Troubleshooting"
+description: "Learn how to deploy a Private Cloud Gateway (PCG) to an existing Kubernetes cluster."
+hide_table_of_contents: false
+sidebar_position: 1
+toc_min_heading_level: 2
+toc_max_heading_level: 3
+tags: ["edge", "troubleshooting", "support"]
+---
+When deploying or operating Edge clusters, you may encounter issues that require assistance from the SpectroCloud support team, such as Edge hosts failing to register, pod failures, or provisioning errors. To help our team troubleshoot these issues more effectively, follow this guide to collect support bundles and attach them to your support ticket.
+
+## Limitations
+
+- This guide applies only to connected installation mode, not airgap environments, since it requires internet access to run the troubleshooting script.
+
+## Prerequisites
+
+- You have connected to the host you need to troubleshoot, using SSH, direct terminal access, or another connection method.
+- The following tools are available on the host:
+    - `journalctl`
+    - `systemctl`
+    - (Optional) `kubectl` (required for the full output of `support-bundle-infra.sh`)
+- (Optional) A valid `kubeconfig` file is configured (required for the full output of `support-bundle-infra.sh`)
+
+## Run the Troubleshooting Scripts
+
+### Run the Script to Collect Cluster Logs
+The `support-bundle-infra.sh` script collects cluster-level diagnostics. Follow the steps below on a host with a valid `kubeconfig` and `kubectl` installed, typically a control plane node.
+
+1. Set the path to your `kubeconfig` file.
+
+    ```bash
+    export KUBECONFIG=/etc/kubernetes/admin.conf
+    ```
+
+2. Run the `support-bundle-infra.sh` script.
+
+    ```bash
+    curl -sSL https://software.spectrocloud.com/scripts/support-bundle-infra.sh | bash
path: docs/docs-content/troubleshooting/edge/collect-support-bundles.md
user: login: github-actions[bot]
body: 🚫 **[vale]** <sub>reported by [reviewdog](https://github.com/reviewdog/reviewdog) :dog:</sub><br>[spectrocloud-docs-internal.longform] Avoid using the short form of commands. Replace the short form flag in 'curl -sSL' with the corresponding long form flag.
created_at: 2025-05-13T17:53:03Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,127 @@
+---
+sidebar_label: "Collect Support Bundles"
+title: "Collect Support Bundles for Edge Cluster Troubleshooting"
+description: "Learn how to deploy a Private Cloud Gateway (PCG) to an existing Kubernetes cluster."
+hide_table_of_contents: false
+sidebar_position: 1
+toc_min_heading_level: 2
+toc_max_heading_level: 3
+tags: ["edge", "troubleshooting", "support"]
+---
+When deploying or operating Edge clusters, you may encounter issues that require assistance from the SpectroCloud support team, such as Edge hosts failing to register, pod failures, or provisioning errors. To help our team troubleshoot these issues more effectively, follow this guide to collect support bundles and attach them to your support ticket.
+
+## Limitations
+
+- This guide applies only to connected installation mode, not airgap environments, since it requires internet access to run the troubleshooting script.
+
+## Prerequisites
+
+- You have connected to the host you need to troubleshoot, using SSH, direct terminal access, or another connection method.
+- The following tools are available on the host:
+    - `journalctl`
+    - `systemctl`
+    - (Optional) `kubectl` (required for the full output of `support-bundle-infra.sh`)
+- (Optional) A valid `kubeconfig` file is configured (required for the full output of `support-bundle-infra.sh`)
+
+## Run the Troubleshooting Scripts
+
+### Run the Script to Collect Cluster Logs
+The `support-bundle-infra.sh` script collects cluster-level diagnostics. Follow the steps below on a host with a valid `kubeconfig` and `kubectl` installed, typically a control plane node.
+
+1. Set the path to your `kubeconfig` file.
+
+    ```bash
+    export KUBECONFIG=/etc/kubernetes/admin.conf
+    ```
+
+2. Run the `support-bundle-infra.sh` script.
+
+    ```bash
+    curl -sSL https://software.spectrocloud.com/scripts/support-bundle-infra.sh | bash
+    ```
+    If the script runs successfully, it creates a file in your home directory. The file name follows the pattern `<cluster name>-<YYYY-MM-DD>_<HH_MM_SS>.tar.gz`. If the script is unable to determine the cluster name, it defaults to `spectro-cluster`. One of the messages the terminal displays contains the name of the created file.
+
+    ```bash
+    Logs are archived in spectro-cluster-2025-05-13_16_50_50.tar.gz
+    ``` 
+
+3. Copy the file to your local computer. The command below serves as an example of how to copy the file `spectro-cluster-2025-05-13_16_50_50.tar.gz` from the `kairos@10.10.150.150` host to your `Downloads` folder. Run the command on the machine to which you want to copy the file.
path: docs/docs-content/troubleshooting/edge/collect-support-bundles.md
user: login: github-actions[bot]
body: 🚫 **[vale]** <sub>reported by [reviewdog](https://github.com/reviewdog/reviewdog) :dog:</sub><br>[spectrocloud-docs-internal.ableism] Avoid using ableism terms. Use 'issue' instead of 'Run'.
created_at: 2025-05-13T17:53:03Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,127 @@
+---
+sidebar_label: "Collect Support Bundles"
+title: "Collect Support Bundles for Edge Cluster Troubleshooting"
+description: "Learn how to deploy a Private Cloud Gateway (PCG) to an existing Kubernetes cluster."
+hide_table_of_contents: false
+sidebar_position: 1
+toc_min_heading_level: 2
+toc_max_heading_level: 3
+tags: ["edge", "troubleshooting", "support"]
+---
+When deploying or operating Edge clusters, you may encounter issues that require assistance from the SpectroCloud support team, such as Edge hosts failing to register, pod failures, or provisioning errors. To help our team troubleshoot these issues more effectively, follow this guide to collect support bundles and attach them to your support ticket.
+
+## Limitations
+
+- This guide applies only to connected installation mode, not airgap environments, since it requires internet access to run the troubleshooting script.
+
+## Prerequisites
+
+- You have connected to the host you need to troubleshoot, using SSH, direct terminal access, or another connection method.
+- The following tools are available on the host:
+    - `journalctl`
+    - `systemctl`
+    - (Optional) `kubectl` (required for the full output of `support-bundle-infra.sh`)
+- (Optional) A valid `kubeconfig` file is configured (required for the full output of `support-bundle-infra.sh`)
+
+## Run the Troubleshooting Scripts
+
+### Run the Script to Collect Cluster Logs
+The `support-bundle-infra.sh` script collects cluster-level diagnostics. Follow the steps below on a host with a valid `kubeconfig` and `kubectl` installed, typically a control plane node.
+
+1. Set the path to your `kubeconfig` file.
+
+    ```bash
+    export KUBECONFIG=/etc/kubernetes/admin.conf
+    ```
+
+2. Run the `support-bundle-infra.sh` script.
+
+    ```bash
+    curl -sSL https://software.spectrocloud.com/scripts/support-bundle-infra.sh | bash
+    ```
+    If the script runs successfully, it creates a file in your home directory. The file name follows the pattern `<cluster name>-<YYYY-MM-DD>_<HH_MM_SS>.tar.gz`. If the script is unable to determine the cluster name, it defaults to `spectro-cluster`. One of the messages the terminal displays contains the name of the created file.
+
+    ```bash
+    Logs are archived in spectro-cluster-2025-05-13_16_50_50.tar.gz
+    ``` 
+
+3. Copy the file to your local computer. The command below serves as an example of how to copy the file `spectro-cluster-2025-05-13_16_50_50.tar.gz` from the `kairos@10.10.150.150` host to your `Downloads` folder. Run the command on the machine to which you want to copy the file.
+
+    ```bash
+    scp kairos@10.10.150.150:~/spectro-cluster-2025-05-13_16_50_50.tar.gz ~/Downloads/
+    ```
+
+### Run the Script to Collect Edge Host Logs
path: docs/docs-content/troubleshooting/edge/collect-support-bundles.md
user: login: github-actions[bot]
body: 🚫 **[vale]** <sub>reported by [reviewdog](https://github.com/reviewdog/reviewdog) :dog:</sub><br>[spectrocloud-docs-internal.ableism] Avoid using ableism terms. Use 'issue' instead of 'Run'.
created_at: 2025-05-13T17:53:03Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,127 @@
+---
+sidebar_label: "Collect Support Bundles"
+title: "Collect Support Bundles for Edge Cluster Troubleshooting"
+description: "Learn how to deploy a Private Cloud Gateway (PCG) to an existing Kubernetes cluster."
+hide_table_of_contents: false
+sidebar_position: 1
+toc_min_heading_level: 2
+toc_max_heading_level: 3
+tags: ["edge", "troubleshooting", "support"]
+---
+When deploying or operating Edge clusters, you may encounter issues that require assistance from the SpectroCloud support team, such as Edge hosts failing to register, pod failures, or provisioning errors. To help our team troubleshoot these issues more effectively, follow this guide to collect support bundles and attach them to your support ticket.
+
+## Limitations
+
+- This guide applies only to connected installation mode, not airgap environments, since it requires internet access to run the troubleshooting script.
+
+## Prerequisites
+
+- You have connected to the host you need to troubleshoot, using SSH, direct terminal access, or another connection method.
+- The following tools are available on the host:
+    - `journalctl`
+    - `systemctl`
+    - (Optional) `kubectl` (required for the full output of `support-bundle-infra.sh`)
+- (Optional) A valid `kubeconfig` file is configured (required for the full output of `support-bundle-infra.sh`)
+
+## Run the Troubleshooting Scripts
+
+### Run the Script to Collect Cluster Logs
+The `support-bundle-infra.sh` script collects cluster-level diagnostics. Follow the steps below on a host with a valid `kubeconfig` and `kubectl` installed, typically a control plane node.
+
+1. Set the path to your `kubeconfig` file.
+
+    ```bash
+    export KUBECONFIG=/etc/kubernetes/admin.conf
+    ```
+
+2. Run the `support-bundle-infra.sh` script.
+
+    ```bash
+    curl -sSL https://software.spectrocloud.com/scripts/support-bundle-infra.sh | bash
+    ```
+    If the script runs successfully, it creates a file in your home directory. The file name follows the pattern `<cluster name>-<YYYY-MM-DD>_<HH_MM_SS>.tar.gz`. If the script is unable to determine the cluster name, it defaults to `spectro-cluster`. One of the messages the terminal displays contains the name of the created file.
+
+    ```bash
+    Logs are archived in spectro-cluster-2025-05-13_16_50_50.tar.gz
+    ``` 
+
+3. Copy the file to your local computer. The command below serves as an example of how to copy the file `spectro-cluster-2025-05-13_16_50_50.tar.gz` from the `kairos@10.10.150.150` host to your `Downloads` folder. Run the command on the machine to which you want to copy the file.
+
+    ```bash
+    scp kairos@10.10.150.150:~/spectro-cluster-2025-05-13_16_50_50.tar.gz ~/Downloads/
+    ```
+
+### Run the Script to Collect Edge Host Logs
+The `support-bundle-edge.sh` script collects host-level diagnostics from an Edge node and, if available, includes Kubernetes data accessible locally on that host.
+Follow the steps below on every Edge host you want to troubleshoot.
+
+1. (Optional) Set the path to your `kubeconfig` file.
+
+    ```bash
+    export KUBECONFIG=/etc/kubernetes/admin.conf
+    ```
+
+    If you do not perform this step, the script defaults to using `/run/kubeconfig` if it exists.
+
+2. Run the `support-bundle-edge.sh` script as a user with sudo privileges.
path: docs/docs-content/troubleshooting/edge/collect-support-bundles.md
user: login: github-actions[bot]
body: 🚫 **[vale]** <sub>reported by [reviewdog](https://github.com/reviewdog/reviewdog) :dog:</sub><br>[spectrocloud-docs-internal.ableism] Avoid using ableism terms. Use 'issue' instead of 'Run'.
created_at: 2025-05-13T17:53:03Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,127 @@
+---
+sidebar_label: "Collect Support Bundles"
+title: "Collect Support Bundles for Edge Cluster Troubleshooting"
+description: "Learn how to deploy a Private Cloud Gateway (PCG) to an existing Kubernetes cluster."
+hide_table_of_contents: false
+sidebar_position: 1
+toc_min_heading_level: 2
+toc_max_heading_level: 3
+tags: ["edge", "troubleshooting", "support"]
+---
+When deploying or operating Edge clusters, you may encounter issues that require assistance from the SpectroCloud support team, such as Edge hosts failing to register, pod failures, or provisioning errors. To help our team troubleshoot these issues more effectively, follow this guide to collect support bundles and attach them to your support ticket.
+
+## Limitations
+
+- This guide applies only to connected installation mode, not airgap environments, since it requires internet access to run the troubleshooting script.
+
+## Prerequisites
+
+- You have connected to the host you need to troubleshoot, using SSH, direct terminal access, or another connection method.
+- The following tools are available on the host:
+    - `journalctl`
+    - `systemctl`
+    - (Optional) `kubectl` (required for the full output of `support-bundle-infra.sh`)
+- (Optional) A valid `kubeconfig` file is configured (required for the full output of `support-bundle-infra.sh`)
+
+## Run the Troubleshooting Scripts
+
+### Run the Script to Collect Cluster Logs
+The `support-bundle-infra.sh` script collects cluster-level diagnostics. Follow the steps below on a host with a valid `kubeconfig` and `kubectl` installed, typically a control plane node.
+
+1. Set the path to your `kubeconfig` file.
+
+    ```bash
+    export KUBECONFIG=/etc/kubernetes/admin.conf
+    ```
+
+2. Run the `support-bundle-infra.sh` script.
+
+    ```bash
+    curl -sSL https://software.spectrocloud.com/scripts/support-bundle-infra.sh | bash
+    ```
+    If the script runs successfully, it creates a file in your home directory. The file name follows the pattern `<cluster name>-<YYYY-MM-DD>_<HH_MM_SS>.tar.gz`. If the script is unable to determine the cluster name, it defaults to `spectro-cluster`. One of the messages the terminal displays contains the name of the created file.
+
+    ```bash
+    Logs are archived in spectro-cluster-2025-05-13_16_50_50.tar.gz
+    ``` 
+
+3. Copy the file to your local computer. The command below serves as an example of how to copy the file `spectro-cluster-2025-05-13_16_50_50.tar.gz` from the `kairos@10.10.150.150` host to your `Downloads` folder. Run the command on the machine to which you want to copy the file.
+
+    ```bash
+    scp kairos@10.10.150.150:~/spectro-cluster-2025-05-13_16_50_50.tar.gz ~/Downloads/
+    ```
+
+### Run the Script to Collect Edge Host Logs
+The `support-bundle-edge.sh` script collects host-level diagnostics from an Edge node and, if available, includes Kubernetes data accessible locally on that host.
+Follow the steps below on every Edge host you want to troubleshoot.
+
+1. (Optional) Set the path to your `kubeconfig` file.
+
+    ```bash
+    export KUBECONFIG=/etc/kubernetes/admin.conf
+    ```
+
+    If you do not perform this step, the script defaults to using `/run/kubeconfig` if it exists.
+
+2. Run the `support-bundle-edge.sh` script as a user with sudo privileges.
path: docs/docs-content/troubleshooting/edge/collect-support-bundles.md
user: login: github-actions[bot]
body: 🚫 **[vale]** <sub>reported by [reviewdog](https://github.com/reviewdog/reviewdog) :dog:</sub><br>[Vale.Spelling] Did you really mean 'sudo'?
created_at: 2025-05-13T17:53:03Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,127 @@
+---
+sidebar_label: "Collect Support Bundles"
+title: "Collect Support Bundles for Edge Cluster Troubleshooting"
+description: "Learn how to deploy a Private Cloud Gateway (PCG) to an existing Kubernetes cluster."
+hide_table_of_contents: false
+sidebar_position: 1
+toc_min_heading_level: 2
+toc_max_heading_level: 3
+tags: ["edge", "troubleshooting", "support"]
+---
+When deploying or operating Edge clusters, you may encounter issues that require assistance from the SpectroCloud support team, such as Edge hosts failing to register, pod failures, or provisioning errors. To help our team troubleshoot these issues more effectively, follow this guide to collect support bundles and attach them to your support ticket.
+
+## Limitations
+
+- This guide applies only to connected installation mode, not airgap environments, since it requires internet access to run the troubleshooting script.
+
+## Prerequisites
+
+- You have connected to the host you need to troubleshoot, using SSH, direct terminal access, or another connection method.
+- The following tools are available on the host:
+    - `journalctl`
+    - `systemctl`
+    - (Optional) `kubectl` (required for the full output of `support-bundle-infra.sh`)
+- (Optional) A valid `kubeconfig` file is configured (required for the full output of `support-bundle-infra.sh`)
+
+## Run the Troubleshooting Scripts
+
+### Run the Script to Collect Cluster Logs
+The `support-bundle-infra.sh` script collects cluster-level diagnostics. Follow the steps below on a host with a valid `kubeconfig` and `kubectl` installed, typically a control plane node.
+
+1. Set the path to your `kubeconfig` file.
+
+    ```bash
+    export KUBECONFIG=/etc/kubernetes/admin.conf
+    ```
+
+2. Run the `support-bundle-infra.sh` script.
+
+    ```bash
+    curl -sSL https://software.spectrocloud.com/scripts/support-bundle-infra.sh | bash
+    ```
+    If the script runs successfully, it creates a file in your home directory. The file name follows the pattern `<cluster name>-<YYYY-MM-DD>_<HH_MM_SS>.tar.gz`. If the script is unable to determine the cluster name, it defaults to `spectro-cluster`. One of the messages the terminal displays contains the name of the created file.
+
+    ```bash
+    Logs are archived in spectro-cluster-2025-05-13_16_50_50.tar.gz
+    ``` 
+
+3. Copy the file to your local computer. The command below serves as an example of how to copy the file `spectro-cluster-2025-05-13_16_50_50.tar.gz` from the `kairos@10.10.150.150` host to your `Downloads` folder. Run the command on the machine to which you want to copy the file.
+
+    ```bash
+    scp kairos@10.10.150.150:~/spectro-cluster-2025-05-13_16_50_50.tar.gz ~/Downloads/
+    ```
+
+### Run the Script to Collect Edge Host Logs
+The `support-bundle-edge.sh` script collects host-level diagnostics from an Edge node and, if available, includes Kubernetes data accessible locally on that host.
+Follow the steps below on every Edge host you want to troubleshoot.
+
+1. (Optional) Set the path to your `kubeconfig` file.
+
+    ```bash
+    export KUBECONFIG=/etc/kubernetes/admin.conf
+    ```
+
+    If you do not perform this step, the script defaults to using `/run/kubeconfig` if it exists.
+
+2. Run the `support-bundle-edge.sh` script as a user with sudo privileges.
+
+    ```bash
+    curl -sSL https://software.spectrocloud.com/scripts/support-bundle-edge.sh | sudo bash
path: docs/docs-content/troubleshooting/edge/collect-support-bundles.md
user: login: github-actions[bot]
body: 🚫 **[vale]** <sub>reported by [reviewdog](https://github.com/reviewdog/reviewdog) :dog:</sub><br>[spectrocloud-docs-internal.longform] Avoid using the short form of commands. Replace the short form flag in 'curl -sSL' with the corresponding long form flag.
created_at: 2025-05-13T17:53:03Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,127 @@
+---
+sidebar_label: "Collect Support Bundles"
+title: "Collect Support Bundles for Edge Cluster Troubleshooting"
+description: "Learn how to deploy a Private Cloud Gateway (PCG) to an existing Kubernetes cluster."
+hide_table_of_contents: false
+sidebar_position: 1
+toc_min_heading_level: 2
+toc_max_heading_level: 3
+tags: ["edge", "troubleshooting", "support"]
+---
+When deploying or operating Edge clusters, you may encounter issues that require assistance from the SpectroCloud support team, such as Edge hosts failing to register, pod failures, or provisioning errors. To help our team troubleshoot these issues more effectively, follow this guide to collect support bundles and attach them to your support ticket.
+
+## Limitations
+
+- This guide applies only to connected installation mode, not airgap environments, since it requires internet access to run the troubleshooting script.
+
+## Prerequisites
+
+- You have connected to the host you need to troubleshoot, using SSH, direct terminal access, or another connection method.
+- The following tools are available on the host:
+    - `journalctl`
+    - `systemctl`
+    - (Optional) `kubectl` (required for the full output of `support-bundle-infra.sh`)
+- (Optional) A valid `kubeconfig` file is configured (required for the full output of `support-bundle-infra.sh`)
+
+## Run the Troubleshooting Scripts
+
+### Run the Script to Collect Cluster Logs
+The `support-bundle-infra.sh` script collects cluster-level diagnostics. Follow the steps below on a host with a valid `kubeconfig` and `kubectl` installed, typically a control plane node.
+
+1. Set the path to your `kubeconfig` file.
+
+    ```bash
+    export KUBECONFIG=/etc/kubernetes/admin.conf
+    ```
+
+2. Run the `support-bundle-infra.sh` script.
+
+    ```bash
+    curl -sSL https://software.spectrocloud.com/scripts/support-bundle-infra.sh | bash
+    ```
+    If the script runs successfully, it creates a file in your home directory. The file name follows the pattern `<cluster name>-<YYYY-MM-DD>_<HH_MM_SS>.tar.gz`. If the script is unable to determine the cluster name, it defaults to `spectro-cluster`. One of the messages the terminal displays contains the name of the created file.
+
+    ```bash
+    Logs are archived in spectro-cluster-2025-05-13_16_50_50.tar.gz
+    ``` 
+
+3. Copy the file to your local computer. The command below serves as an example of how to copy the file `spectro-cluster-2025-05-13_16_50_50.tar.gz` from the `kairos@10.10.150.150` host to your `Downloads` folder. Run the command on the machine to which you want to copy the file.
+
+    ```bash
+    scp kairos@10.10.150.150:~/spectro-cluster-2025-05-13_16_50_50.tar.gz ~/Downloads/
+    ```
+
+### Run the Script to Collect Edge Host Logs
+The `support-bundle-edge.sh` script collects host-level diagnostics from an Edge node and, if available, includes Kubernetes data accessible locally on that host.
+Follow the steps below on every Edge host you want to troubleshoot.
+
+1. (Optional) Set the path to your `kubeconfig` file.
+
+    ```bash
+    export KUBECONFIG=/etc/kubernetes/admin.conf
+    ```
+
+    If you do not perform this step, the script defaults to using `/run/kubeconfig` if it exists.
+
+2. Run the `support-bundle-edge.sh` script as a user with sudo privileges.
+
+    ```bash
+    curl -sSL https://software.spectrocloud.com/scripts/support-bundle-edge.sh | sudo bash
+    ```
+    The table below contains the optional flags you can use when running the script.
path: docs/docs-content/troubleshooting/edge/collect-support-bundles.md
user: login: github-actions[bot]
body: 🚫 **[vale]** <sub>reported by [reviewdog](https://github.com/reviewdog/reviewdog) :dog:</sub><br>[spectrocloud-docs-internal.ableism] Avoid using ableism terms. Use 'operating' instead of 'running'.
created_at: 2025-05-13T17:53:03Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,127 @@
+---
+sidebar_label: "Collect Support Bundles"
+title: "Collect Support Bundles for Edge Cluster Troubleshooting"
+description: "Learn how to deploy a Private Cloud Gateway (PCG) to an existing Kubernetes cluster."
+hide_table_of_contents: false
+sidebar_position: 1
+toc_min_heading_level: 2
+toc_max_heading_level: 3
+tags: ["edge", "troubleshooting", "support"]
+---
+When deploying or operating Edge clusters, you may encounter issues that require assistance from the SpectroCloud support team, such as Edge hosts failing to register, pod failures, or provisioning errors. To help our team troubleshoot these issues more effectively, follow this guide to collect support bundles and attach them to your support ticket.
+
+## Limitations
+
+- This guide applies only to connected installation mode, not airgap environments, since it requires internet access to run the troubleshooting script.
+
+## Prerequisites
+
+- You have connected to the host you need to troubleshoot, using SSH, direct terminal access, or another connection method.
+- The following tools are available on the host:
+    - `journalctl`
+    - `systemctl`
+    - (Optional) `kubectl` (required for the full output of `support-bundle-infra.sh`)
+- (Optional) A valid `kubeconfig` file is configured (required for the full output of `support-bundle-infra.sh`)
+
+## Run the Troubleshooting Scripts
+
+### Run the Script to Collect Cluster Logs
+The `support-bundle-infra.sh` script collects cluster-level diagnostics. Follow the steps below on a host with a valid `kubeconfig` and `kubectl` installed, typically a control plane node.
+
+1. Set the path to your `kubeconfig` file.
+
+    ```bash
+    export KUBECONFIG=/etc/kubernetes/admin.conf
+    ```
+
+2. Run the `support-bundle-infra.sh` script.
+
+    ```bash
+    curl -sSL https://software.spectrocloud.com/scripts/support-bundle-infra.sh | bash
+    ```
+    If the script runs successfully, it creates a file in your home directory. The file name follows the pattern `<cluster name>-<YYYY-MM-DD>_<HH_MM_SS>.tar.gz`. If the script is unable to determine the cluster name, it defaults to `spectro-cluster`. One of the messages the terminal displays contains the name of the created file.
+
+    ```bash
+    Logs are archived in spectro-cluster-2025-05-13_16_50_50.tar.gz
+    ``` 
+
+3. Copy the file to your local computer. The command below serves as an example of how to copy the file `spectro-cluster-2025-05-13_16_50_50.tar.gz` from the `kairos@10.10.150.150` host to your `Downloads` folder. Run the command on the machine to which you want to copy the file.
+
+    ```bash
+    scp kairos@10.10.150.150:~/spectro-cluster-2025-05-13_16_50_50.tar.gz ~/Downloads/
+    ```
+
+### Run the Script to Collect Edge Host Logs
+The `support-bundle-edge.sh` script collects host-level diagnostics from an Edge node and, if available, includes Kubernetes data accessible locally on that host.
+Follow the steps below on every Edge host you want to troubleshoot.
+
+1. (Optional) Set the path to your `kubeconfig` file.
+
+    ```bash
+    export KUBECONFIG=/etc/kubernetes/admin.conf
+    ```
+
+    If you do not perform this step, the script defaults to using `/run/kubeconfig` if it exists.
+
+2. Run the `support-bundle-edge.sh` script as a user with sudo privileges.
+
+    ```bash
+    curl -sSL https://software.spectrocloud.com/scripts/support-bundle-edge.sh | sudo bash
+    ```
+    The table below contains the optional flags you can use when running the script.
+
+    | **Full Flag Name**          | **Short Flag Name** | **Description** | **Example** |
+    | --------------------------- | ------------------- |  -------------- | ------------|
+    | `--start-days-ago`          | `-s`                | Number of days before now to begin collecting journald logs from. | `-s 7`| 
path: docs/docs-content/troubleshooting/edge/collect-support-bundles.md
user: login: github-actions[bot]
body: 🚫 **[vale]** <sub>reported by [reviewdog](https://github.com/reviewdog/reviewdog) :dog:</sub><br>[Vale.Spelling] Did you really mean 'journald'?
created_at: 2025-05-13T17:53:03Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,127 @@
+---
+sidebar_label: "Collect Support Bundles"
+title: "Collect Support Bundles for Edge Cluster Troubleshooting"
+description: "Learn how to deploy a Private Cloud Gateway (PCG) to an existing Kubernetes cluster."
+hide_table_of_contents: false
+sidebar_position: 1
+toc_min_heading_level: 2
+toc_max_heading_level: 3
+tags: ["edge", "troubleshooting", "support"]
+---
+When deploying or operating Edge clusters, you may encounter issues that require assistance from the SpectroCloud support team, such as Edge hosts failing to register, pod failures, or provisioning errors. To help our team troubleshoot these issues more effectively, follow this guide to collect support bundles and attach them to your support ticket.
+
+## Limitations
+
+- This guide applies only to connected installation mode, not airgap environments, since it requires internet access to run the troubleshooting script.
+
+## Prerequisites
+
+- You have connected to the host you need to troubleshoot, using SSH, direct terminal access, or another connection method.
+- The following tools are available on the host:
+    - `journalctl`
+    - `systemctl`
+    - (Optional) `kubectl` (required for the full output of `support-bundle-infra.sh`)
+- (Optional) A valid `kubeconfig` file is configured (required for the full output of `support-bundle-infra.sh`)
+
+## Run the Troubleshooting Scripts
+
+### Run the Script to Collect Cluster Logs
+The `support-bundle-infra.sh` script collects cluster-level diagnostics. Follow the steps below on a host with a valid `kubeconfig` and `kubectl` installed, typically a control plane node.
+
+1. Set the path to your `kubeconfig` file.
+
+    ```bash
+    export KUBECONFIG=/etc/kubernetes/admin.conf
+    ```
+
+2. Run the `support-bundle-infra.sh` script.
+
+    ```bash
+    curl -sSL https://software.spectrocloud.com/scripts/support-bundle-infra.sh | bash
+    ```
+    If the script runs successfully, it creates a file in your home directory. The file name follows the pattern `<cluster name>-<YYYY-MM-DD>_<HH_MM_SS>.tar.gz`. If the script is unable to determine the cluster name, it defaults to `spectro-cluster`. One of the messages the terminal displays contains the name of the created file.
+
+    ```bash
+    Logs are archived in spectro-cluster-2025-05-13_16_50_50.tar.gz
+    ``` 
+
+3. Copy the file to your local computer. The command below serves as an example of how to copy the file `spectro-cluster-2025-05-13_16_50_50.tar.gz` from the `kairos@10.10.150.150` host to your `Downloads` folder. Run the command on the machine to which you want to copy the file.
+
+    ```bash
+    scp kairos@10.10.150.150:~/spectro-cluster-2025-05-13_16_50_50.tar.gz ~/Downloads/
+    ```
+
+### Run the Script to Collect Edge Host Logs
+The `support-bundle-edge.sh` script collects host-level diagnostics from an Edge node and, if available, includes Kubernetes data accessible locally on that host.
+Follow the steps below on every Edge host you want to troubleshoot.
+
+1. (Optional) Set the path to your `kubeconfig` file.
+
+    ```bash
+    export KUBECONFIG=/etc/kubernetes/admin.conf
+    ```
+
+    If you do not perform this step, the script defaults to using `/run/kubeconfig` if it exists.
+
+2. Run the `support-bundle-edge.sh` script as a user with sudo privileges.
+
+    ```bash
+    curl -sSL https://software.spectrocloud.com/scripts/support-bundle-edge.sh | sudo bash
+    ```
+    The table below contains the optional flags you can use when running the script.
+
+    | **Full Flag Name**          | **Short Flag Name** | **Description** | **Example** |
+    | --------------------------- | ------------------- |  -------------- | ------------|
+    | `--start-days-ago`          | `-s`                | Number of days before now to begin collecting journald logs from. | `-s 7`| 
+    | `--end-days-ago`            | `-e`                | Number of days before now to stop collecting journald logs. The value must be smaller than `-s`. | `-e 5`| 
path: docs/docs-content/troubleshooting/edge/collect-support-bundles.md
user: login: github-actions[bot]
body: 🚫 **[vale]** <sub>reported by [reviewdog](https://github.com/reviewdog/reviewdog) :dog:</sub><br>[Vale.Spelling] Did you really mean 'journald'?
created_at: 2025-05-13T17:53:03Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,127 @@
+---
+sidebar_label: "Collect Support Bundles"
+title: "Collect Support Bundles for Edge Cluster Troubleshooting"
+description: "Learn how to deploy a Private Cloud Gateway (PCG) to an existing Kubernetes cluster."
+hide_table_of_contents: false
+sidebar_position: 1
+toc_min_heading_level: 2
+toc_max_heading_level: 3
+tags: ["edge", "troubleshooting", "support"]
+---
+When deploying or operating Edge clusters, you may encounter issues that require assistance from the SpectroCloud support team, such as Edge hosts failing to register, pod failures, or provisioning errors. To help our team troubleshoot these issues more effectively, follow this guide to collect support bundles and attach them to your support ticket.
+
+## Limitations
+
+- This guide applies only to connected installation mode, not airgap environments, since it requires internet access to run the troubleshooting script.
+
+## Prerequisites
+
+- You have connected to the host you need to troubleshoot, using SSH, direct terminal access, or another connection method.
+- The following tools are available on the host:
+    - `journalctl`
+    - `systemctl`
+    - (Optional) `kubectl` (required for the full output of `support-bundle-infra.sh`)
+- (Optional) A valid `kubeconfig` file is configured (required for the full output of `support-bundle-infra.sh`)
+
+## Run the Troubleshooting Scripts
+
+### Run the Script to Collect Cluster Logs
+The `support-bundle-infra.sh` script collects cluster-level diagnostics. Follow the steps below on a host with a valid `kubeconfig` and `kubectl` installed, typically a control plane node.
+
+1. Set the path to your `kubeconfig` file.
+
+    ```bash
+    export KUBECONFIG=/etc/kubernetes/admin.conf
+    ```
+
+2. Run the `support-bundle-infra.sh` script.
+
+    ```bash
+    curl -sSL https://software.spectrocloud.com/scripts/support-bundle-infra.sh | bash
+    ```
+    If the script runs successfully, it creates a file in your home directory. The file name follows the pattern `<cluster name>-<YYYY-MM-DD>_<HH_MM_SS>.tar.gz`. If the script is unable to determine the cluster name, it defaults to `spectro-cluster`. One of the messages the terminal displays contains the name of the created file.
+
+    ```bash
+    Logs are archived in spectro-cluster-2025-05-13_16_50_50.tar.gz
+    ``` 
+
+3. Copy the file to your local computer. The command below serves as an example of how to copy the file `spectro-cluster-2025-05-13_16_50_50.tar.gz` from the `kairos@10.10.150.150` host to your `Downloads` folder. Run the command on the machine to which you want to copy the file.
+
+    ```bash
+    scp kairos@10.10.150.150:~/spectro-cluster-2025-05-13_16_50_50.tar.gz ~/Downloads/
+    ```
+
+### Run the Script to Collect Edge Host Logs
+The `support-bundle-edge.sh` script collects host-level diagnostics from an Edge node and, if available, includes Kubernetes data accessible locally on that host.
+Follow the steps below on every Edge host you want to troubleshoot.
+
+1. (Optional) Set the path to your `kubeconfig` file.
+
+    ```bash
+    export KUBECONFIG=/etc/kubernetes/admin.conf
+    ```
+
+    If you do not perform this step, the script defaults to using `/run/kubeconfig` if it exists.
+
+2. Run the `support-bundle-edge.sh` script as a user with sudo privileges.
+
+    ```bash
+    curl -sSL https://software.spectrocloud.com/scripts/support-bundle-edge.sh | sudo bash
+    ```
+    The table below contains the optional flags you can use when running the script.
+
+    | **Full Flag Name**          | **Short Flag Name** | **Description** | **Example** |
+    | --------------------------- | ------------------- |  -------------- | ------------|
+    | `--start-days-ago`          | `-s`                | Number of days before now to begin collecting journald logs from. | `-s 7`| 
+    | `--end-days-ago`            | `-e`                | Number of days before now to stop collecting journald logs. The value must be smaller than `-s`. | `-e 5`| 
+    | `--start-date`              | `-S`                | Start date for journald log collection. | `-S 2024-01-01`| 
path: docs/docs-content/troubleshooting/edge/collect-support-bundles.md
user: login: github-actions[bot]
body: 🚫 **[vale]** <sub>reported by [reviewdog](https://github.com/reviewdog/reviewdog) :dog:</sub><br>[Vale.Spelling] Did you really mean 'journald'?
created_at: 2025-05-13T17:53:03Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,127 @@
+---
+sidebar_label: "Collect Support Bundles"
+title: "Collect Support Bundles for Edge Cluster Troubleshooting"
+description: "Learn how to deploy a Private Cloud Gateway (PCG) to an existing Kubernetes cluster."
+hide_table_of_contents: false
+sidebar_position: 1
+toc_min_heading_level: 2
+toc_max_heading_level: 3
+tags: ["edge", "troubleshooting", "support"]
+---
+When deploying or operating Edge clusters, you may encounter issues that require assistance from the SpectroCloud support team, such as Edge hosts failing to register, pod failures, or provisioning errors. To help our team troubleshoot these issues more effectively, follow this guide to collect support bundles and attach them to your support ticket.
+
+## Limitations
+
+- This guide applies only to connected installation mode, not airgap environments, since it requires internet access to run the troubleshooting script.
+
+## Prerequisites
+
+- You have connected to the host you need to troubleshoot, using SSH, direct terminal access, or another connection method.
+- The following tools are available on the host:
+    - `journalctl`
+    - `systemctl`
+    - (Optional) `kubectl` (required for the full output of `support-bundle-infra.sh`)
+- (Optional) A valid `kubeconfig` file is configured (required for the full output of `support-bundle-infra.sh`)
+
+## Run the Troubleshooting Scripts
+
+### Run the Script to Collect Cluster Logs
+The `support-bundle-infra.sh` script collects cluster-level diagnostics. Follow the steps below on a host with a valid `kubeconfig` and `kubectl` installed, typically a control plane node.
+
+1. Set the path to your `kubeconfig` file.
+
+    ```bash
+    export KUBECONFIG=/etc/kubernetes/admin.conf
+    ```
+
+2. Run the `support-bundle-infra.sh` script.
+
+    ```bash
+    curl -sSL https://software.spectrocloud.com/scripts/support-bundle-infra.sh | bash
+    ```
+    If the script runs successfully, it creates a file in your home directory. The file name follows the pattern `<cluster name>-<YYYY-MM-DD>_<HH_MM_SS>.tar.gz`. If the script is unable to determine the cluster name, it defaults to `spectro-cluster`. One of the messages the terminal displays contains the name of the created file.
+
+    ```bash
+    Logs are archived in spectro-cluster-2025-05-13_16_50_50.tar.gz
+    ``` 
+
+3. Copy the file to your local computer. The command below serves as an example of how to copy the file `spectro-cluster-2025-05-13_16_50_50.tar.gz` from the `kairos@10.10.150.150` host to your `Downloads` folder. Run the command on the machine to which you want to copy the file.
+
+    ```bash
+    scp kairos@10.10.150.150:~/spectro-cluster-2025-05-13_16_50_50.tar.gz ~/Downloads/
+    ```
+
+### Run the Script to Collect Edge Host Logs
+The `support-bundle-edge.sh` script collects host-level diagnostics from an Edge node and, if available, includes Kubernetes data accessible locally on that host.
+Follow the steps below on every Edge host you want to troubleshoot.
+
+1. (Optional) Set the path to your `kubeconfig` file.
+
+    ```bash
+    export KUBECONFIG=/etc/kubernetes/admin.conf
+    ```
+
+    If you do not perform this step, the script defaults to using `/run/kubeconfig` if it exists.
+
+2. Run the `support-bundle-edge.sh` script as a user with sudo privileges.
+
+    ```bash
+    curl -sSL https://software.spectrocloud.com/scripts/support-bundle-edge.sh | sudo bash
+    ```
+    The table below contains the optional flags you can use when running the script.
+
+    | **Full Flag Name**          | **Short Flag Name** | **Description** | **Example** |
+    | --------------------------- | ------------------- |  -------------- | ------------|
+    | `--start-days-ago`          | `-s`                | Number of days before now to begin collecting journald logs from. | `-s 7`| 
+    | `--end-days-ago`            | `-e`                | Number of days before now to stop collecting journald logs. The value must be smaller than `-s`. | `-e 5`| 
+    | `--start-date`              | `-S`                | Start date for journald log collection. | `-S 2024-01-01`| 
+    | `--end-date`                | `-E`                | End date for journald log collection. Must be later than `-S`. | `-E 2024-01-06`|
path: docs/docs-content/troubleshooting/edge/collect-support-bundles.md
user: login: github-actions[bot]
body: 🚫 **[vale]** <sub>reported by [reviewdog](https://github.com/reviewdog/reviewdog) :dog:</sub><br>[Vale.Spelling] Did you really mean 'journald'?
created_at: 2025-05-13T17:53:03Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,127 @@
+---
+sidebar_label: "Collect Support Bundles"
+title: "Collect Support Bundles for Edge Cluster Troubleshooting"
+description: "Learn how to deploy a Private Cloud Gateway (PCG) to an existing Kubernetes cluster."
+hide_table_of_contents: false
+sidebar_position: 1
+toc_min_heading_level: 2
+toc_max_heading_level: 3
+tags: ["edge", "troubleshooting", "support"]
+---
+When deploying or operating Edge clusters, you may encounter issues that require assistance from the SpectroCloud support team, such as Edge hosts failing to register, pod failures, or provisioning errors. To help our team troubleshoot these issues more effectively, follow this guide to collect support bundles and attach them to your support ticket.
+
+## Limitations
+
+- This guide applies only to connected installation mode, not airgap environments, since it requires internet access to run the troubleshooting script.
+
+## Prerequisites
+
+- You have connected to the host you need to troubleshoot, using SSH, direct terminal access, or another connection method.
+- The following tools are available on the host:
+    - `journalctl`
+    - `systemctl`
+    - (Optional) `kubectl` (required for the full output of `support-bundle-infra.sh`)
+- (Optional) A valid `kubeconfig` file is configured (required for the full output of `support-bundle-infra.sh`)
+
+## Run the Troubleshooting Scripts
+
+### Run the Script to Collect Cluster Logs
+The `support-bundle-infra.sh` script collects cluster-level diagnostics. Follow the steps below on a host with a valid `kubeconfig` and `kubectl` installed, typically a control plane node.
+
+1. Set the path to your `kubeconfig` file.
+
+    ```bash
+    export KUBECONFIG=/etc/kubernetes/admin.conf
+    ```
+
+2. Run the `support-bundle-infra.sh` script.
+
+    ```bash
+    curl -sSL https://software.spectrocloud.com/scripts/support-bundle-infra.sh | bash
+    ```
+    If the script runs successfully, it creates a file in your home directory. The file name follows the pattern `<cluster name>-<YYYY-MM-DD>_<HH_MM_SS>.tar.gz`. If the script is unable to determine the cluster name, it defaults to `spectro-cluster`. One of the messages the terminal displays contains the name of the created file.
+
+    ```bash
+    Logs are archived in spectro-cluster-2025-05-13_16_50_50.tar.gz
+    ``` 
+
+3. Copy the file to your local computer. The command below serves as an example of how to copy the file `spectro-cluster-2025-05-13_16_50_50.tar.gz` from the `kairos@10.10.150.150` host to your `Downloads` folder. Run the command on the machine to which you want to copy the file.
+
+    ```bash
+    scp kairos@10.10.150.150:~/spectro-cluster-2025-05-13_16_50_50.tar.gz ~/Downloads/
+    ```
+
+### Run the Script to Collect Edge Host Logs
+The `support-bundle-edge.sh` script collects host-level diagnostics from an Edge node and, if available, includes Kubernetes data accessible locally on that host.
+Follow the steps below on every Edge host you want to troubleshoot.
+
+1. (Optional) Set the path to your `kubeconfig` file.
+
+    ```bash
+    export KUBECONFIG=/etc/kubernetes/admin.conf
+    ```
+
+    If you do not perform this step, the script defaults to using `/run/kubeconfig` if it exists.
+
+2. Run the `support-bundle-edge.sh` script as a user with sudo privileges.
+
+    ```bash
+    curl -sSL https://software.spectrocloud.com/scripts/support-bundle-edge.sh | sudo bash
+    ```
+    The table below contains the optional flags you can use when running the script.
+
+    | **Full Flag Name**          | **Short Flag Name** | **Description** | **Example** |
+    | --------------------------- | ------------------- |  -------------- | ------------|
+    | `--start-days-ago`          | `-s`                | Number of days before now to begin collecting journald logs from. | `-s 7`| 
+    | `--end-days-ago`            | `-e`                | Number of days before now to stop collecting journald logs. The value must be smaller than `-s`. | `-e 5`| 
+    | `--start-date`              | `-S`                | Start date for journald log collection. | `-S 2024-01-01`| 
+    | `--end-date`                | `-E`                | End date for journald log collection. Must be later than `-S`. | `-E 2024-01-06`|
+    | `--namespaces`              | `-n`                | Additional namespaces to collect logs from. | `-n hello-universe,hello-world`|
+    | `--resources-namespaced`    | `-r`                | Additional namespace-scoped resources to collect. | `-r certificates.cert-manager.io` |
+    | `--resources-cluster-scoped`| `-R`                | Additional cluster-scoped resources to collect. | `-R clusterissuers.cert-manager.io` |
+    | `--journald-services`       | `-j`                | Additional journald services to include in logs. | `-j cloud-init,systemd-resolved`| 
path: docs/docs-content/troubleshooting/edge/collect-support-bundles.md
user: login: github-actions[bot]
body: 🚫 **[vale]** <sub>reported by [reviewdog](https://github.com/reviewdog/reviewdog) :dog:</sub><br>[Vale.Spelling] Did you really mean 'journald'?
created_at: 2025-05-13T17:53:03Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,127 @@
+---
+sidebar_label: "Collect Support Bundles"
+title: "Collect Support Bundles for Edge Cluster Troubleshooting"
+description: "Learn how to deploy a Private Cloud Gateway (PCG) to an existing Kubernetes cluster."
+hide_table_of_contents: false
+sidebar_position: 1
+toc_min_heading_level: 2
+toc_max_heading_level: 3
+tags: ["edge", "troubleshooting", "support"]
+---
+When deploying or operating Edge clusters, you may encounter issues that require assistance from the SpectroCloud support team, such as Edge hosts failing to register, pod failures, or provisioning errors. To help our team troubleshoot these issues more effectively, follow this guide to collect support bundles and attach them to your support ticket.
+
+## Limitations
+
+- This guide applies only to connected installation mode, not airgap environments, since it requires internet access to run the troubleshooting script.
+
+## Prerequisites
+
+- You have connected to the host you need to troubleshoot, using SSH, direct terminal access, or another connection method.
+- The following tools are available on the host:
+    - `journalctl`
+    - `systemctl`
+    - (Optional) `kubectl` (required for the full output of `support-bundle-infra.sh`)
+- (Optional) A valid `kubeconfig` file is configured (required for the full output of `support-bundle-infra.sh`)
+
+## Run the Troubleshooting Scripts
+
+### Run the Script to Collect Cluster Logs
+The `support-bundle-infra.sh` script collects cluster-level diagnostics. Follow the steps below on a host with a valid `kubeconfig` and `kubectl` installed, typically a control plane node.
+
+1. Set the path to your `kubeconfig` file.
+
+    ```bash
+    export KUBECONFIG=/etc/kubernetes/admin.conf
+    ```
+
+2. Run the `support-bundle-infra.sh` script.
+
+    ```bash
+    curl -sSL https://software.spectrocloud.com/scripts/support-bundle-infra.sh | bash
+    ```
+    If the script runs successfully, it creates a file in your home directory. The file name follows the pattern `<cluster name>-<YYYY-MM-DD>_<HH_MM_SS>.tar.gz`. If the script is unable to determine the cluster name, it defaults to `spectro-cluster`. One of the messages the terminal displays contains the name of the created file.
+
+    ```bash
+    Logs are archived in spectro-cluster-2025-05-13_16_50_50.tar.gz
+    ``` 
+
+3. Copy the file to your local computer. The command below serves as an example of how to copy the file `spectro-cluster-2025-05-13_16_50_50.tar.gz` from the `kairos@10.10.150.150` host to your `Downloads` folder. Run the command on the machine to which you want to copy the file.
+
+    ```bash
+    scp kairos@10.10.150.150:~/spectro-cluster-2025-05-13_16_50_50.tar.gz ~/Downloads/
+    ```
+
+### Run the Script to Collect Edge Host Logs
+The `support-bundle-edge.sh` script collects host-level diagnostics from an Edge node and, if available, includes Kubernetes data accessible locally on that host.
+Follow the steps below on every Edge host you want to troubleshoot.
+
+1. (Optional) Set the path to your `kubeconfig` file.
+
+    ```bash
+    export KUBECONFIG=/etc/kubernetes/admin.conf
+    ```
+
+    If you do not perform this step, the script defaults to using `/run/kubeconfig` if it exists.
+
+2. Run the `support-bundle-edge.sh` script as a user with sudo privileges.
+
+    ```bash
+    curl -sSL https://software.spectrocloud.com/scripts/support-bundle-edge.sh | sudo bash
+    ```
+    The table below contains the optional flags you can use when running the script.
+
+    | **Full Flag Name**          | **Short Flag Name** | **Description** | **Example** |
+    | --------------------------- | ------------------- |  -------------- | ------------|
+    | `--start-days-ago`          | `-s`                | Number of days before now to begin collecting journald logs from. | `-s 7`| 
+    | `--end-days-ago`            | `-e`                | Number of days before now to stop collecting journald logs. The value must be smaller than `-s`. | `-e 5`| 
+    | `--start-date`              | `-S`                | Start date for journald log collection. | `-S 2024-01-01`| 
+    | `--end-date`                | `-E`                | End date for journald log collection. Must be later than `-S`. | `-E 2024-01-06`|
+    | `--namespaces`              | `-n`                | Additional namespaces to collect logs from. | `-n hello-universe,hello-world`|
+    | `--resources-namespaced`    | `-r`                | Additional namespace-scoped resources to collect. | `-r certificates.cert-manager.io` |
+    | `--resources-cluster-scoped`| `-R`                | Additional cluster-scoped resources to collect. | `-R clusterissuers.cert-manager.io` |
+    | `--journald-services`       | `-j`                | Additional journald services to include in logs. | `-j cloud-init,systemd-resolved`| 
+
+
+    If the script runs successfully, it creates a file in the `/opt/spectrocloud/logs` directory. The file name follows the pattern `<hostname>-<YYYY-MM-DD>_<HH_MM_SS>.tar.gz`. One of the messages the terminal displays contains the created file's name and its path.
+
+    ```bash
+    Logs are archived in /opt/spectrocloud/logs/edge-e965384209c2d45078a29480e90bd275-2025-05-13_16_58_20.tar.gz
+    ``` 
+
+    :::info
+
+    The script collects only Helm release secrets from Spectro Cloud namespaces and excludes other Kubernetes secrets to protect sensitive data.
+
+    :::
+
+3. Copy the file to your local computer. The command below serves as an example of how to copy the file `edge-e965384209c2d45078a29480e90bd275-2025-05-13_16_58_20.tar.gz` from the `kairos@10.10.150.150` host to your `Downloads` folder. Run the command on the machine to which you want to copy the file.
path: docs/docs-content/troubleshooting/edge/collect-support-bundles.md
user: login: github-actions[bot]
body: 🚫 **[vale]** <sub>reported by [reviewdog](https://github.com/reviewdog/reviewdog) :dog:</sub><br>[spectrocloud-docs-internal.ableism] Avoid using ableism terms. Use 'issue' instead of 'Run'.
created_at: 2025-05-13T17:53:04Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,127 @@
+---
+sidebar_label: "Collect Support Bundles"
+title: "Collect Support Bundles for Edge Cluster Troubleshooting"
+description: "Learn how to deploy a Private Cloud Gateway (PCG) to an existing Kubernetes cluster."
+hide_table_of_contents: false
+sidebar_position: 1
+toc_min_heading_level: 2
+toc_max_heading_level: 3
+tags: ["edge", "troubleshooting", "support"]
+---
+When deploying or operating Edge clusters, you may encounter issues that require assistance from the SpectroCloud support team, such as Edge hosts failing to register, pod failures, or provisioning errors. To help our team troubleshoot these issues more effectively, follow this guide to collect support bundles and attach them to your support ticket.
+
+## Limitations
+
+- This guide applies only to connected installation mode, not airgap environments, since it requires internet access to run the troubleshooting script.
+
+## Prerequisites
+
+- You have connected to the host you need to troubleshoot, using SSH, direct terminal access, or another connection method.
+- The following tools are available on the host:
+    - `journalctl`
+    - `systemctl`
+    - (Optional) `kubectl` (required for the full output of `support-bundle-infra.sh`)
+- (Optional) A valid `kubeconfig` file is configured (required for the full output of `support-bundle-infra.sh`)
+
+## Run the Troubleshooting Scripts
+
+### Run the Script to Collect Cluster Logs
+The `support-bundle-infra.sh` script collects cluster-level diagnostics. Follow the steps below on a host with a valid `kubeconfig` and `kubectl` installed, typically a control plane node.
+
+1. Set the path to your `kubeconfig` file.
+
+    ```bash
+    export KUBECONFIG=/etc/kubernetes/admin.conf
+    ```
+
+2. Run the `support-bundle-infra.sh` script.
+
+    ```bash
+    curl -sSL https://software.spectrocloud.com/scripts/support-bundle-infra.sh | bash
+    ```
+    If the script runs successfully, it creates a file in your home directory. The file name follows the pattern `<cluster name>-<YYYY-MM-DD>_<HH_MM_SS>.tar.gz`. If the script is unable to determine the cluster name, it defaults to `spectro-cluster`. One of the messages the terminal displays contains the name of the created file.
+
+    ```bash
+    Logs are archived in spectro-cluster-2025-05-13_16_50_50.tar.gz
+    ``` 
+
+3. Copy the file to your local computer. The command below serves as an example of how to copy the file `spectro-cluster-2025-05-13_16_50_50.tar.gz` from the `kairos@10.10.150.150` host to your `Downloads` folder. Run the command on the machine to which you want to copy the file.
+
+    ```bash
+    scp kairos@10.10.150.150:~/spectro-cluster-2025-05-13_16_50_50.tar.gz ~/Downloads/
+    ```
+
+### Run the Script to Collect Edge Host Logs
+The `support-bundle-edge.sh` script collects host-level diagnostics from an Edge node and, if available, includes Kubernetes data accessible locally on that host.
+Follow the steps below on every Edge host you want to troubleshoot.
+
+1. (Optional) Set the path to your `kubeconfig` file.
+
+    ```bash
+    export KUBECONFIG=/etc/kubernetes/admin.conf
+    ```
+
+    If you do not perform this step, the script defaults to using `/run/kubeconfig` if it exists.
+
+2. Run the `support-bundle-edge.sh` script as a user with sudo privileges.
+
+    ```bash
+    curl -sSL https://software.spectrocloud.com/scripts/support-bundle-edge.sh | sudo bash
+    ```
+    The table below contains the optional flags you can use when running the script.
+
+    | **Full Flag Name**          | **Short Flag Name** | **Description** | **Example** |
+    | --------------------------- | ------------------- |  -------------- | ------------|
+    | `--start-days-ago`          | `-s`                | Number of days before now to begin collecting journald logs from. | `-s 7`| 
+    | `--end-days-ago`            | `-e`                | Number of days before now to stop collecting journald logs. The value must be smaller than `-s`. | `-e 5`| 
+    | `--start-date`              | `-S`                | Start date for journald log collection. | `-S 2024-01-01`| 
+    | `--end-date`                | `-E`                | End date for journald log collection. Must be later than `-S`. | `-E 2024-01-06`|
+    | `--namespaces`              | `-n`                | Additional namespaces to collect logs from. | `-n hello-universe,hello-world`|
+    | `--resources-namespaced`    | `-r`                | Additional namespace-scoped resources to collect. | `-r certificates.cert-manager.io` |
+    | `--resources-cluster-scoped`| `-R`                | Additional cluster-scoped resources to collect. | `-R clusterissuers.cert-manager.io` |
+    | `--journald-services`       | `-j`                | Additional journald services to include in logs. | `-j cloud-init,systemd-resolved`| 
+
+
+    If the script runs successfully, it creates a file in the `/opt/spectrocloud/logs` directory. The file name follows the pattern `<hostname>-<YYYY-MM-DD>_<HH_MM_SS>.tar.gz`. One of the messages the terminal displays contains the created file's name and its path.
+
+    ```bash
+    Logs are archived in /opt/spectrocloud/logs/edge-e965384209c2d45078a29480e90bd275-2025-05-13_16_58_20.tar.gz
+    ``` 
+
+    :::info
+
+    The script collects only Helm release secrets from Spectro Cloud namespaces and excludes other Kubernetes secrets to protect sensitive data.
+
+    :::
+
+3. Copy the file to your local computer. The command below serves as an example of how to copy the file `edge-e965384209c2d45078a29480e90bd275-2025-05-13_16_58_20.tar.gz` from the `kairos@10.10.150.150` host to your `Downloads` folder. Run the command on the machine to which you want to copy the file.
+
+    ```bash
+    scp kairos@10.10.150.150:/opt/spectrocloud/logs/edge-e965384209c2d45078a29480e90bd275-2025-05-13_16_58_20.tar.gz ~/Downloads/
+    ```
+
+## Validate
+
+Review the files you copied to the `Downloads` folder. The scripts archive the collected logs into compressed tarballs TAR.GAR.
+
+Extract the file named in the format `<cluster name>-<YYYY-MM-DD>_<HH_MM_SS>.tar.gz` and verify it contains the `k8s` folder with the following subfolders:
path: docs/docs-content/troubleshooting/edge/collect-support-bundles.md
user: login: github-actions[bot]
body: 🚫 **[vale]** <sub>reported by [reviewdog](https://github.com/reviewdog/reviewdog) :dog:</sub><br>[Vale.Spelling] Did you really mean 'subfolders'?
created_at: 2025-05-13T17:53:04Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,127 @@
+---
+sidebar_label: "Collect Support Bundles"
+title: "Collect Support Bundles for Edge Cluster Troubleshooting"
+description: "Learn how to deploy a Private Cloud Gateway (PCG) to an existing Kubernetes cluster."
+hide_table_of_contents: false
+sidebar_position: 1
+toc_min_heading_level: 2
+toc_max_heading_level: 3
+tags: ["edge", "troubleshooting", "support"]
+---
+When deploying or operating Edge clusters, you may encounter issues that require assistance from the SpectroCloud support team, such as Edge hosts failing to register, pod failures, or provisioning errors. To help our team troubleshoot these issues more effectively, follow this guide to collect support bundles and attach them to your support ticket.
+
+## Limitations
+
+- This guide applies only to connected installation mode, not airgap environments, since it requires internet access to run the troubleshooting script.
+
+## Prerequisites
+
+- You have connected to the host you need to troubleshoot, using SSH, direct terminal access, or another connection method.
+- The following tools are available on the host:
+    - `journalctl`
+    - `systemctl`
+    - (Optional) `kubectl` (required for the full output of `support-bundle-infra.sh`)
+- (Optional) A valid `kubeconfig` file is configured (required for the full output of `support-bundle-infra.sh`)
+
+## Run the Troubleshooting Scripts
+
+### Run the Script to Collect Cluster Logs
+The `support-bundle-infra.sh` script collects cluster-level diagnostics. Follow the steps below on a host with a valid `kubeconfig` and `kubectl` installed, typically a control plane node.
+
+1. Set the path to your `kubeconfig` file.
+
+    ```bash
+    export KUBECONFIG=/etc/kubernetes/admin.conf
+    ```
+
+2. Run the `support-bundle-infra.sh` script.
+
+    ```bash
+    curl -sSL https://software.spectrocloud.com/scripts/support-bundle-infra.sh | bash
+    ```
+    If the script runs successfully, it creates a file in your home directory. The file name follows the pattern `<cluster name>-<YYYY-MM-DD>_<HH_MM_SS>.tar.gz`. If the script is unable to determine the cluster name, it defaults to `spectro-cluster`. One of the messages the terminal displays contains the name of the created file.
+
+    ```bash
+    Logs are archived in spectro-cluster-2025-05-13_16_50_50.tar.gz
+    ``` 
+
+3. Copy the file to your local computer. The command below serves as an example of how to copy the file `spectro-cluster-2025-05-13_16_50_50.tar.gz` from the `kairos@10.10.150.150` host to your `Downloads` folder. Run the command on the machine to which you want to copy the file.
+
+    ```bash
+    scp kairos@10.10.150.150:~/spectro-cluster-2025-05-13_16_50_50.tar.gz ~/Downloads/
+    ```
+
+### Run the Script to Collect Edge Host Logs
+The `support-bundle-edge.sh` script collects host-level diagnostics from an Edge node and, if available, includes Kubernetes data accessible locally on that host.
+Follow the steps below on every Edge host you want to troubleshoot.
+
+1. (Optional) Set the path to your `kubeconfig` file.
+
+    ```bash
+    export KUBECONFIG=/etc/kubernetes/admin.conf
+    ```
+
+    If you do not perform this step, the script defaults to using `/run/kubeconfig` if it exists.
+
+2. Run the `support-bundle-edge.sh` script as a user with sudo privileges.
+
+    ```bash
+    curl -sSL https://software.spectrocloud.com/scripts/support-bundle-edge.sh | sudo bash
+    ```
+    The table below contains the optional flags you can use when running the script.
+
+    | **Full Flag Name**          | **Short Flag Name** | **Description** | **Example** |
+    | --------------------------- | ------------------- |  -------------- | ------------|
+    | `--start-days-ago`          | `-s`                | Number of days before now to begin collecting journald logs from. | `-s 7`| 
+    | `--end-days-ago`            | `-e`                | Number of days before now to stop collecting journald logs. The value must be smaller than `-s`. | `-e 5`| 
+    | `--start-date`              | `-S`                | Start date for journald log collection. | `-S 2024-01-01`| 
+    | `--end-date`                | `-E`                | End date for journald log collection. Must be later than `-S`. | `-E 2024-01-06`|
+    | `--namespaces`              | `-n`                | Additional namespaces to collect logs from. | `-n hello-universe,hello-world`|
+    | `--resources-namespaced`    | `-r`                | Additional namespace-scoped resources to collect. | `-r certificates.cert-manager.io` |
+    | `--resources-cluster-scoped`| `-R`                | Additional cluster-scoped resources to collect. | `-R clusterissuers.cert-manager.io` |
+    | `--journald-services`       | `-j`                | Additional journald services to include in logs. | `-j cloud-init,systemd-resolved`| 
path: docs/docs-content/troubleshooting/edge/collect-support-bundles.md
user: login: svetlana-efimova
body: Yes I did
created_at: 2025-05-13T17:54:45Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,127 @@
+---
+sidebar_label: "Collect Support Bundles"
+title: "Collect Support Bundles for Edge Cluster Troubleshooting"
+description: "Learn how to deploy a Private Cloud Gateway (PCG) to an existing Kubernetes cluster."
+hide_table_of_contents: false
+sidebar_position: 1
+toc_min_heading_level: 2
+toc_max_heading_level: 3
+tags: ["edge", "troubleshooting", "support"]
+---
+When deploying or operating Edge clusters, you may encounter issues that require assistance from the SpectroCloud support team, such as Edge hosts failing to register, pod failures, or provisioning errors. To help our team troubleshoot these issues more effectively, follow this guide to collect support bundles and attach them to your support ticket.
+
+## Limitations
+
+- This guide applies only to connected installation mode, not airgap environments, since it requires internet access to run the troubleshooting script.
path: docs/docs-content/troubleshooting/edge/collect-support-bundles.md
user: login: svetlana-efimova
body: According to the Style guide, “Run” in the context of “run a program” or “run a command” is widely understood and is generally considered inclusive. 
created_at: 2025-05-13T17:55:25Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,127 @@
+---
+sidebar_label: "Collect Support Bundles"
+title: "Collect Support Bundles for Edge Cluster Troubleshooting"
+description: "Learn how to deploy a Private Cloud Gateway (PCG) to an existing Kubernetes cluster."
+hide_table_of_contents: false
+sidebar_position: 1
+toc_min_heading_level: 2
+toc_max_heading_level: 3
+tags: ["edge", "troubleshooting", "support"]
+---
+When deploying or operating Edge clusters, you may encounter issues that require assistance from the SpectroCloud support team, such as Edge hosts failing to register, pod failures, or provisioning errors. To help our team troubleshoot these issues more effectively, follow this guide to collect support bundles and attach them to your support ticket.
+
+## Limitations
+
+- This guide applies only to connected installation mode, not airgap environments, since it requires internet access to run the troubleshooting script.
+
+## Prerequisites
+
+- You have connected to the host you need to troubleshoot, using SSH, direct terminal access, or another connection method.
+- The following tools are available on the host:
+    - `journalctl`
+    - `systemctl`
+    - (Optional) `kubectl` (required for the full output of `support-bundle-infra.sh`)
+- (Optional) A valid `kubeconfig` file is configured (required for the full output of `support-bundle-infra.sh`)
+
+## Run the Troubleshooting Scripts
+
+### Run the Script to Collect Cluster Logs
+The `support-bundle-infra.sh` script collects cluster-level diagnostics. Follow the steps below on a host with a valid `kubeconfig` and `kubectl` installed, typically a control plane node.
+
+1. Set the path to your `kubeconfig` file.
+
+    ```bash
+    export KUBECONFIG=/etc/kubernetes/admin.conf
+    ```
+
+2. Run the `support-bundle-infra.sh` script.
+
+    ```bash
+    curl -sSL https://software.spectrocloud.com/scripts/support-bundle-infra.sh | bash
+    ```
+    If the script runs successfully, it creates a file in your home directory. The file name follows the pattern `<cluster name>-<YYYY-MM-DD>_<HH_MM_SS>.tar.gz`. If the script is unable to determine the cluster name, it defaults to `spectro-cluster`. One of the messages the terminal displays contains the name of the created file.
+
+    ```bash
+    Logs are archived in spectro-cluster-2025-05-13_16_50_50.tar.gz
+    ``` 
+
+3. Copy the file to your local computer. The command below serves as an example of how to copy the file `spectro-cluster-2025-05-13_16_50_50.tar.gz` from the `kairos@10.10.150.150` host to your `Downloads` folder. Run the command on the machine to which you want to copy the file.
+
+    ```bash
+    scp kairos@10.10.150.150:~/spectro-cluster-2025-05-13_16_50_50.tar.gz ~/Downloads/
+    ```
+
+### Run the Script to Collect Edge Host Logs
+The `support-bundle-edge.sh` script collects host-level diagnostics from an Edge node and, if available, includes Kubernetes data accessible locally on that host.
+Follow the steps below on every Edge host you want to troubleshoot.
+
+1. (Optional) Set the path to your `kubeconfig` file.
+
+    ```bash
+    export KUBECONFIG=/etc/kubernetes/admin.conf
+    ```
+
+    If you do not perform this step, the script defaults to using `/run/kubeconfig` if it exists.
+
+2. Run the `support-bundle-edge.sh` script as a user with sudo privileges.
path: docs/docs-content/troubleshooting/edge/collect-support-bundles.md
user: login: svetlana-efimova
body: Yes I did
created_at: 2025-05-13T17:56:01Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,149 @@
+---
+sidebar_label: "Collect Support Bundles"
+title: "Collect Support Bundles for Edge Cluster Troubleshooting"
+description: "Learn how to deploy a Private Cloud Gateway (PCG) to an existing Kubernetes cluster."
+hide_table_of_contents: false
+sidebar_position: 1
+toc_min_heading_level: 2
+toc_max_heading_level: 3
+tags: ["edge", "troubleshooting", "support"]
+---
+
+When deploying or operating Edge clusters, you may encounter issues that require assistance from the SpectroCloud
path: docs/docs-content/troubleshooting/edge/collect-support-bundles.md
user: login: github-actions[bot]
body: 🚫 **[vale]** <sub>reported by [reviewdog](https://github.com/reviewdog/reviewdog) :dog:</sub><br>[spectrocloud-docs-internal.brand] Avoid using 'spectrocloud' outside of a URL format. Use 'Spectro Cloud' instead.
created_at: 2025-05-13T17:56:55Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,149 @@
+---
+sidebar_label: "Collect Support Bundles"
+title: "Collect Support Bundles for Edge Cluster Troubleshooting"
+description: "Learn how to deploy a Private Cloud Gateway (PCG) to an existing Kubernetes cluster."
+hide_table_of_contents: false
+sidebar_position: 1
+toc_min_heading_level: 2
+toc_max_heading_level: 3
+tags: ["edge", "troubleshooting", "support"]
+---
+
+When deploying or operating Edge clusters, you may encounter issues that require assistance from the SpectroCloud
+support team, such as Edge hosts failing to register, pod failures, or provisioning errors. To help our team
+troubleshoot these issues more effectively, follow this guide to collect support bundles and attach them to your support
+ticket.
+
+## Limitations
+
+- This guide applies only to connected installation mode, not airgap environments, since it requires internet access to
+  run the troubleshooting script.
path: docs/docs-content/troubleshooting/edge/collect-support-bundles.md
user: login: github-actions[bot]
body: 🚫 **[vale]** <sub>reported by [reviewdog](https://github.com/reviewdog/reviewdog) :dog:</sub><br>[spectrocloud-docs-internal.ableism] Avoid using ableism terms. Use 'issue' instead of 'run'.
created_at: 2025-05-13T17:56:55Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,149 @@
+---
+sidebar_label: "Collect Support Bundles"
+title: "Collect Support Bundles for Edge Cluster Troubleshooting"
+description: "Learn how to deploy a Private Cloud Gateway (PCG) to an existing Kubernetes cluster."
+hide_table_of_contents: false
+sidebar_position: 1
+toc_min_heading_level: 2
+toc_max_heading_level: 3
+tags: ["edge", "troubleshooting", "support"]
+---
+
+When deploying or operating Edge clusters, you may encounter issues that require assistance from the SpectroCloud
+support team, such as Edge hosts failing to register, pod failures, or provisioning errors. To help our team
+troubleshoot these issues more effectively, follow this guide to collect support bundles and attach them to your support
+ticket.
+
+## Limitations
+
+- This guide applies only to connected installation mode, not airgap environments, since it requires internet access to
+  run the troubleshooting script.
+
+## Prerequisites
+
+- You have connected to the host you need to troubleshoot, using SSH, direct terminal access, or another connection
+  method.
+- The following tools are available on the host:
+  - `journalctl`
+  - `systemctl`
+  - (Optional) `kubectl` (required for the full output of `support-bundle-infra.sh`)
+- (Optional) A valid `kubeconfig` file is configured (required for the full output of `support-bundle-infra.sh`)
+
+## Run the Troubleshooting Scripts
+
+### Run the Script to Collect Cluster Logs
+
+The `support-bundle-infra.sh` script collects cluster-level diagnostics. Follow the steps below on a host with a valid
+`kubeconfig` and `kubectl` installed, typically a control plane node.
+
+1. Set the path to your `kubeconfig` file.
+
+   ```bash
+   export KUBECONFIG=/etc/kubernetes/admin.conf
+   ```
+
+2. Run the `support-bundle-infra.sh` script.
+
+   ```bash
+   curl -sSL https://software.spectrocloud.com/scripts/support-bundle-infra.sh | bash
path: docs/docs-content/troubleshooting/edge/collect-support-bundles.md
user: login: github-actions[bot]
body: 🚫 **[vale]** <sub>reported by [reviewdog](https://github.com/reviewdog/reviewdog) :dog:</sub><br>[spectrocloud-docs-internal.longform] Avoid using the short form of commands. Replace the short form flag in 'curl -sSL' with the corresponding long form flag.
created_at: 2025-05-13T17:56:55Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,149 @@
+---
+sidebar_label: "Collect Support Bundles"
+title: "Collect Support Bundles for Edge Cluster Troubleshooting"
+description: "Learn how to deploy a Private Cloud Gateway (PCG) to an existing Kubernetes cluster."
+hide_table_of_contents: false
+sidebar_position: 1
+toc_min_heading_level: 2
+toc_max_heading_level: 3
+tags: ["edge", "troubleshooting", "support"]
+---
+
+When deploying or operating Edge clusters, you may encounter issues that require assistance from the SpectroCloud
+support team, such as Edge hosts failing to register, pod failures, or provisioning errors. To help our team
+troubleshoot these issues more effectively, follow this guide to collect support bundles and attach them to your support
+ticket.
+
+## Limitations
+
+- This guide applies only to connected installation mode, not airgap environments, since it requires internet access to
+  run the troubleshooting script.
+
+## Prerequisites
+
+- You have connected to the host you need to troubleshoot, using SSH, direct terminal access, or another connection
+  method.
+- The following tools are available on the host:
+  - `journalctl`
+  - `systemctl`
+  - (Optional) `kubectl` (required for the full output of `support-bundle-infra.sh`)
+- (Optional) A valid `kubeconfig` file is configured (required for the full output of `support-bundle-infra.sh`)
+
+## Run the Troubleshooting Scripts
+
+### Run the Script to Collect Cluster Logs
+
+The `support-bundle-infra.sh` script collects cluster-level diagnostics. Follow the steps below on a host with a valid
+`kubeconfig` and `kubectl` installed, typically a control plane node.
+
+1. Set the path to your `kubeconfig` file.
+
+   ```bash
+   export KUBECONFIG=/etc/kubernetes/admin.conf
+   ```
+
+2. Run the `support-bundle-infra.sh` script.
+
+   ```bash
+   curl -sSL https://software.spectrocloud.com/scripts/support-bundle-infra.sh | bash
+   ```
+
+   If the script runs successfully, it creates a file in your home directory. The file name follows the pattern
+   `<cluster name>-<YYYY-MM-DD>_<HH_MM_SS>.tar.gz`. If the script is unable to determine the cluster name, it defaults
+   to `spectro-cluster`. One of the messages the terminal displays contains the name of the created file.
+
+   ```bash
+   Logs are archived in spectro-cluster-2025-05-13_16_50_50.tar.gz
+   ```
+
+3. Copy the file to your local computer. The command below serves as an example of how to copy the file
+   `spectro-cluster-2025-05-13_16_50_50.tar.gz` from the `kairos@10.10.150.150` host to your `Downloads` folder. Run the
path: docs/docs-content/troubleshooting/edge/collect-support-bundles.md
user: login: github-actions[bot]
body: 🚫 **[vale]** <sub>reported by [reviewdog](https://github.com/reviewdog/reviewdog) :dog:</sub><br>[spectrocloud-docs-internal.ableism] Avoid using ableism terms. Use 'issue' instead of 'Run'.
created_at: 2025-05-13T17:56:55Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,149 @@
+---
+sidebar_label: "Collect Support Bundles"
+title: "Collect Support Bundles for Edge Cluster Troubleshooting"
+description: "Learn how to deploy a Private Cloud Gateway (PCG) to an existing Kubernetes cluster."
+hide_table_of_contents: false
+sidebar_position: 1
+toc_min_heading_level: 2
+toc_max_heading_level: 3
+tags: ["edge", "troubleshooting", "support"]
+---
+
+When deploying or operating Edge clusters, you may encounter issues that require assistance from the SpectroCloud
+support team, such as Edge hosts failing to register, pod failures, or provisioning errors. To help our team
+troubleshoot these issues more effectively, follow this guide to collect support bundles and attach them to your support
+ticket.
+
+## Limitations
+
+- This guide applies only to connected installation mode, not airgap environments, since it requires internet access to
+  run the troubleshooting script.
+
+## Prerequisites
+
+- You have connected to the host you need to troubleshoot, using SSH, direct terminal access, or another connection
+  method.
+- The following tools are available on the host:
+  - `journalctl`
+  - `systemctl`
+  - (Optional) `kubectl` (required for the full output of `support-bundle-infra.sh`)
+- (Optional) A valid `kubeconfig` file is configured (required for the full output of `support-bundle-infra.sh`)
+
+## Run the Troubleshooting Scripts
+
+### Run the Script to Collect Cluster Logs
+
+The `support-bundle-infra.sh` script collects cluster-level diagnostics. Follow the steps below on a host with a valid
+`kubeconfig` and `kubectl` installed, typically a control plane node.
+
+1. Set the path to your `kubeconfig` file.
+
+   ```bash
+   export KUBECONFIG=/etc/kubernetes/admin.conf
+   ```
+
+2. Run the `support-bundle-infra.sh` script.
+
+   ```bash
+   curl -sSL https://software.spectrocloud.com/scripts/support-bundle-infra.sh | bash
+   ```
+
+   If the script runs successfully, it creates a file in your home directory. The file name follows the pattern
+   `<cluster name>-<YYYY-MM-DD>_<HH_MM_SS>.tar.gz`. If the script is unable to determine the cluster name, it defaults
+   to `spectro-cluster`. One of the messages the terminal displays contains the name of the created file.
+
+   ```bash
+   Logs are archived in spectro-cluster-2025-05-13_16_50_50.tar.gz
+   ```
+
+3. Copy the file to your local computer. The command below serves as an example of how to copy the file
+   `spectro-cluster-2025-05-13_16_50_50.tar.gz` from the `kairos@10.10.150.150` host to your `Downloads` folder. Run the
+   command on the machine to which you want to copy the file.
+
+   ```bash
+   scp kairos@10.10.150.150:~/spectro-cluster-2025-05-13_16_50_50.tar.gz ~/Downloads/
+   ```
+
+### Run the Script to Collect Edge Host Logs
+
+The `support-bundle-edge.sh` script collects host-level diagnostics from an Edge node and, if available, includes
+Kubernetes data accessible locally on that host. Follow the steps below on every Edge host you want to troubleshoot.
+
+1. (Optional) Set the path to your `kubeconfig` file.
+
+   ```bash
+   export KUBECONFIG=/etc/kubernetes/admin.conf
+   ```
+
+   If you do not perform this step, the script defaults to using `/run/kubeconfig` if it exists.
+
+2. Run the `support-bundle-edge.sh` script as a user with sudo privileges.
+
+   ```bash
+   curl -sSL https://software.spectrocloud.com/scripts/support-bundle-edge.sh | sudo bash
path: docs/docs-content/troubleshooting/edge/collect-support-bundles.md
user: login: github-actions[bot]
body: 🚫 **[vale]** <sub>reported by [reviewdog](https://github.com/reviewdog/reviewdog) :dog:</sub><br>[spectrocloud-docs-internal.longform] Avoid using the short form of commands. Replace the short form flag in 'curl -sSL' with the corresponding long form flag.
created_at: 2025-05-13T17:56:55Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,149 @@
+---
+sidebar_label: "Collect Support Bundles"
+title: "Collect Support Bundles for Edge Cluster Troubleshooting"
+description: "Learn how to deploy a Private Cloud Gateway (PCG) to an existing Kubernetes cluster."
+hide_table_of_contents: false
+sidebar_position: 1
+toc_min_heading_level: 2
+toc_max_heading_level: 3
+tags: ["edge", "troubleshooting", "support"]
+---
+
+When deploying or operating Edge clusters, you may encounter issues that require assistance from the SpectroCloud
+support team, such as Edge hosts failing to register, pod failures, or provisioning errors. To help our team
+troubleshoot these issues more effectively, follow this guide to collect support bundles and attach them to your support
+ticket.
+
+## Limitations
+
+- This guide applies only to connected installation mode, not airgap environments, since it requires internet access to
+  run the troubleshooting script.
+
+## Prerequisites
+
+- You have connected to the host you need to troubleshoot, using SSH, direct terminal access, or another connection
+  method.
+- The following tools are available on the host:
+  - `journalctl`
+  - `systemctl`
+  - (Optional) `kubectl` (required for the full output of `support-bundle-infra.sh`)
+- (Optional) A valid `kubeconfig` file is configured (required for the full output of `support-bundle-infra.sh`)
+
+## Run the Troubleshooting Scripts
+
+### Run the Script to Collect Cluster Logs
+
+The `support-bundle-infra.sh` script collects cluster-level diagnostics. Follow the steps below on a host with a valid
+`kubeconfig` and `kubectl` installed, typically a control plane node.
+
+1. Set the path to your `kubeconfig` file.
+
+   ```bash
+   export KUBECONFIG=/etc/kubernetes/admin.conf
+   ```
+
+2. Run the `support-bundle-infra.sh` script.
+
+   ```bash
+   curl -sSL https://software.spectrocloud.com/scripts/support-bundle-infra.sh | bash
+   ```
+
+   If the script runs successfully, it creates a file in your home directory. The file name follows the pattern
+   `<cluster name>-<YYYY-MM-DD>_<HH_MM_SS>.tar.gz`. If the script is unable to determine the cluster name, it defaults
+   to `spectro-cluster`. One of the messages the terminal displays contains the name of the created file.
+
+   ```bash
+   Logs are archived in spectro-cluster-2025-05-13_16_50_50.tar.gz
+   ```
+
+3. Copy the file to your local computer. The command below serves as an example of how to copy the file
+   `spectro-cluster-2025-05-13_16_50_50.tar.gz` from the `kairos@10.10.150.150` host to your `Downloads` folder. Run the
+   command on the machine to which you want to copy the file.
+
+   ```bash
+   scp kairos@10.10.150.150:~/spectro-cluster-2025-05-13_16_50_50.tar.gz ~/Downloads/
+   ```
+
+### Run the Script to Collect Edge Host Logs
+
+The `support-bundle-edge.sh` script collects host-level diagnostics from an Edge node and, if available, includes
+Kubernetes data accessible locally on that host. Follow the steps below on every Edge host you want to troubleshoot.
+
+1. (Optional) Set the path to your `kubeconfig` file.
+
+   ```bash
+   export KUBECONFIG=/etc/kubernetes/admin.conf
+   ```
+
+   If you do not perform this step, the script defaults to using `/run/kubeconfig` if it exists.
+
+2. Run the `support-bundle-edge.sh` script as a user with sudo privileges.
+
+   ```bash
+   curl -sSL https://software.spectrocloud.com/scripts/support-bundle-edge.sh | sudo bash
+   ```
+
+   The table below contains the optional flags you can use when running the script.
path: docs/docs-content/troubleshooting/edge/collect-support-bundles.md
user: login: github-actions[bot]
body: 🚫 **[vale]** <sub>reported by [reviewdog](https://github.com/reviewdog/reviewdog) :dog:</sub><br>[spectrocloud-docs-internal.ableism] Avoid using ableism terms. Use 'operating' instead of 'running'.
created_at: 2025-05-13T17:56:55Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,149 @@
+---
+sidebar_label: "Collect Support Bundles"
+title: "Collect Support Bundles for Edge Cluster Troubleshooting"
+description: "Learn how to deploy a Private Cloud Gateway (PCG) to an existing Kubernetes cluster."
+hide_table_of_contents: false
+sidebar_position: 1
+toc_min_heading_level: 2
+toc_max_heading_level: 3
+tags: ["edge", "troubleshooting", "support"]
+---
+
+When deploying or operating Edge clusters, you may encounter issues that require assistance from the SpectroCloud
+support team, such as Edge hosts failing to register, pod failures, or provisioning errors. To help our team
+troubleshoot these issues more effectively, follow this guide to collect support bundles and attach them to your support
+ticket.
+
+## Limitations
+
+- This guide applies only to connected installation mode, not airgap environments, since it requires internet access to
+  run the troubleshooting script.
+
+## Prerequisites
+
+- You have connected to the host you need to troubleshoot, using SSH, direct terminal access, or another connection
+  method.
+- The following tools are available on the host:
+  - `journalctl`
+  - `systemctl`
+  - (Optional) `kubectl` (required for the full output of `support-bundle-infra.sh`)
+- (Optional) A valid `kubeconfig` file is configured (required for the full output of `support-bundle-infra.sh`)
+
+## Run the Troubleshooting Scripts
+
+### Run the Script to Collect Cluster Logs
+
+The `support-bundle-infra.sh` script collects cluster-level diagnostics. Follow the steps below on a host with a valid
+`kubeconfig` and `kubectl` installed, typically a control plane node.
+
+1. Set the path to your `kubeconfig` file.
+
+   ```bash
+   export KUBECONFIG=/etc/kubernetes/admin.conf
+   ```
+
+2. Run the `support-bundle-infra.sh` script.
+
+   ```bash
+   curl -sSL https://software.spectrocloud.com/scripts/support-bundle-infra.sh | bash
+   ```
+
+   If the script runs successfully, it creates a file in your home directory. The file name follows the pattern
+   `<cluster name>-<YYYY-MM-DD>_<HH_MM_SS>.tar.gz`. If the script is unable to determine the cluster name, it defaults
+   to `spectro-cluster`. One of the messages the terminal displays contains the name of the created file.
+
+   ```bash
+   Logs are archived in spectro-cluster-2025-05-13_16_50_50.tar.gz
+   ```
+
+3. Copy the file to your local computer. The command below serves as an example of how to copy the file
+   `spectro-cluster-2025-05-13_16_50_50.tar.gz` from the `kairos@10.10.150.150` host to your `Downloads` folder. Run the
+   command on the machine to which you want to copy the file.
+
+   ```bash
+   scp kairos@10.10.150.150:~/spectro-cluster-2025-05-13_16_50_50.tar.gz ~/Downloads/
+   ```
+
+### Run the Script to Collect Edge Host Logs
+
+The `support-bundle-edge.sh` script collects host-level diagnostics from an Edge node and, if available, includes
+Kubernetes data accessible locally on that host. Follow the steps below on every Edge host you want to troubleshoot.
+
+1. (Optional) Set the path to your `kubeconfig` file.
+
+   ```bash
+   export KUBECONFIG=/etc/kubernetes/admin.conf
+   ```
+
+   If you do not perform this step, the script defaults to using `/run/kubeconfig` if it exists.
+
+2. Run the `support-bundle-edge.sh` script as a user with sudo privileges.
+
+   ```bash
+   curl -sSL https://software.spectrocloud.com/scripts/support-bundle-edge.sh | sudo bash
+   ```
+
+   The table below contains the optional flags you can use when running the script.
+
+   | **Full Flag Name**           | **Short Flag Name** | **Description**                                                                                  | **Example**                         |
+   | ---------------------------- | ------------------- | ------------------------------------------------------------------------------------------------ | ----------------------------------- |
+   | `--start-days-ago`           | `-s`                | Number of days before now to begin collecting journald logs from.                                | `-s 7`                              |
path: docs/docs-content/troubleshooting/edge/collect-support-bundles.md
user: login: github-actions[bot]
body: 🚫 **[vale]** <sub>reported by [reviewdog](https://github.com/reviewdog/reviewdog) :dog:</sub><br>[Vale.Spelling] Did you really mean 'journald'?
created_at: 2025-05-13T17:56:56Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,149 @@
+---
+sidebar_label: "Collect Support Bundles"
+title: "Collect Support Bundles for Edge Cluster Troubleshooting"
+description: "Learn how to deploy a Private Cloud Gateway (PCG) to an existing Kubernetes cluster."
+hide_table_of_contents: false
+sidebar_position: 1
+toc_min_heading_level: 2
+toc_max_heading_level: 3
+tags: ["edge", "troubleshooting", "support"]
+---
+
+When deploying or operating Edge clusters, you may encounter issues that require assistance from the SpectroCloud
+support team, such as Edge hosts failing to register, pod failures, or provisioning errors. To help our team
+troubleshoot these issues more effectively, follow this guide to collect support bundles and attach them to your support
+ticket.
+
+## Limitations
+
+- This guide applies only to connected installation mode, not airgap environments, since it requires internet access to
+  run the troubleshooting script.
+
+## Prerequisites
+
+- You have connected to the host you need to troubleshoot, using SSH, direct terminal access, or another connection
+  method.
+- The following tools are available on the host:
+  - `journalctl`
+  - `systemctl`
+  - (Optional) `kubectl` (required for the full output of `support-bundle-infra.sh`)
+- (Optional) A valid `kubeconfig` file is configured (required for the full output of `support-bundle-infra.sh`)
+
+## Run the Troubleshooting Scripts
+
+### Run the Script to Collect Cluster Logs
+
+The `support-bundle-infra.sh` script collects cluster-level diagnostics. Follow the steps below on a host with a valid
+`kubeconfig` and `kubectl` installed, typically a control plane node.
+
+1. Set the path to your `kubeconfig` file.
+
+   ```bash
+   export KUBECONFIG=/etc/kubernetes/admin.conf
+   ```
+
+2. Run the `support-bundle-infra.sh` script.
+
+   ```bash
+   curl -sSL https://software.spectrocloud.com/scripts/support-bundle-infra.sh | bash
+   ```
+
+   If the script runs successfully, it creates a file in your home directory. The file name follows the pattern
+   `<cluster name>-<YYYY-MM-DD>_<HH_MM_SS>.tar.gz`. If the script is unable to determine the cluster name, it defaults
+   to `spectro-cluster`. One of the messages the terminal displays contains the name of the created file.
+
+   ```bash
+   Logs are archived in spectro-cluster-2025-05-13_16_50_50.tar.gz
+   ```
+
+3. Copy the file to your local computer. The command below serves as an example of how to copy the file
+   `spectro-cluster-2025-05-13_16_50_50.tar.gz` from the `kairos@10.10.150.150` host to your `Downloads` folder. Run the
+   command on the machine to which you want to copy the file.
+
+   ```bash
+   scp kairos@10.10.150.150:~/spectro-cluster-2025-05-13_16_50_50.tar.gz ~/Downloads/
+   ```
+
+### Run the Script to Collect Edge Host Logs
+
+The `support-bundle-edge.sh` script collects host-level diagnostics from an Edge node and, if available, includes
+Kubernetes data accessible locally on that host. Follow the steps below on every Edge host you want to troubleshoot.
+
+1. (Optional) Set the path to your `kubeconfig` file.
+
+   ```bash
+   export KUBECONFIG=/etc/kubernetes/admin.conf
+   ```
+
+   If you do not perform this step, the script defaults to using `/run/kubeconfig` if it exists.
+
+2. Run the `support-bundle-edge.sh` script as a user with sudo privileges.
+
+   ```bash
+   curl -sSL https://software.spectrocloud.com/scripts/support-bundle-edge.sh | sudo bash
+   ```
+
+   The table below contains the optional flags you can use when running the script.
+
+   | **Full Flag Name**           | **Short Flag Name** | **Description**                                                                                  | **Example**                         |
+   | ---------------------------- | ------------------- | ------------------------------------------------------------------------------------------------ | ----------------------------------- |
+   | `--start-days-ago`           | `-s`                | Number of days before now to begin collecting journald logs from.                                | `-s 7`                              |
+   | `--end-days-ago`             | `-e`                | Number of days before now to stop collecting journald logs. The value must be smaller than `-s`. | `-e 5`                              |
path: docs/docs-content/troubleshooting/edge/collect-support-bundles.md
user: login: github-actions[bot]
body: 🚫 **[vale]** <sub>reported by [reviewdog](https://github.com/reviewdog/reviewdog) :dog:</sub><br>[Vale.Spelling] Did you really mean 'journald'?
created_at: 2025-05-13T17:56:56Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,149 @@
+---
+sidebar_label: "Collect Support Bundles"
+title: "Collect Support Bundles for Edge Cluster Troubleshooting"
+description: "Learn how to deploy a Private Cloud Gateway (PCG) to an existing Kubernetes cluster."
+hide_table_of_contents: false
+sidebar_position: 1
+toc_min_heading_level: 2
+toc_max_heading_level: 3
+tags: ["edge", "troubleshooting", "support"]
+---
+
+When deploying or operating Edge clusters, you may encounter issues that require assistance from the SpectroCloud
+support team, such as Edge hosts failing to register, pod failures, or provisioning errors. To help our team
+troubleshoot these issues more effectively, follow this guide to collect support bundles and attach them to your support
+ticket.
+
+## Limitations
+
+- This guide applies only to connected installation mode, not airgap environments, since it requires internet access to
+  run the troubleshooting script.
+
+## Prerequisites
+
+- You have connected to the host you need to troubleshoot, using SSH, direct terminal access, or another connection
+  method.
+- The following tools are available on the host:
+  - `journalctl`
+  - `systemctl`
+  - (Optional) `kubectl` (required for the full output of `support-bundle-infra.sh`)
+- (Optional) A valid `kubeconfig` file is configured (required for the full output of `support-bundle-infra.sh`)
+
+## Run the Troubleshooting Scripts
+
+### Run the Script to Collect Cluster Logs
+
+The `support-bundle-infra.sh` script collects cluster-level diagnostics. Follow the steps below on a host with a valid
+`kubeconfig` and `kubectl` installed, typically a control plane node.
+
+1. Set the path to your `kubeconfig` file.
+
+   ```bash
+   export KUBECONFIG=/etc/kubernetes/admin.conf
+   ```
+
+2. Run the `support-bundle-infra.sh` script.
+
+   ```bash
+   curl -sSL https://software.spectrocloud.com/scripts/support-bundle-infra.sh | bash
+   ```
+
+   If the script runs successfully, it creates a file in your home directory. The file name follows the pattern
+   `<cluster name>-<YYYY-MM-DD>_<HH_MM_SS>.tar.gz`. If the script is unable to determine the cluster name, it defaults
+   to `spectro-cluster`. One of the messages the terminal displays contains the name of the created file.
+
+   ```bash
+   Logs are archived in spectro-cluster-2025-05-13_16_50_50.tar.gz
+   ```
+
+3. Copy the file to your local computer. The command below serves as an example of how to copy the file
+   `spectro-cluster-2025-05-13_16_50_50.tar.gz` from the `kairos@10.10.150.150` host to your `Downloads` folder. Run the
+   command on the machine to which you want to copy the file.
+
+   ```bash
+   scp kairos@10.10.150.150:~/spectro-cluster-2025-05-13_16_50_50.tar.gz ~/Downloads/
+   ```
+
+### Run the Script to Collect Edge Host Logs
+
+The `support-bundle-edge.sh` script collects host-level diagnostics from an Edge node and, if available, includes
+Kubernetes data accessible locally on that host. Follow the steps below on every Edge host you want to troubleshoot.
+
+1. (Optional) Set the path to your `kubeconfig` file.
+
+   ```bash
+   export KUBECONFIG=/etc/kubernetes/admin.conf
+   ```
+
+   If you do not perform this step, the script defaults to using `/run/kubeconfig` if it exists.
+
+2. Run the `support-bundle-edge.sh` script as a user with sudo privileges.
+
+   ```bash
+   curl -sSL https://software.spectrocloud.com/scripts/support-bundle-edge.sh | sudo bash
+   ```
+
+   The table below contains the optional flags you can use when running the script.
+
+   | **Full Flag Name**           | **Short Flag Name** | **Description**                                                                                  | **Example**                         |
+   | ---------------------------- | ------------------- | ------------------------------------------------------------------------------------------------ | ----------------------------------- |
+   | `--start-days-ago`           | `-s`                | Number of days before now to begin collecting journald logs from.                                | `-s 7`                              |
+   | `--end-days-ago`             | `-e`                | Number of days before now to stop collecting journald logs. The value must be smaller than `-s`. | `-e 5`                              |
+   | `--start-date`               | `-S`                | Start date for journald log collection.                                                          | `-S 2024-01-01`                     |
path: docs/docs-content/troubleshooting/edge/collect-support-bundles.md
user: login: github-actions[bot]
body: 🚫 **[vale]** <sub>reported by [reviewdog](https://github.com/reviewdog/reviewdog) :dog:</sub><br>[Vale.Spelling] Did you really mean 'journald'?
created_at: 2025-05-13T17:56:56Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,149 @@
+---
+sidebar_label: "Collect Support Bundles"
+title: "Collect Support Bundles for Edge Cluster Troubleshooting"
+description: "Learn how to deploy a Private Cloud Gateway (PCG) to an existing Kubernetes cluster."
+hide_table_of_contents: false
+sidebar_position: 1
+toc_min_heading_level: 2
+toc_max_heading_level: 3
+tags: ["edge", "troubleshooting", "support"]
+---
+
+When deploying or operating Edge clusters, you may encounter issues that require assistance from the SpectroCloud
+support team, such as Edge hosts failing to register, pod failures, or provisioning errors. To help our team
+troubleshoot these issues more effectively, follow this guide to collect support bundles and attach them to your support
+ticket.
+
+## Limitations
+
+- This guide applies only to connected installation mode, not airgap environments, since it requires internet access to
+  run the troubleshooting script.
+
+## Prerequisites
+
+- You have connected to the host you need to troubleshoot, using SSH, direct terminal access, or another connection
+  method.
+- The following tools are available on the host:
+  - `journalctl`
+  - `systemctl`
+  - (Optional) `kubectl` (required for the full output of `support-bundle-infra.sh`)
+- (Optional) A valid `kubeconfig` file is configured (required for the full output of `support-bundle-infra.sh`)
+
+## Run the Troubleshooting Scripts
+
+### Run the Script to Collect Cluster Logs
+
+The `support-bundle-infra.sh` script collects cluster-level diagnostics. Follow the steps below on a host with a valid
+`kubeconfig` and `kubectl` installed, typically a control plane node.
+
+1. Set the path to your `kubeconfig` file.
+
+   ```bash
+   export KUBECONFIG=/etc/kubernetes/admin.conf
+   ```
+
+2. Run the `support-bundle-infra.sh` script.
+
+   ```bash
+   curl -sSL https://software.spectrocloud.com/scripts/support-bundle-infra.sh | bash
+   ```
+
+   If the script runs successfully, it creates a file in your home directory. The file name follows the pattern
+   `<cluster name>-<YYYY-MM-DD>_<HH_MM_SS>.tar.gz`. If the script is unable to determine the cluster name, it defaults
+   to `spectro-cluster`. One of the messages the terminal displays contains the name of the created file.
+
+   ```bash
+   Logs are archived in spectro-cluster-2025-05-13_16_50_50.tar.gz
+   ```
+
+3. Copy the file to your local computer. The command below serves as an example of how to copy the file
+   `spectro-cluster-2025-05-13_16_50_50.tar.gz` from the `kairos@10.10.150.150` host to your `Downloads` folder. Run the
+   command on the machine to which you want to copy the file.
+
+   ```bash
+   scp kairos@10.10.150.150:~/spectro-cluster-2025-05-13_16_50_50.tar.gz ~/Downloads/
+   ```
+
+### Run the Script to Collect Edge Host Logs
+
+The `support-bundle-edge.sh` script collects host-level diagnostics from an Edge node and, if available, includes
+Kubernetes data accessible locally on that host. Follow the steps below on every Edge host you want to troubleshoot.
+
+1. (Optional) Set the path to your `kubeconfig` file.
+
+   ```bash
+   export KUBECONFIG=/etc/kubernetes/admin.conf
+   ```
+
+   If you do not perform this step, the script defaults to using `/run/kubeconfig` if it exists.
+
+2. Run the `support-bundle-edge.sh` script as a user with sudo privileges.
+
+   ```bash
+   curl -sSL https://software.spectrocloud.com/scripts/support-bundle-edge.sh | sudo bash
+   ```
+
+   The table below contains the optional flags you can use when running the script.
+
+   | **Full Flag Name**           | **Short Flag Name** | **Description**                                                                                  | **Example**                         |
+   | ---------------------------- | ------------------- | ------------------------------------------------------------------------------------------------ | ----------------------------------- |
+   | `--start-days-ago`           | `-s`                | Number of days before now to begin collecting journald logs from.                                | `-s 7`                              |
+   | `--end-days-ago`             | `-e`                | Number of days before now to stop collecting journald logs. The value must be smaller than `-s`. | `-e 5`                              |
+   | `--start-date`               | `-S`                | Start date for journald log collection.                                                          | `-S 2024-01-01`                     |
+   | `--end-date`                 | `-E`                | End date for journald log collection. Must be later than `-S`.                                   | `-E 2024-01-06`                     |
path: docs/docs-content/troubleshooting/edge/collect-support-bundles.md
user: login: github-actions[bot]
body: 🚫 **[vale]** <sub>reported by [reviewdog](https://github.com/reviewdog/reviewdog) :dog:</sub><br>[Vale.Spelling] Did you really mean 'journald'?
created_at: 2025-05-13T17:56:56Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,149 @@
+---
+sidebar_label: "Collect Support Bundles"
+title: "Collect Support Bundles for Edge Cluster Troubleshooting"
+description: "Learn how to deploy a Private Cloud Gateway (PCG) to an existing Kubernetes cluster."
+hide_table_of_contents: false
+sidebar_position: 1
+toc_min_heading_level: 2
+toc_max_heading_level: 3
+tags: ["edge", "troubleshooting", "support"]
+---
+
+When deploying or operating Edge clusters, you may encounter issues that require assistance from the SpectroCloud
+support team, such as Edge hosts failing to register, pod failures, or provisioning errors. To help our team
+troubleshoot these issues more effectively, follow this guide to collect support bundles and attach them to your support
+ticket.
+
+## Limitations
+
+- This guide applies only to connected installation mode, not airgap environments, since it requires internet access to
+  run the troubleshooting script.
+
+## Prerequisites
+
+- You have connected to the host you need to troubleshoot, using SSH, direct terminal access, or another connection
+  method.
+- The following tools are available on the host:
+  - `journalctl`
+  - `systemctl`
+  - (Optional) `kubectl` (required for the full output of `support-bundle-infra.sh`)
+- (Optional) A valid `kubeconfig` file is configured (required for the full output of `support-bundle-infra.sh`)
+
+## Run the Troubleshooting Scripts
+
+### Run the Script to Collect Cluster Logs
+
+The `support-bundle-infra.sh` script collects cluster-level diagnostics. Follow the steps below on a host with a valid
+`kubeconfig` and `kubectl` installed, typically a control plane node.
+
+1. Set the path to your `kubeconfig` file.
+
+   ```bash
+   export KUBECONFIG=/etc/kubernetes/admin.conf
+   ```
+
+2. Run the `support-bundle-infra.sh` script.
+
+   ```bash
+   curl -sSL https://software.spectrocloud.com/scripts/support-bundle-infra.sh | bash
+   ```
+
+   If the script runs successfully, it creates a file in your home directory. The file name follows the pattern
+   `<cluster name>-<YYYY-MM-DD>_<HH_MM_SS>.tar.gz`. If the script is unable to determine the cluster name, it defaults
+   to `spectro-cluster`. One of the messages the terminal displays contains the name of the created file.
+
+   ```bash
+   Logs are archived in spectro-cluster-2025-05-13_16_50_50.tar.gz
+   ```
+
+3. Copy the file to your local computer. The command below serves as an example of how to copy the file
+   `spectro-cluster-2025-05-13_16_50_50.tar.gz` from the `kairos@10.10.150.150` host to your `Downloads` folder. Run the
+   command on the machine to which you want to copy the file.
+
+   ```bash
+   scp kairos@10.10.150.150:~/spectro-cluster-2025-05-13_16_50_50.tar.gz ~/Downloads/
+   ```
+
+### Run the Script to Collect Edge Host Logs
+
+The `support-bundle-edge.sh` script collects host-level diagnostics from an Edge node and, if available, includes
+Kubernetes data accessible locally on that host. Follow the steps below on every Edge host you want to troubleshoot.
+
+1. (Optional) Set the path to your `kubeconfig` file.
+
+   ```bash
+   export KUBECONFIG=/etc/kubernetes/admin.conf
+   ```
+
+   If you do not perform this step, the script defaults to using `/run/kubeconfig` if it exists.
+
+2. Run the `support-bundle-edge.sh` script as a user with sudo privileges.
+
+   ```bash
+   curl -sSL https://software.spectrocloud.com/scripts/support-bundle-edge.sh | sudo bash
+   ```
+
+   The table below contains the optional flags you can use when running the script.
+
+   | **Full Flag Name**           | **Short Flag Name** | **Description**                                                                                  | **Example**                         |
+   | ---------------------------- | ------------------- | ------------------------------------------------------------------------------------------------ | ----------------------------------- |
+   | `--start-days-ago`           | `-s`                | Number of days before now to begin collecting journald logs from.                                | `-s 7`                              |
+   | `--end-days-ago`             | `-e`                | Number of days before now to stop collecting journald logs. The value must be smaller than `-s`. | `-e 5`                              |
+   | `--start-date`               | `-S`                | Start date for journald log collection.                                                          | `-S 2024-01-01`                     |
+   | `--end-date`                 | `-E`                | End date for journald log collection. Must be later than `-S`.                                   | `-E 2024-01-06`                     |
+   | `--namespaces`               | `-n`                | Additional namespaces to collect logs from.                                                      | `-n hello-universe,hello-world`     |
+   | `--resources-namespaced`     | `-r`                | Additional namespace-scoped resources to collect.                                                | `-r certificates.cert-manager.io`   |
+   | `--resources-cluster-scoped` | `-R`                | Additional cluster-scoped resources to collect.                                                  | `-R clusterissuers.cert-manager.io` |
+   | `--journald-services`        | `-j`                | Additional journald services to include in logs.                                                 | `-j cloud-init,systemd-resolved`    |
path: docs/docs-content/troubleshooting/edge/collect-support-bundles.md
user: login: github-actions[bot]
body: 🚫 **[vale]** <sub>reported by [reviewdog](https://github.com/reviewdog/reviewdog) :dog:</sub><br>[Vale.Spelling] Did you really mean 'journald'?
created_at: 2025-05-13T17:56:56Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,149 @@
+---
+sidebar_label: "Collect Support Bundles"
+title: "Collect Support Bundles for Edge Cluster Troubleshooting"
+description: "Learn how to deploy a Private Cloud Gateway (PCG) to an existing Kubernetes cluster."
+hide_table_of_contents: false
+sidebar_position: 1
+toc_min_heading_level: 2
+toc_max_heading_level: 3
+tags: ["edge", "troubleshooting", "support"]
+---
+
+When deploying or operating Edge clusters, you may encounter issues that require assistance from the SpectroCloud
+support team, such as Edge hosts failing to register, pod failures, or provisioning errors. To help our team
+troubleshoot these issues more effectively, follow this guide to collect support bundles and attach them to your support
+ticket.
+
+## Limitations
+
+- This guide applies only to connected installation mode, not airgap environments, since it requires internet access to
+  run the troubleshooting script.
+
+## Prerequisites
+
+- You have connected to the host you need to troubleshoot, using SSH, direct terminal access, or another connection
+  method.
+- The following tools are available on the host:
+  - `journalctl`
+  - `systemctl`
+  - (Optional) `kubectl` (required for the full output of `support-bundle-infra.sh`)
+- (Optional) A valid `kubeconfig` file is configured (required for the full output of `support-bundle-infra.sh`)
+
+## Run the Troubleshooting Scripts
+
+### Run the Script to Collect Cluster Logs
+
+The `support-bundle-infra.sh` script collects cluster-level diagnostics. Follow the steps below on a host with a valid
+`kubeconfig` and `kubectl` installed, typically a control plane node.
+
+1. Set the path to your `kubeconfig` file.
+
+   ```bash
+   export KUBECONFIG=/etc/kubernetes/admin.conf
+   ```
+
+2. Run the `support-bundle-infra.sh` script.
+
+   ```bash
+   curl -sSL https://software.spectrocloud.com/scripts/support-bundle-infra.sh | bash
+   ```
+
+   If the script runs successfully, it creates a file in your home directory. The file name follows the pattern
+   `<cluster name>-<YYYY-MM-DD>_<HH_MM_SS>.tar.gz`. If the script is unable to determine the cluster name, it defaults
+   to `spectro-cluster`. One of the messages the terminal displays contains the name of the created file.
+
+   ```bash
+   Logs are archived in spectro-cluster-2025-05-13_16_50_50.tar.gz
+   ```
+
+3. Copy the file to your local computer. The command below serves as an example of how to copy the file
+   `spectro-cluster-2025-05-13_16_50_50.tar.gz` from the `kairos@10.10.150.150` host to your `Downloads` folder. Run the
+   command on the machine to which you want to copy the file.
+
+   ```bash
+   scp kairos@10.10.150.150:~/spectro-cluster-2025-05-13_16_50_50.tar.gz ~/Downloads/
+   ```
+
+### Run the Script to Collect Edge Host Logs
+
+The `support-bundle-edge.sh` script collects host-level diagnostics from an Edge node and, if available, includes
+Kubernetes data accessible locally on that host. Follow the steps below on every Edge host you want to troubleshoot.
+
+1. (Optional) Set the path to your `kubeconfig` file.
+
+   ```bash
+   export KUBECONFIG=/etc/kubernetes/admin.conf
+   ```
+
+   If you do not perform this step, the script defaults to using `/run/kubeconfig` if it exists.
+
+2. Run the `support-bundle-edge.sh` script as a user with sudo privileges.
+
+   ```bash
+   curl -sSL https://software.spectrocloud.com/scripts/support-bundle-edge.sh | sudo bash
+   ```
+
+   The table below contains the optional flags you can use when running the script.
+
+   | **Full Flag Name**           | **Short Flag Name** | **Description**                                                                                  | **Example**                         |
+   | ---------------------------- | ------------------- | ------------------------------------------------------------------------------------------------ | ----------------------------------- |
+   | `--start-days-ago`           | `-s`                | Number of days before now to begin collecting journald logs from.                                | `-s 7`                              |
+   | `--end-days-ago`             | `-e`                | Number of days before now to stop collecting journald logs. The value must be smaller than `-s`. | `-e 5`                              |
+   | `--start-date`               | `-S`                | Start date for journald log collection.                                                          | `-S 2024-01-01`                     |
+   | `--end-date`                 | `-E`                | End date for journald log collection. Must be later than `-S`.                                   | `-E 2024-01-06`                     |
+   | `--namespaces`               | `-n`                | Additional namespaces to collect logs from.                                                      | `-n hello-universe,hello-world`     |
+   | `--resources-namespaced`     | `-r`                | Additional namespace-scoped resources to collect.                                                | `-r certificates.cert-manager.io`   |
+   | `--resources-cluster-scoped` | `-R`                | Additional cluster-scoped resources to collect.                                                  | `-R clusterissuers.cert-manager.io` |
+   | `--journald-services`        | `-j`                | Additional journald services to include in logs.                                                 | `-j cloud-init,systemd-resolved`    |
+
+   If the script runs successfully, it creates a file in the `/opt/spectrocloud/logs` directory. The file name follows
+   the pattern `<hostname>-<YYYY-MM-DD>_<HH_MM_SS>.tar.gz`. One of the messages the terminal displays contains the
+   created file's name and its path.
+
+   ```bash
+   Logs are archived in /opt/spectrocloud/logs/edge-e965384209c2d45078a29480e90bd275-2025-05-13_16_58_20.tar.gz
+   ```
+
+   :::info
+
+   The script collects only Helm release secrets from Spectro Cloud namespaces and excludes other Kubernetes secrets to
+   protect sensitive data.
+
+   :::
+
+3. Copy the file to your local computer. The command below serves as an example of how to copy the file
+   `edge-e965384209c2d45078a29480e90bd275-2025-05-13_16_58_20.tar.gz` from the `kairos@10.10.150.150` host to your
+   `Downloads` folder. Run the command on the machine to which you want to copy the file.
path: docs/docs-content/troubleshooting/edge/collect-support-bundles.md
user: login: github-actions[bot]
body: 🚫 **[vale]** <sub>reported by [reviewdog](https://github.com/reviewdog/reviewdog) :dog:</sub><br>[spectrocloud-docs-internal.ableism] Avoid using ableism terms. Use 'issue' instead of 'Run'.
created_at: 2025-05-13T17:56:56Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,149 @@
+---
+sidebar_label: "Collect Support Bundles"
+title: "Collect Support Bundles for Edge Cluster Troubleshooting"
+description: "Learn how to deploy a Private Cloud Gateway (PCG) to an existing Kubernetes cluster."
+hide_table_of_contents: false
+sidebar_position: 1
+toc_min_heading_level: 2
+toc_max_heading_level: 3
+tags: ["edge", "troubleshooting", "support"]
+---
+
+When deploying or operating Edge clusters, you may encounter issues that require assistance from the SpectroCloud
+support team, such as Edge hosts failing to register, pod failures, or provisioning errors. To help our team
+troubleshoot these issues more effectively, follow this guide to collect support bundles and attach them to your support
+ticket.
+
+## Limitations
+
+- This guide applies only to connected installation mode, not airgap environments, since it requires internet access to
+  run the troubleshooting script.
+
+## Prerequisites
+
+- You have connected to the host you need to troubleshoot, using SSH, direct terminal access, or another connection
+  method.
+- The following tools are available on the host:
+  - `journalctl`
+  - `systemctl`
+  - (Optional) `kubectl` (required for the full output of `support-bundle-infra.sh`)
+- (Optional) A valid `kubeconfig` file is configured (required for the full output of `support-bundle-infra.sh`)
+
+## Run the Troubleshooting Scripts
+
+### Run the Script to Collect Cluster Logs
+
+The `support-bundle-infra.sh` script collects cluster-level diagnostics. Follow the steps below on a host with a valid
+`kubeconfig` and `kubectl` installed, typically a control plane node.
+
+1. Set the path to your `kubeconfig` file.
+
+   ```bash
+   export KUBECONFIG=/etc/kubernetes/admin.conf
+   ```
+
+2. Run the `support-bundle-infra.sh` script.
+
+   ```bash
+   curl -sSL https://software.spectrocloud.com/scripts/support-bundle-infra.sh | bash
+   ```
+
+   If the script runs successfully, it creates a file in your home directory. The file name follows the pattern
+   `<cluster name>-<YYYY-MM-DD>_<HH_MM_SS>.tar.gz`. If the script is unable to determine the cluster name, it defaults
+   to `spectro-cluster`. One of the messages the terminal displays contains the name of the created file.
+
+   ```bash
+   Logs are archived in spectro-cluster-2025-05-13_16_50_50.tar.gz
+   ```
+
+3. Copy the file to your local computer. The command below serves as an example of how to copy the file
+   `spectro-cluster-2025-05-13_16_50_50.tar.gz` from the `kairos@10.10.150.150` host to your `Downloads` folder. Run the
+   command on the machine to which you want to copy the file.
+
+   ```bash
+   scp kairos@10.10.150.150:~/spectro-cluster-2025-05-13_16_50_50.tar.gz ~/Downloads/
+   ```
+
+### Run the Script to Collect Edge Host Logs
+
+The `support-bundle-edge.sh` script collects host-level diagnostics from an Edge node and, if available, includes
+Kubernetes data accessible locally on that host. Follow the steps below on every Edge host you want to troubleshoot.
+
+1. (Optional) Set the path to your `kubeconfig` file.
+
+   ```bash
+   export KUBECONFIG=/etc/kubernetes/admin.conf
+   ```
+
+   If you do not perform this step, the script defaults to using `/run/kubeconfig` if it exists.
+
+2. Run the `support-bundle-edge.sh` script as a user with sudo privileges.
+
+   ```bash
+   curl -sSL https://software.spectrocloud.com/scripts/support-bundle-edge.sh | sudo bash
+   ```
+
+   The table below contains the optional flags you can use when running the script.
+
+   | **Full Flag Name**           | **Short Flag Name** | **Description**                                                                                  | **Example**                         |
+   | ---------------------------- | ------------------- | ------------------------------------------------------------------------------------------------ | ----------------------------------- |
+   | `--start-days-ago`           | `-s`                | Number of days before now to begin collecting journald logs from.                                | `-s 7`                              |
+   | `--end-days-ago`             | `-e`                | Number of days before now to stop collecting journald logs. The value must be smaller than `-s`. | `-e 5`                              |
+   | `--start-date`               | `-S`                | Start date for journald log collection.                                                          | `-S 2024-01-01`                     |
+   | `--end-date`                 | `-E`                | End date for journald log collection. Must be later than `-S`.                                   | `-E 2024-01-06`                     |
+   | `--namespaces`               | `-n`                | Additional namespaces to collect logs from.                                                      | `-n hello-universe,hello-world`     |
+   | `--resources-namespaced`     | `-r`                | Additional namespace-scoped resources to collect.                                                | `-r certificates.cert-manager.io`   |
+   | `--resources-cluster-scoped` | `-R`                | Additional cluster-scoped resources to collect.                                                  | `-R clusterissuers.cert-manager.io` |
+   | `--journald-services`        | `-j`                | Additional journald services to include in logs.                                                 | `-j cloud-init,systemd-resolved`    |
+
+   If the script runs successfully, it creates a file in the `/opt/spectrocloud/logs` directory. The file name follows
+   the pattern `<hostname>-<YYYY-MM-DD>_<HH_MM_SS>.tar.gz`. One of the messages the terminal displays contains the
+   created file's name and its path.
+
+   ```bash
+   Logs are archived in /opt/spectrocloud/logs/edge-e965384209c2d45078a29480e90bd275-2025-05-13_16_58_20.tar.gz
+   ```
+
+   :::info
+
+   The script collects only Helm release secrets from Spectro Cloud namespaces and excludes other Kubernetes secrets to
+   protect sensitive data.
+
+   :::
+
+3. Copy the file to your local computer. The command below serves as an example of how to copy the file
+   `edge-e965384209c2d45078a29480e90bd275-2025-05-13_16_58_20.tar.gz` from the `kairos@10.10.150.150` host to your
+   `Downloads` folder. Run the command on the machine to which you want to copy the file.
+
+   ```bash
+   scp kairos@10.10.150.150:/opt/spectrocloud/logs/edge-e965384209c2d45078a29480e90bd275-2025-05-13_16_58_20.tar.gz ~/Downloads/
+   ```
+
+## Validate
+
+Review the files you copied to the `Downloads` folder. The scripts archive the collected logs into compressed tarballs
+TAR.GAR.
+
+Extract the file named in the format `<cluster name>-<YYYY-MM-DD>_<HH_MM_SS>.tar.gz` and verify it contains the `k8s`
+folder with the following subfolders:
path: docs/docs-content/troubleshooting/edge/collect-support-bundles.md
user: login: github-actions[bot]
body: 🚫 **[vale]** <sub>reported by [reviewdog](https://github.com/reviewdog/reviewdog) :dog:</sub><br>[Vale.Spelling] Did you really mean 'subfolders'?
created_at: 2025-05-13T17:56:56Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,149 @@
+---
+sidebar_label: "Collect Support Bundles"
+title: "Collect Support Bundles for Edge Cluster Troubleshooting"
+description: "Learn how to deploy a Private Cloud Gateway (PCG) to an existing Kubernetes cluster."
+hide_table_of_contents: false
+sidebar_position: 1
+toc_min_heading_level: 2
+toc_max_heading_level: 3
+tags: ["edge", "troubleshooting", "support"]
+---
+
+When deploying or operating Edge clusters, you may encounter issues that require assistance from the SpectroCloud
+support team, such as Edge hosts failing to register, pod failures, or provisioning errors. To help our team
+troubleshoot these issues more effectively, follow this guide to collect support bundles and attach them to your support
+ticket.
+
+## Limitations
+
+- This guide applies only to connected installation mode, not airgap environments, since it requires internet access to
+  run the troubleshooting script.
+
+## Prerequisites
+
+- You have connected to the host you need to troubleshoot, using SSH, direct terminal access, or another connection
+  method.
+- The following tools are available on the host:
+  - `journalctl`
+  - `systemctl`
+  - (Optional) `kubectl` (required for the full output of `support-bundle-infra.sh`)
+- (Optional) A valid `kubeconfig` file is configured (required for the full output of `support-bundle-infra.sh`)
+
+## Run the Troubleshooting Scripts
+
+### Run the Script to Collect Cluster Logs
+
+The `support-bundle-infra.sh` script collects cluster-level diagnostics. Follow the steps below on a host with a valid
+`kubeconfig` and `kubectl` installed, typically a control plane node.
+
+1. Set the path to your `kubeconfig` file.
+
+   ```bash
+   export KUBECONFIG=/etc/kubernetes/admin.conf
+   ```
+
+2. Run the `support-bundle-infra.sh` script.
+
+   ```bash
+   curl -sSL https://software.spectrocloud.com/scripts/support-bundle-infra.sh | bash
+   ```
+
+   If the script runs successfully, it creates a file in your home directory. The file name follows the pattern
+   `<cluster name>-<YYYY-MM-DD>_<HH_MM_SS>.tar.gz`. If the script is unable to determine the cluster name, it defaults
+   to `spectro-cluster`. One of the messages the terminal displays contains the name of the created file.
+
+   ```bash
+   Logs are archived in spectro-cluster-2025-05-13_16_50_50.tar.gz
+   ```
+
+3. Copy the file to your local computer. The command below serves as an example of how to copy the file
+   `spectro-cluster-2025-05-13_16_50_50.tar.gz` from the `kairos@10.10.150.150` host to your `Downloads` folder. Run the
+   command on the machine to which you want to copy the file.
+
+   ```bash
+   scp kairos@10.10.150.150:~/spectro-cluster-2025-05-13_16_50_50.tar.gz ~/Downloads/
+   ```
+
+### Run the Script to Collect Edge Host Logs
+
+The `support-bundle-edge.sh` script collects host-level diagnostics from an Edge node and, if available, includes
+Kubernetes data accessible locally on that host. Follow the steps below on every Edge host you want to troubleshoot.
+
+1. (Optional) Set the path to your `kubeconfig` file.
+
+   ```bash
+   export KUBECONFIG=/etc/kubernetes/admin.conf
+   ```
+
+   If you do not perform this step, the script defaults to using `/run/kubeconfig` if it exists.
+
+2. Run the `support-bundle-edge.sh` script as a user with sudo privileges.
+
+   ```bash
+   curl -sSL https://software.spectrocloud.com/scripts/support-bundle-edge.sh | sudo bash
+   ```
+
+   The table below contains the optional flags you can use when running the script.
+
+   | **Full Flag Name**           | **Short Flag Name** | **Description**                                                                                  | **Example**                         |
+   | ---------------------------- | ------------------- | ------------------------------------------------------------------------------------------------ | ----------------------------------- |
+   | `--start-days-ago`           | `-s`                | Number of days before now to begin collecting journald logs from.                                | `-s 7`                              |
+   | `--end-days-ago`             | `-e`                | Number of days before now to stop collecting journald logs. The value must be smaller than `-s`. | `-e 5`                              |
+   | `--start-date`               | `-S`                | Start date for journald log collection.                                                          | `-S 2024-01-01`                     |
+   | `--end-date`                 | `-E`                | End date for journald log collection. Must be later than `-S`.                                   | `-E 2024-01-06`                     |
+   | `--namespaces`               | `-n`                | Additional namespaces to collect logs from.                                                      | `-n hello-universe,hello-world`     |
+   | `--resources-namespaced`     | `-r`                | Additional namespace-scoped resources to collect.                                                | `-r certificates.cert-manager.io`   |
+   | `--resources-cluster-scoped` | `-R`                | Additional cluster-scoped resources to collect.                                                  | `-R clusterissuers.cert-manager.io` |
+   | `--journald-services`        | `-j`                | Additional journald services to include in logs.                                                 | `-j cloud-init,systemd-resolved`    |
+
+   If the script runs successfully, it creates a file in the `/opt/spectrocloud/logs` directory. The file name follows
+   the pattern `<hostname>-<YYYY-MM-DD>_<HH_MM_SS>.tar.gz`. One of the messages the terminal displays contains the
+   created file's name and its path.
+
+   ```bash
+   Logs are archived in /opt/spectrocloud/logs/edge-e965384209c2d45078a29480e90bd275-2025-05-13_16_58_20.tar.gz
+   ```
+
+   :::info
+
+   The script collects only Helm release secrets from Spectro Cloud namespaces and excludes other Kubernetes secrets to
+   protect sensitive data.
+
+   :::
+
+3. Copy the file to your local computer. The command below serves as an example of how to copy the file
+   `edge-e965384209c2d45078a29480e90bd275-2025-05-13_16_58_20.tar.gz` from the `kairos@10.10.150.150` host to your
+   `Downloads` folder. Run the command on the machine to which you want to copy the file.
+
+   ```bash
+   scp kairos@10.10.150.150:/opt/spectrocloud/logs/edge-e965384209c2d45078a29480e90bd275-2025-05-13_16_58_20.tar.gz ~/Downloads/
+   ```
+
+## Validate
+
+Review the files you copied to the `Downloads` folder. The scripts archive the collected logs into compressed tarballs
+TAR.GAR.
+
+Extract the file named in the format `<cluster name>-<YYYY-MM-DD>_<HH_MM_SS>.tar.gz` and verify it contains the `k8s`
+folder with the following subfolders:
path: docs/docs-content/troubleshooting/edge/collect-support-bundles.md
user: login: svetlana-efimova
body: Yes I did
created_at: 2025-05-13T18:06:20Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,127 @@
+---
+sidebar_label: "Collect Support Bundles"
+title: "Collect Support Bundles for Edge Cluster Troubleshooting"
+description: "Learn how to deploy a Private Cloud Gateway (PCG) to an existing Kubernetes cluster."
+hide_table_of_contents: false
+sidebar_position: 1
+toc_min_heading_level: 2
+toc_max_heading_level: 3
+tags: ["edge", "troubleshooting", "support"]
+---
+When deploying or operating Edge clusters, you may encounter issues that require assistance from the SpectroCloud support team, such as Edge hosts failing to register, pod failures, or provisioning errors. To help our team troubleshoot these issues more effectively, follow this guide to collect support bundles and attach them to your support ticket.
+
+## Limitations
+
+- This guide applies only to connected installation mode, not airgap environments, since it requires internet access to run the troubleshooting script.
+
+## Prerequisites
+
+- You have connected to the host you need to troubleshoot, using SSH, direct terminal access, or another connection method.
+- The following tools are available on the host:
+    - `journalctl`
+    - `systemctl`
+    - (Optional) `kubectl` (required for the full output of `support-bundle-infra.sh`)
+- (Optional) A valid `kubeconfig` file is configured (required for the full output of `support-bundle-infra.sh`)
+
+## Run the Troubleshooting Scripts
+
+### Run the Script to Collect Cluster Logs
+The `support-bundle-infra.sh` script collects cluster-level diagnostics. Follow the steps below on a host with a valid `kubeconfig` and `kubectl` installed, typically a control plane node.
+
+1. Set the path to your `kubeconfig` file.
+
+    ```bash
+    export KUBECONFIG=/etc/kubernetes/admin.conf
+    ```
+
+2. Run the `support-bundle-infra.sh` script.
+
+    ```bash
+    curl -sSL https://software.spectrocloud.com/scripts/support-bundle-infra.sh | bash
+    ```
+    If the script runs successfully, it creates a file in your home directory. The file name follows the pattern `<cluster name>-<YYYY-MM-DD>_<HH_MM_SS>.tar.gz`. If the script is unable to determine the cluster name, it defaults to `spectro-cluster`. One of the messages the terminal displays contains the name of the created file.
+
+    ```bash
+    Logs are archived in spectro-cluster-2025-05-13_16_50_50.tar.gz
+    ``` 
+
+3. Copy the file to your local computer. The command below serves as an example of how to copy the file `spectro-cluster-2025-05-13_16_50_50.tar.gz` from the `kairos@10.10.150.150` host to your `Downloads` folder. Run the command on the machine to which you want to copy the file.
+
+    ```bash
+    scp kairos@10.10.150.150:~/spectro-cluster-2025-05-13_16_50_50.tar.gz ~/Downloads/
+    ```
+
+### Run the Script to Collect Edge Host Logs
+The `support-bundle-edge.sh` script collects host-level diagnostics from an Edge node and, if available, includes Kubernetes data accessible locally on that host.
+Follow the steps below on every Edge host you want to troubleshoot.
+
+1. (Optional) Set the path to your `kubeconfig` file.
+
+    ```bash
+    export KUBECONFIG=/etc/kubernetes/admin.conf
+    ```
+
+    If you do not perform this step, the script defaults to using `/run/kubeconfig` if it exists.
+
+2. Run the `support-bundle-edge.sh` script as a user with sudo privileges.
+
+    ```bash
+    curl -sSL https://software.spectrocloud.com/scripts/support-bundle-edge.sh | sudo bash
+    ```
+    The table below contains the optional flags you can use when running the script.
+
+    | **Full Flag Name**          | **Short Flag Name** | **Description** | **Example** |
+    | --------------------------- | ------------------- |  -------------- | ------------|
+    | `--start-days-ago`          | `-s`                | Number of days before now to begin collecting journald logs from. | `-s 7`| 
+    | `--end-days-ago`            | `-e`                | Number of days before now to stop collecting journald logs. The value must be smaller than `-s`. | `-e 5`| 
+    | `--start-date`              | `-S`                | Start date for journald log collection. | `-S 2024-01-01`| 
+    | `--end-date`                | `-E`                | End date for journald log collection. Must be later than `-S`. | `-E 2024-01-06`|
+    | `--namespaces`              | `-n`                | Additional namespaces to collect logs from. | `-n hello-universe,hello-world`|
+    | `--resources-namespaced`    | `-r`                | Additional namespace-scoped resources to collect. | `-r certificates.cert-manager.io` |
+    | `--resources-cluster-scoped`| `-R`                | Additional cluster-scoped resources to collect. | `-R clusterissuers.cert-manager.io` |
+    | `--journald-services`       | `-j`                | Additional journald services to include in logs. | `-j cloud-init,systemd-resolved`| 
+
+
+    If the script runs successfully, it creates a file in the `/opt/spectrocloud/logs` directory. The file name follows the pattern `<hostname>-<YYYY-MM-DD>_<HH_MM_SS>.tar.gz`. One of the messages the terminal displays contains the created file's name and its path.
+
+    ```bash
+    Logs are archived in /opt/spectrocloud/logs/edge-e965384209c2d45078a29480e90bd275-2025-05-13_16_58_20.tar.gz
+    ``` 
+
+    :::info
+
+    The script collects only Helm release secrets from Spectro Cloud namespaces and excludes other Kubernetes secrets to protect sensitive data.
+
+    :::
+
+3. Copy the file to your local computer. The command below serves as an example of how to copy the file `edge-e965384209c2d45078a29480e90bd275-2025-05-13_16_58_20.tar.gz` from the `kairos@10.10.150.150` host to your `Downloads` folder. Run the command on the machine to which you want to copy the file.
+
+    ```bash
+    scp kairos@10.10.150.150:/opt/spectrocloud/logs/edge-e965384209c2d45078a29480e90bd275-2025-05-13_16_58_20.tar.gz ~/Downloads/
+    ```
+
+## Validate
+
+Review the files you copied to the `Downloads` folder. The scripts archive the collected logs into compressed tarballs TAR.GAR.
+
+Extract the file named in the format `<cluster name>-<YYYY-MM-DD>_<HH_MM_SS>.tar.gz` and verify it contains the `k8s` folder with the following subfolders:
path: docs/docs-content/troubleshooting/edge/collect-support-bundles.md
user: login: svetlana-efimova
body: Yes I did
created_at: 2025-05-13T18:46:17Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,149 @@
+---
+sidebar_label: "Collect Support Bundles"
+title: "Collect Support Bundles for Edge Cluster Troubleshooting"
+description: "Learn how to deploy a Private Cloud Gateway (PCG) to an existing Kubernetes cluster."
+hide_table_of_contents: false
+sidebar_position: 1
+toc_min_heading_level: 2
+toc_max_heading_level: 3
+tags: ["edge", "troubleshooting", "support"]
+---
+
+When deploying or operating Edge clusters, you may encounter issues that require assistance from the Spectro Cloud
+support team, such as Edge hosts failing to register, pod failures, or provisioning errors. To help our team
+troubleshoot these issues more effectively, follow this guide to collect support bundles and attach them to your support
+ticket.
+
+## Limitations
+
+- This guide applies only to connected installation mode, not airgap environments, since it requires internet access to
path: docs/docs-content/troubleshooting/edge/collect-support-bundles.md
user: login: lennessyy
body: Remember that we no longer use "connected vs airgap", we now use "centrally vs locally managed". Though maybe you are using this language only because this one is getting backported. 

Also, I would remove the limitation and put this as a prerequisite that the cluster has a connection to the internet. Even if your cluster is locally managed, I don't think there is a reason that this script wouldn't work as long as it has an internet connection. 
created_at: 2025-05-13T20:31:21Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,149 @@
+---
+sidebar_label: "Collect Support Bundles"
+title: "Collect Support Bundles for Edge Cluster Troubleshooting"
+description: "Learn how to deploy a Private Cloud Gateway (PCG) to an existing Kubernetes cluster."
+hide_table_of_contents: false
+sidebar_position: 1
+toc_min_heading_level: 2
+toc_max_heading_level: 3
+tags: ["edge", "troubleshooting", "support"]
+---
+
+When deploying or operating Edge clusters, you may encounter issues that require assistance from the Spectro Cloud
+support team, such as Edge hosts failing to register, pod failures, or provisioning errors. To help our team
+troubleshoot these issues more effectively, follow this guide to collect support bundles and attach them to your support
+ticket.
+
+## Limitations
+
+- This guide applies only to connected installation mode, not airgap environments, since it requires internet access to
+  run the troubleshooting script.
+
+## Prerequisites
+
+- You have connected to the host you need to troubleshoot, using SSH, direct terminal access, or another connection
+  method.
+- The following tools are available on the host:
+  - `journalctl`
+  - `systemctl`
+  - (Optional) `kubectl` (required for the full output of `support-bundle-infra.sh`)
+- (Optional) A valid `kubeconfig` file is configured (required for the full output of `support-bundle-infra.sh`)
path: docs/docs-content/troubleshooting/edge/collect-support-bundles.md
user: login: lennessyy
body: I would put this together with the kubectl bullet. 
created_at: 2025-05-13T20:34:32Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,149 @@
+---
+sidebar_label: "Collect Support Bundles"
+title: "Collect Support Bundles for Edge Cluster Troubleshooting"
+description: "Learn how to deploy a Private Cloud Gateway (PCG) to an existing Kubernetes cluster."
+hide_table_of_contents: false
+sidebar_position: 1
+toc_min_heading_level: 2
+toc_max_heading_level: 3
+tags: ["edge", "troubleshooting", "support"]
+---
+
+When deploying or operating Edge clusters, you may encounter issues that require assistance from the Spectro Cloud
+support team, such as Edge hosts failing to register, pod failures, or provisioning errors. To help our team
+troubleshoot these issues more effectively, follow this guide to collect support bundles and attach them to your support
+ticket.
+
+## Limitations
+
+- This guide applies only to connected installation mode, not airgap environments, since it requires internet access to
+  run the troubleshooting script.
+
+## Prerequisites
+
+- You have connected to the host you need to troubleshoot, using SSH, direct terminal access, or another connection
+  method.
+- The following tools are available on the host:
+  - `journalctl`
+  - `systemctl`
+  - (Optional) `kubectl` (required for the full output of `support-bundle-infra.sh`)
+- (Optional) A valid `kubeconfig` file is configured (required for the full output of `support-bundle-infra.sh`)
+
+## Run the Troubleshooting Scripts
+
+### Run the Script to Collect Cluster Logs
+
+The `support-bundle-infra.sh` script collects cluster-level diagnostics. Follow the steps below on a host with a valid
+`kubeconfig` and `kubectl` installed, typically a control plane node.
+
+1. Set the path to your `kubeconfig` file.
+
+   ```bash
+   export KUBECONFIG=/etc/kubernetes/admin.conf
+   ```
+
+2. Run the `support-bundle-infra.sh` script.
+
+   ```bash
+   curl --silent --show-error --location https://software.spectrocloud.com/scripts/support-bundle-infra.sh | bash
+   ```
+
+   If the script runs successfully, it creates a file in your home directory. The file name follows the pattern
+   `<cluster name>-<YYYY-MM-DD>_<HH_MM_SS>.tar.gz`. If the script is unable to determine the cluster name, it defaults
+   to `spectro-cluster`. One of the messages the terminal displays contains the name of the created file.
+
+   ```bash
+   Logs are archived in spectro-cluster-2025-05-13_16_50_50.tar.gz
+   ```
+
+3. Copy the file to your local computer. The command below serves as an example of how to copy the file
+   `spectro-cluster-2025-05-13_16_50_50.tar.gz` from the `kairos@10.10.150.150` host to your `Downloads` folder. Run the
+   command on the machine to which you want to copy the file.
+
+   ```bash
+   scp kairos@10.10.150.150:~/spectro-cluster-2025-05-13_16_50_50.tar.gz ~/Downloads/
+   ```
+
+### Run the Script to Collect Edge Host Logs
+
+The `support-bundle-edge.sh` script collects host-level diagnostics from an Edge node and, if available, includes
+Kubernetes data accessible locally on that host. Follow the steps below on every Edge host you want to troubleshoot.
+
+1. (Optional) Set the path to your `kubeconfig` file.
+
+   ```bash
+   export KUBECONFIG=/etc/kubernetes/admin.conf
+   ```
+
+   If you do not perform this step, the script defaults to using `/run/kubeconfig` if it exists.
+
+2. Run the `support-bundle-edge.sh` script as a user with sudo privileges.
path: docs/docs-content/troubleshooting/edge/collect-support-bundles.md
user: login: lennessyy
body: ```suggestion
2. Run the `support-bundle-edge.sh` script as a user with root privileges.
```
It's better to use English words whenever possible. You can use root or superuser (sudo is superuser do)
created_at: 2025-05-13T20:38:03Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,149 @@
+---
+sidebar_label: "Collect Support Bundles"
+title: "Collect Support Bundles for Edge Cluster Troubleshooting"
+description: "Learn how to deploy a Private Cloud Gateway (PCG) to an existing Kubernetes cluster."
+hide_table_of_contents: false
+sidebar_position: 1
+toc_min_heading_level: 2
+toc_max_heading_level: 3
+tags: ["edge", "troubleshooting", "support"]
+---
+
+When deploying or operating Edge clusters, you may encounter issues that require assistance from the Spectro Cloud
+support team, such as Edge hosts failing to register, pod failures, or provisioning errors. To help our team
+troubleshoot these issues more effectively, follow this guide to collect support bundles and attach them to your support
+ticket.
+
+## Limitations
+
+- This guide applies only to connected installation mode, not airgap environments, since it requires internet access to
+  run the troubleshooting script.
+
+## Prerequisites
+
+- You have connected to the host you need to troubleshoot, using SSH, direct terminal access, or another connection
+  method.
+- The following tools are available on the host:
+  - `journalctl`
+  - `systemctl`
+  - (Optional) `kubectl` (required for the full output of `support-bundle-infra.sh`)
+- (Optional) A valid `kubeconfig` file is configured (required for the full output of `support-bundle-infra.sh`)
+
+## Run the Troubleshooting Scripts
+
+### Run the Script to Collect Cluster Logs
+
+The `support-bundle-infra.sh` script collects cluster-level diagnostics. Follow the steps below on a host with a valid
+`kubeconfig` and `kubectl` installed, typically a control plane node.
+
+1. Set the path to your `kubeconfig` file.
+
+   ```bash
+   export KUBECONFIG=/etc/kubernetes/admin.conf
+   ```
+
+2. Run the `support-bundle-infra.sh` script.
+
+   ```bash
+   curl --silent --show-error --location https://software.spectrocloud.com/scripts/support-bundle-infra.sh | bash
+   ```
+
+   If the script runs successfully, it creates a file in your home directory. The file name follows the pattern
+   `<cluster name>-<YYYY-MM-DD>_<HH_MM_SS>.tar.gz`. If the script is unable to determine the cluster name, it defaults
+   to `spectro-cluster`. One of the messages the terminal displays contains the name of the created file.
+
+   ```bash
+   Logs are archived in spectro-cluster-2025-05-13_16_50_50.tar.gz
+   ```
+
+3. Copy the file to your local computer. The command below serves as an example of how to copy the file
+   `spectro-cluster-2025-05-13_16_50_50.tar.gz` from the `kairos@10.10.150.150` host to your `Downloads` folder. Run the
+   command on the machine to which you want to copy the file.
+
+   ```bash
+   scp kairos@10.10.150.150:~/spectro-cluster-2025-05-13_16_50_50.tar.gz ~/Downloads/
+   ```
+
+### Run the Script to Collect Edge Host Logs
+
+The `support-bundle-edge.sh` script collects host-level diagnostics from an Edge node and, if available, includes
+Kubernetes data accessible locally on that host. Follow the steps below on every Edge host you want to troubleshoot.
+
+1. (Optional) Set the path to your `kubeconfig` file.
+
+   ```bash
+   export KUBECONFIG=/etc/kubernetes/admin.conf
+   ```
+
+   If you do not perform this step, the script defaults to using `/run/kubeconfig` if it exists.
+
+2. Run the `support-bundle-edge.sh` script as a user with sudo privileges.
+
+   ```bash
+   curl --silent --show-error --location https://software.spectrocloud.com/scripts/support-bundle-edge.sh | sudo bash
+   ```
+
+   The table below contains the optional flags you can use when running the script.
+
+   | **Full Flag Name**           | **Short Flag Name** | **Description**                                                                                  | **Example**                         |
+   | ---------------------------- | ------------------- | ------------------------------------------------------------------------------------------------ | ----------------------------------- |
+   | `--start-days-ago`           | `-s`                | Number of days before now to begin collecting journald logs from.                                | `-s 7`                              |
path: docs/docs-content/troubleshooting/edge/collect-support-bundles.md
user: login: lennessyy
body: ```suggestion
   | `--start-days-ago`           | `-s`                | Number of days in the past to start collecting journald logs.                                | `-s 7`                              |
```
maybe?
created_at: 2025-05-13T20:40:11Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,149 @@
+---
+sidebar_label: "Collect Support Bundles"
+title: "Collect Support Bundles for Edge Cluster Troubleshooting"
+description: "Learn how to deploy a Private Cloud Gateway (PCG) to an existing Kubernetes cluster."
+hide_table_of_contents: false
+sidebar_position: 1
+toc_min_heading_level: 2
+toc_max_heading_level: 3
+tags: ["edge", "troubleshooting", "support"]
+---
+
+When deploying or operating Edge clusters, you may encounter issues that require assistance from the Spectro Cloud
+support team, such as Edge hosts failing to register, pod failures, or provisioning errors. To help our team
+troubleshoot these issues more effectively, follow this guide to collect support bundles and attach them to your support
+ticket.
+
+## Limitations
+
+- This guide applies only to connected installation mode, not airgap environments, since it requires internet access to
+  run the troubleshooting script.
+
+## Prerequisites
+
+- You have connected to the host you need to troubleshoot, using SSH, direct terminal access, or another connection
+  method.
+- The following tools are available on the host:
+  - `journalctl`
+  - `systemctl`
+  - (Optional) `kubectl` (required for the full output of `support-bundle-infra.sh`)
+- (Optional) A valid `kubeconfig` file is configured (required for the full output of `support-bundle-infra.sh`)
+
+## Run the Troubleshooting Scripts
+
+### Run the Script to Collect Cluster Logs
+
+The `support-bundle-infra.sh` script collects cluster-level diagnostics. Follow the steps below on a host with a valid
+`kubeconfig` and `kubectl` installed, typically a control plane node.
+
+1. Set the path to your `kubeconfig` file.
+
+   ```bash
+   export KUBECONFIG=/etc/kubernetes/admin.conf
+   ```
+
+2. Run the `support-bundle-infra.sh` script.
+
+   ```bash
+   curl --silent --show-error --location https://software.spectrocloud.com/scripts/support-bundle-infra.sh | bash
+   ```
+
+   If the script runs successfully, it creates a file in your home directory. The file name follows the pattern
+   `<cluster name>-<YYYY-MM-DD>_<HH_MM_SS>.tar.gz`. If the script is unable to determine the cluster name, it defaults
+   to `spectro-cluster`. One of the messages the terminal displays contains the name of the created file.
+
+   ```bash
+   Logs are archived in spectro-cluster-2025-05-13_16_50_50.tar.gz
+   ```
+
+3. Copy the file to your local computer. The command below serves as an example of how to copy the file
+   `spectro-cluster-2025-05-13_16_50_50.tar.gz` from the `kairos@10.10.150.150` host to your `Downloads` folder. Run the
+   command on the machine to which you want to copy the file.
+
+   ```bash
+   scp kairos@10.10.150.150:~/spectro-cluster-2025-05-13_16_50_50.tar.gz ~/Downloads/
+   ```
+
+### Run the Script to Collect Edge Host Logs
+
+The `support-bundle-edge.sh` script collects host-level diagnostics from an Edge node and, if available, includes
+Kubernetes data accessible locally on that host. Follow the steps below on every Edge host you want to troubleshoot.
+
+1. (Optional) Set the path to your `kubeconfig` file.
+
+   ```bash
+   export KUBECONFIG=/etc/kubernetes/admin.conf
+   ```
+
+   If you do not perform this step, the script defaults to using `/run/kubeconfig` if it exists.
+
+2. Run the `support-bundle-edge.sh` script as a user with root privileges.
path: docs/docs-content/troubleshooting/edge/collect-support-bundles.md
user: login: github-actions[bot]
body: 🚫 **[vale]** <sub>reported by [reviewdog](https://github.com/reviewdog/reviewdog) :dog:</sub><br>[spectrocloud-docs-internal.ableism] Avoid using ableism terms. Use 'issue' instead of 'Run'.
created_at: 2025-05-13T20:48:11Z
author_association: CONTRIBUTOR

PR comments:
user: login: netlify[bot]
created_at: 2025-05-13T17:52:22Z
body: ### <span aria-hidden="true">✅</span> Deploy Preview for *docs-spectrocloud* ready!


|  Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 16db94c2445a12575543488e08e4733950b3b334 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/sites/docs-spectrocloud/deploys/6823bd827d8d21000856e809 |
|<span aria-hidden="true">😎</span> Deploy Preview | [https://deploy-preview-6781--docs-spectrocloud.netlify.app](https://deploy-preview-6781--docs-spectrocloud.netlify.app) |
|<span aria-hidden="true">📱</span> Preview on mobile | <details><summary> Toggle QR Code... </summary><br /><br />![QR Code](https://app.netlify.com/qr-code/eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJ1cmwiOiJodHRwczovL2RlcGxveS1wcmV2aWV3LTY3ODEtLWRvY3Mtc3BlY3Ryb2Nsb3VkLm5ldGxpZnkuYXBwIn0.lkKhaHX1mru43wURG6kPp66Cw7bv_p-zXfDmdjdXCCs)<br /><br />_Use your smartphone camera to open QR code link._</details> |
---
<!-- [docs-spectrocloud Preview](https://deploy-preview-6781--docs-spectrocloud.netlify.app) -->
_To edit notification comments on pull requests, go to your [Netlify site configuration](https://app.netlify.com/sites/docs-spectrocloud/configuration/notifications#deploy-webhooks)._
author_association: NONE
user: login: vault-token-factory-spectrocloud[bot]
created_at: 2025-05-13T22:12:41Z
body: ## 💔 Some backports could not be created

| Status | Branch | Result |
|:------:|:------:|:------|
|❌|version-4-2|**Backport failed because of merge conflicts**<br><br>You might need to backport the following PRs to version-4-2:<br> - [docs: DOC-1500: "Too many open files" Troubleshooting (#4967)](https://github.com/spectrocloud/librarium/pull/4967)<br> - [docs: add ubuntu to known issue (#4120)](https://github.com/spectrocloud/librarium/pull/4120)|
|❌|version-4-3|**Backport failed because of merge conflicts**<br><br>You might need to backport the following PRs to version-4-3:<br> - [docs: DOC-1500: "Too many open files" Troubleshooting (#4967)](https://github.com/spectrocloud/librarium/pull/4967)<br> - [docs: add known issue Pe 5556 (#4717)](https://github.com/spectrocloud/librarium/pull/4717)<br> - [docs: change earthly command to installed earthly (#4323)](https://github.com/spectrocloud/librarium/pull/4323)|
|❌|version-4-4|**Backport failed because of merge conflicts**<br><br>You might need to backport the following PRs to version-4-4:<br> - [docs: DOC-1500: "Too many open files" Troubleshooting (#4967)](https://github.com/spectrocloud/librarium/pull/4967)<br> - [docs: add known issue Pe 5556 (#4717)](https://github.com/spectrocloud/librarium/pull/4717)<br> - [fix: Release 4.4.c (#3723)](https://github.com/spectrocloud/librarium/pull/3723)|
|❌|version-4-5|Backport failed because of merge conflicts|
|✅|version-4-6|[<img src="https://img.shields.io/github/pulls/detail/state/spectrocloud/librarium/6797">](https://github.com/spectrocloud/librarium/pull/6797)|

Note: Successful backport PRs will be merged automatically after passing CI.

### Manual backport
To create the backport manually run:
```
backport --pr 6781
```

### Questions ?
Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) and see the [Github Action logs](https://github.com/spectrocloud/librarium/actions/runs/15007550249) for details

<!--- Backport version: 9.5.1 -->
author_association: CONTRIBUTOR
user: login: vault-token-factory-spectrocloud[bot]
created_at: 2025-05-20T21:02:59Z
body: :tada: This PR is included in version 4.7.4 :tada:

The release is available on [GitHub release](https://github.com/spectrocloud/librarium/releases/tag/v4.7.4)

Your **[semantic-release](https://github.com/semantic-release/semantic-release)** bot :package::rocket:
author_association: CONTRIBUTOR