Skip to content

Commit 370412e

Browse files
committed
[SCOPED] Fix links
1 parent 8e5cb0b commit 370412e

File tree

4 files changed

+5
-5
lines changed

4 files changed

+5
-5
lines changed

support/azure/azure-kubernetes/availability-performance/identify-memory-saturation-aks.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ This article discusses methods for troubleshooting memory saturation issues. Mem
1414
## Prerequisites
1515

1616
- The Kubernetes [kubectl](https://kubernetes.io/docs/reference/kubectl/overview/) command-line tool. To install kubectl by using [Azure CLI](/cli/azure/install-azure-cli), run the [az aks install-cli](/cli/azure/aks#az-aks-install-cli) command.
17-
- The open source project [Inspektor Gadget](/troubleshoot/azure/azure-kubernetes/logs/capture-system-insights-from-aks#what-is-inspektor-gadget) for advanced process level memory analysis. For more information, see [How to install Inspektor Gadget in an AKS cluster](/troubleshoot/azure/azure-kubernetes/logs/capture-system-insights-from-aks#how-to-install-inspektor-gadget-in-an-aks-cluster).
17+
- The open source project [Inspektor Gadget](../logs/capture-system-insights-from-aks.md#what-is-inspektor-gadget) for advanced process level memory analysis. For more information, see [How to install Inspektor Gadget in an AKS cluster](../logs/capture-system-insights-from-aks.md#how-to-install-inspektor-gadget-in-an-aks-cluster).
1818

1919
## Symptoms
2020

@@ -165,7 +165,7 @@ Now that you've identified the pods that are using high memory, you can identify
165165

166166
For advanced process level memory analysis, use [Inspektor Gadget](https://go.microsoft.com/fwlink/?linkid=2260072) to monitor real time memory usage at the process level within pods:
167167

168-
1. Install Inspektor Gadget using the instructions found in the [documentation](/troubleshoot/azure/azure-kubernetes/logs/capture-system-insights-from-aks#how-to-install-inspektor-gadget-in-an-aks-cluster)
168+
1. Install Inspektor Gadget using the instructions found in the [documentation](../logs/capture-system-insights-from-aks.md#how-to-install-inspektor-gadget-in-an-aks-cluster)
169169

170170
2. Run the [top_process gadget](https://aka.ms/igtopprocess) to identify processes that are using large amounts of memory. You can use `--fields` to select certain columns and `--filter` to filter events based on specific field values, for example the pod names of previously identified pods with high memory consumption. You can also:
171171

support/azure/azure-kubernetes/load-bal-ingress-c/troubleshoot-app-gateway-ingress-controller-connectivity-issues.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ Before you start, make sure that you have the following tools installed:
2323
## Common symptoms
2424

2525
> [!NOTE]
26-
> This article focuses on Application Gateway Ingress Controller issues. Other underlying problems might cause similar symptoms. For more information, see [Troubleshoot connection issues to an app hosted in an AKS cluster](/troubleshoot/azure/azure-kubernetes/connectivity/connection-issues-application-hosted-aks-cluster).
26+
> This article focuses on Application Gateway Ingress Controller issues. Other underlying problems might cause similar symptoms. For more information, see [Troubleshoot connection issues to an app hosted in an AKS cluster](../connectivity/connection-issues-application-hosted-aks-cluster.md).
2727
2828
| Symptom | Description |
2929
| --- | --- |

support/windows-server/windows-security/kerberos-authentication-troubleshooting-guidance.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -353,7 +353,7 @@ Kerberos supports three types of delegation:
353353
>
354354
> Constrained delegation and RBCD are different configurations, and they are mutually exclusive. When a front-end service requests a ticket to a back-end service, the KDC first checks the front-end service for constrained delegation. If constrained delegation is not configured for the front-end service, the KDC checks the back-end service for resource-based constrained delegation. Because of this sequence, constrained delegation takes precedence over resource-based delegation.
355355
>
356-
> - By default, Microsoft Edge does not support unconstrained delegation. If you're using unconstrained delegation, see [Kerberos unconstrained double-hop authentication with Microsoft Edge (Chromium)](/troubleshoot/developer/webapps/iis/www-authentication-authorization/kerberos-double-hop-authentication-edge-chromium) for more information about the configuration that you need.
356+
> - By default, Microsoft Edge does not support unconstrained delegation. If you're using unconstrained delegation, see [Kerberos unconstrained double-hop authentication with Microsoft Edge (Chromium)](../../developer/webapps/iis/www-authentication-authorization/kerberos-double-hop-authentication-edge-chromium.md) for more information about the configuration that you need.
357357
>
358358
> - Unconstrained delegation is not recommended because it doesn't restrict which services the authenticated account can interact with.
359359

support/windows-server/windows-security/troubleshoot-kerberos-sso-issues.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ Different kinds of clients use different criteria to identify intranet sites, an
5353

5454
- **Clients that aren't browser-based**. Review the documentation for the client application or contact the application's support provider. Make sure that the client is configured correctly to support SSO authentication.
5555

56-
- **Clients that are based on Internet Explorer (or similar older browser)**. Older browsers, including Internet Explorer (all versions) and Microsoft Edge versions older than version 87 use different default configurations than the newer browsers. For more information about how to troubleshoot Kerberos issues when using Internet Explorer, see [Troubleshoot Kerberos failures in Internet Explorer](/troubleshoot/developer/webapps/iis/www-authentication-authorization/troubleshoot-kerberos-failures-ie).
56+
- **Clients that are based on Internet Explorer (or similar older browser)**. Older browsers, including Internet Explorer (all versions) and Microsoft Edge versions older than version 87 use different default configurations than the newer browsers. For more information about how to troubleshoot Kerberos issues when using Internet Explorer, see [Troubleshoot Kerberos failures in Internet Explorer](../../developer/webapps/iis/www-authentication-authorization/troubleshoot-kerberos-failures-ie.md).
5757

5858
Unlike older browsers, Microsoft Edge, version 87 (and later versions) uses only two internet zones: **Internet** and **Local intranet**. Edge ignores other zone settings, such as **Restricted sites**. Additionally, Edge doesn't always use the client computer zone settings to identify intranet sites. Edge considers other factors, such as proxy configurations. For these reasons, Group Policy provides the most consistent method to manage Microsoft Edge configuration.
5959

0 commit comments

Comments
 (0)