From 4e584e5ea0289909558a81eb43b5bf28964591f3 Mon Sep 17 00:00:00 2001
From: PDTeamX <8293321+ehsandeep@users.noreply.github.com>
Date: Mon, 4 Aug 2025 15:32:21 -0700
Subject: [PATCH] Clarify Kubernetes integration requires public/external
 access

- Add warning that Kubernetes integration only works with publicly accessible clusters
- Clarify that internal-only clusters will fail to integrate
- Add troubleshooting section for common integration failures
- Provide alternative solutions for internal clusters (cloud provider integrations)
- Fix formatting issue with Verify button text
- Add detailed accessibility requirements and examples
---
 cloud/integrations.mdx | 27 ++++++++++++++++++++++++++-
 1 file changed, 26 insertions(+), 1 deletion(-)

diff --git a/cloud/integrations.mdx b/cloud/integrations.mdx
index ab6ad23..8c1ddaf 100644
--- a/cloud/integrations.mdx
+++ b/cloud/integrations.mdx
@@ -630,8 +630,20 @@ Supported Kubernetes Services:
 - Ingresses
 - Cross-cloud cluster discovery
 
+<Warning>
+  **Public/External Access Required**: Kubernetes integration only works with clusters that are publicly accessible or have external endpoints. Internal-only clusters (accessible only within private networks) will fail to integrate as ProjectDiscovery cannot reach them from the cloud platform.
+</Warning>
+
 **Kubernetes Integration Method**
 
+<Note>
+  **Cluster Accessibility**: Before attempting integration, ensure your Kubernetes cluster has public/external endpoints that ProjectDiscovery can access. This includes:
+  - Publicly accessible API servers
+  - External load balancers exposing services
+  - Internet-facing ingress controllers
+  - Clusters with public IP addresses
+</Note>
+
 1. **Prepare Base64-Encoded Kubeconfig**
    - Your kubeconfig file is typically located at:
 
@@ -660,7 +672,20 @@ Supported Kubernetes Services:
    - Use the relevant context name if required.
 3. **Define Integration Name & Verify**
 
-   Choose a unique, descriptive name for this integration and click \*\*Verify \*\*to complete the integration.
+   Choose a unique, descriptive name for this integration and click **Verify** to complete the integration.
+
+**Troubleshooting Integration Failures**
+
+If your Kubernetes integration fails, the most common cause is cluster accessibility:
+
+- **Internal Clusters**: Clusters only accessible within private networks (VPN, internal VPCs) cannot be reached by ProjectDiscovery
+- **Firewall Restrictions**: Ensure your cluster's API server and services are accessible from the internet
+- **Network Policies**: Check that network policies allow external access to required endpoints
+- **Load Balancer Configuration**: Verify that external load balancers are properly configured and accessible
+
+<Info>
+  **Alternative for Internal Clusters**: For internal-only Kubernetes clusters, consider using the cloud provider integration (AWS EKS, GCP GKE, Azure AKS) which can discover cluster endpoints through the cloud provider's APIs, or manually add the cluster's external endpoints as assets.
+</Info>
 
 References