Skip to content

Commit f3bab31

Browse files
Merge branch 'MicrosoftDocs:main' into patch-6
2 parents f214577 + e66ca20 commit f3bab31

File tree

185 files changed

+9459
-1953
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

185 files changed

+9459
-1953
lines changed

CODEOWNERS

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,5 +35,5 @@
3535
/articles/copilot @jasonwhowell @thomps23
3636
/articles/lighthouse @jasonwhowell @thomps23
3737
/articles/quotas @jasonwhowell @thomps23
38+
/articles/container-registry @jasonwhowell @thomps23
3839
/articles/kubernetes-fleet @jasonwhowell @thomps23
39-

articles/api-management/authentication-basic-policy.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,8 @@ ms.author: danlep
1616

1717
Use the `authentication-basic` policy to authenticate with a backend service using Basic authentication. This policy effectively sets the HTTP Authorization header to the value corresponding to the credentials provided in the policy.
1818

19+
[!INCLUDE [api-management-credentials-caution](../../includes/api-management-credentials-caution.md)]
20+
1921
[!INCLUDE [api-management-policy-generic-alert](../../includes/api-management-policy-generic-alert.md)]
2022

2123

articles/api-management/authentication-certificate-policy.md

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,9 @@ ms.author: danlep
1414

1515
[!INCLUDE [api-management-availability-all-tiers](../../includes/api-management-availability-all-tiers.md)]
1616

17-
Use the `authentication-certificate` policy to authenticate with a backend service using a client certificate. When the certificate is [installed into API Management](./api-management-howto-mutual-certificates.md) first, identify it first by its thumbprint or certificate ID (resource name).
17+
Use the `authentication-certificate` policy to authenticate with a backend service using a client certificate. When the certificate is [installed into API Management](./api-management-howto-mutual-certificates.md) first, identify it first by its thumbprint or certificate ID (resourcename).
18+
19+
[!INCLUDE [api-management-credentials-caution](../../includes/api-management-credentials-caution.md)]
1820

1921
> [!CAUTION]
2022
> If the certificate references a certificate stored in Azure Key Vault, identify it using the certificate ID. When a key vault certificate is rotated, its thumbprint in API Management will change, and the policy will not resolve the new certificate if it is identified by thumbprint.
@@ -43,6 +45,12 @@ ms.author: danlep
4345
- [**Policy scopes:**](./api-management-howto-policies.md#scopes) global, workspace, product, API, operation
4446
- [**Gateways:**](api-management-gateways-overview.md) classic, v2, consumption, self-hosted, workspace
4547

48+
### Usage notes
49+
50+
- We recommend configuring [key vault certificates](api-management-howto-mutual-certificates.md) to manage certificates used to secure access to backend services.
51+
- If you configure a certificate password in this policy, we recommend using a [named value](api-management-howto-properties.md).
52+
53+
4654
## Examples
4755

4856
### Client certificate identified by the certificate ID

articles/api-management/proxy-policy.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,8 @@ ms.author: danlep
1616

1717
The `proxy` policy allows you to route requests forwarded to backends via an HTTP proxy. Only HTTP (not HTTPS) is supported between the gateway and the proxy. Basic and NTLM authentication only.
1818

19+
[!INCLUDE [api-management-credentials-caution](../../includes/api-management-credentials-caution.md)]
20+
1921
[!INCLUDE [api-management-policy-generic-alert](../../includes/api-management-policy-generic-alert.md)]
2022

2123

@@ -39,6 +41,11 @@ The `proxy` policy allows you to route requests forwarded to backends via an HTT
3941
- [**Policy scopes:**](./api-management-howto-policies.md#scopes) global, workspace, product, API, operation
4042
- [**Gateways:**](api-management-gateways-overview.md) classic, v2, consumption, self-hosted, workspace
4143

44+
### Usage notes
45+
46+
- We recommend using [named values](api-management-howto-properties.md) to provide credentials, with secrets protected in a key vault.
47+
48+
4249
## Example
4350

4451
In this example, [named values](api-management-howto-properties.md) are used for the username and password to avoid storing sensitive information in the policy document.

articles/api-management/virtual-network-workspaces-resources.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -31,6 +31,11 @@ For information about networking options in API Management, see [Use a virtual n
3131

3232
* The subnet can't be shared with another Azure resource, including another workspace gateway.
3333

34+
## Subnet size
35+
36+
* Minimum: /27 (32 addresses)
37+
* Maximum: /24 (256 addresses) - recommended
38+
3439
## Subnet delegation
3540

3641
The subnet must be delegated as follows to enable the desired inbound and outbound access.

articles/application-gateway/for-containers/alb-controller-release-notes.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,12 +27,13 @@ Instructions for new or existing deployments of ALB Controller are found in the
2727

2828
| ALB Controller Version | Gateway API Version | Kubernetes Version | Release Notes |
2929
| ---------------------- | ------------------- | ------------------ | ------------- |
30-
| 1.0.2| v1 | v1.26, v1.27, v1.28, v1.29 | ECDSA + RSA certificate support for both Ingress and Gateway API, Ingress fixes, Server-sent events support |
30+
| 1.2.3| v1.1 | v1.26, v1.27, v1.28, v1.29, v1.30 | Gateway API v1.1, gRPC support, frontend mutual authentication, readiness probe fixes, custom health probe port and TLS mode |
3131

3232
## Release history
3333

3434
| ALB Controller Version | Gateway API Version | Kubernetes Version | Release Notes |
3535
| ---------------------- | ------------------- | ------------------ | ------------- |
36+
| 1.0.2| v1 | v1.26, v1.27, v1.28, v1.29 | ECDSA + RSA certificate support for both Ingress and Gateway API, Ingress fixes, Server-sent events support |
3637
| 1.0.0| v1 | v1.26, v1.27, v1.28 | General Availability! URL redirect for both Gateway and Ingress API, v1beta1 -> v1 of Gateway API, quality improvements<br/>Breaking Changes: TLS Policy for Gateway API [PolicyTargetReference](https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io%2fv1alpha2.PolicyTargetReferenceWithSectionName)<br/>Listener is now referred to as [SectionName](https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.SectionName)<br/>Fixes: Request timeout of 3 seconds, [HealthCheckPolicy interval](https://github.com/Azure/AKS/issues/4086), [pod crash for missing API fields](https://github.com/Azure/AKS/issues/4087) |
3738
| 0.6.3 | v1beta1 | v1.25 | Hotfix to address handling of Application Gateway for Containers frontends during controller restart in managed scenario |
3839
| 0.6.2 | - | - | Skipped release |

0 commit comments

Comments
 (0)