Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tunnel Connectivity Documentation Updates #1820

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Tunnel Connectivity Documentation Updates #1820

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8d8afe3
Tunnel Connectivity Documentation Updates
Mar 20, 2025
d1a1e8b
Add metadata and improve formatting in documentation
kthakar1990 Mar 20, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions support/azure/azure-kubernetes/connectivity/tunnel-connectivity-issues.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -251,6 +251,15 @@ If everything is OK within the application, you'll have to adjust the allocated

You can set up a new cluster to use a Managed Network Address Translation (NAT) Gateway for outbound connections. For more information, see [Create an AKS cluster with a Managed NAT Gateway](/azure/aks/nat-gateway#create-an-aks-cluster-with-a-managed-nat-gateway).

## Cause 6: Konnectivity Agents performance challenges with Cluster Growth

> [!NOTE]
> This cause applies to only the `Konnectivity-agent` pods.

### Solution 6: Cluster Proportional Autoscaler (CPA) for Konnectivity Agent

To address scalability challenges in large clusters, we have implemented the Cluster Proportional Autoscaler (CPA) for our Konnectivity Agents. This approach aligns with industry standards and best practices, ensuring optimal resource usage and enhanced performance. Previously, the Konnectivity agent had a fixed replica count, which created a bottleneck as the cluster grew. With this change, the replica count will now dynamically adjust based on node-scaling rules, providing best-in-class performance.

[!INCLUDE [Third-party contact disclaimer](../../../includes/third-party-contact-disclaimer.md)]

[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]