Skip to content

Commit 4cfed30

Browse files
committed
freshness
1 parent 02fac48 commit 4cfed30

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/machine-learning/how-to-secure-kubernetes-inferencing-environment.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,15 +7,15 @@ ms.author: larryfr
77
ms.reviewer: bozhlin
88
ms.service: azure-machine-learning
99
ms.subservice: core
10-
ms.date: 08/31/2022
10+
ms.date: 02/06/2025
1111
ms.topic: how-to
1212
ms.custom: build-spring-2022, cliv2, sdkv2
1313
# Customer intent: I would like to have machine learning with all private IP only
1414
---
1515

1616
# Secure Azure Kubernetes Service inferencing environment
1717

18-
If you have an Azure Kubernetes (AKS) cluster behind of VNet, you would need to secure Azure Machine Learning workspace resources and a compute environment using the same or peered VNet. In this article, you'll learn:
18+
If you have an Azure Kubernetes (AKS) cluster behind of VNet, you would need to secure Azure Machine Learning workspace resources and a compute environment using the same or peered VNet. In this article, you learn:
1919
* What is a secure AKS inferencing environment
2020
* How to configure a secure AKS inferencing environment
2121

@@ -53,7 +53,7 @@ After you have VNet information for AKS cluster and if you already have workspac
5353
* If you have other storage that is used by your Azure Machine Learning workloads, add a new private endpoint for that storage. The private endpoint should be in the same or peered VNet as AKS cluster and have private DNS zone integration enabled.
5454
* Add a new private endpoint to your workspace. This private endpoint should be in the same or peered VNet as your AKS cluster and have private DNS zone integration enabled.
5555

56-
If you have AKS cluster ready but don't have workspace created yet, you can use AKS cluster VNet when creating the workspace. Use the AKS cluster VNet information when following the [create secure workspace](./tutorial-create-secure-workspace.md) tutorial. Once the workspace has been created, add a new private endpoint to your workspace as the last step. For all the above steps, it's important to ensure that all private endpoints should exist in the same AKS cluster VNet and have private DNS zone integration enabled.
56+
If you have AKS cluster ready but don't have workspace created yet, you can use AKS cluster VNet when creating the workspace. Use the AKS cluster VNet information when following the [create secure workspace](./tutorial-create-secure-workspace.md) tutorial. Once the workspace is created, add a new private endpoint to your workspace as the last step. For all the above steps, it's important to ensure that all private endpoints should exist in the same AKS cluster VNet and have private DNS zone integration enabled.
5757

5858
Special notes for configuring a secure AKS inferencing environment:
5959
* Use system-assigned managed identity when creating workspace, as storage account with private endpoint only allows access with system-assigned managed identity.

0 commit comments

Comments
 (0)