You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/iot-operations/deploy-iot-ops/howto-deploy-iot-operations.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -169,9 +169,10 @@ One at a time, run each Azure CLI command on the **Automation** tab in a termina
169
169
170
170
> [!TIP]
171
171
> The `init` command only needs to be run once per cluster. If you're reusing a cluster that already had Azure IoT Operations version 0.8.0 deployed on it, you can skip this step.
172
-
172
+
<!--
173
173
> [!IMPORTANT]
174
174
> When you initialize your Azure IoT Operations instance on a VKS cluster with its [pod security admission controller running in restricted mode](https://techdocs.broadcom.com/us/en/vmware-cis/vcf/vsphere-supervisor-services-and-standalone-components/latest/managing-vsphere-kuberenetes-service-clusters-and-workloads/managing-security-for-tkg-service-clusters/configure-psa-for-tkr-1-25-and-later.html) you must include the `--cm-config global.telemetry.logs.enabled=false` flag when you run `az iot ops init`.
175
+
-->
175
176
176
177
This command might take several minutes to complete. You can watch the progress in the deployment progress display in the terminal.
Copy file name to clipboardExpand all lines: articles/iot-operations/deploy-iot-ops/howto-deploy-iot-test-operations.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -154,9 +154,10 @@ One at a time, run each Azure CLI command on the **Automation** tab in a termina
154
154
> The `init` command only needs to be run once per cluster. If you followed the optional prerequisite to set up your own certificate authority issuer, follow the steps in [Bring your own issuer](../secure-iot-ops/howto-manage-certificates.md#bring-your-own-issuer).
155
155
156
156
This command might take several minutes to complete. You can watch the progress in the deployment progress display in the terminal.
157
-
157
+
<!--
158
158
> [!IMPORTANT]
159
159
> When you initialize your Azure IoT Operations instance on a VKS cluster with its [pod security admission controller running in restricted mode](https://techdocs.broadcom.com/us/en/vmware-cis/vcf/vsphere-supervisor-services-and-standalone-components/latest/managing-vsphere-kuberenetes-service-clusters-and-workloads/managing-security-for-tkg-service-clusters/configure-psa-for-tkr-1-25-and-later.html) you must include the `--cm-config global.telemetry.logs.enabled=false` flag when you run `az iot ops init`.
160
+
-->
160
161
161
162
1. To deploy Azure IoT Operations, copy and run the provided [az iot ops create](/cli/azure/iot/ops#az-iot-ops-create) command. This command might take several minutes to complete. You can watch the progress in the deployment progress display in the terminal.
Copy file name to clipboardExpand all lines: articles/iot-operations/deploy-iot-ops/howto-prepare-cluster.md
+24-11Lines changed: 24 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,19 +12,19 @@ ms.date: 10/23/2024
12
12
13
13
# Prepare your Azure Arc-enabled Kubernetes cluster
14
14
15
-
An Azure Arc-enabled Kubernetes cluster is a prerequisite for deploying Azure IoT Operations. This article describes how to prepare a cluster before you deploy Azure IoT Operations. This article includes guidance for Ubuntu, Windows, Azure Local, and vSphere Kubernetes Service (VKS), formerly Tanzu Kubernetes Grid Service.
15
+
An Azure Arc-enabled Kubernetes cluster is a prerequisite for deploying Azure IoT Operations. This article describes how to prepare a cluster before you deploy Azure IoT Operations. This article includes guidance for Ubuntu, Windows, Azure Local, and Tanzu Kubernetes Grid (TKG).
16
16
17
17
If you want to deploy Azure IoT Operations quickly and run a sample workload in a test environment, see the [Quickstart: Run Azure IoT Operations in GitHub Codespaces with K3s](../get-started-end-to-end-sample/quickstart-deploy.md).
18
18
19
19
## Prerequisites
20
20
21
-
For multi-node deployments, K3s for deployments on Ubuntu, AKS deployments on Azure Local, and VKS. Azure Kubernetes Service (AKS) Edge Essentials for Windows only supports single-node deployments.
21
+
For multi-node deployments, K3s for deployments on Ubuntu, AKS deployments on Azure Local, and Tanzu Kubernetes release (TKr) on TKG. Azure Kubernetes Service (AKS) Edge Essentials for Windows only supports single-node deployments.
22
22
23
23
### [Ubuntu](#tab/ubuntu)
24
24
25
25
To prepare an Azure Arc-enabled Kubernetes cluster, you need:
26
26
27
-
[!INCLUDE [Cluster prerequisites for Ubuntu and VKS](../includes/cluster-prerequisites.md)]
27
+
[!INCLUDE [Cluster prerequisites for Ubuntu and Tanzu](../includes/cluster-prerequisites.md)]
28
28
29
29
* Hardware that meets the system requirements:
30
30
@@ -60,20 +60,20 @@ To prepare an Azure Arc-enabled Kubernetes cluster, you need:
-[TKG with a standalone management cluster.](https://techdocs.broadcom.com/us/en/vmware-tanzu/standalone-components/tanzu-kubernetes-grid/2-5/tkg/mgmt-index.html)
-[Azure Arc-enabled Kubernetes system requirements](/azure/azure-arc/kubernetes/system-requirements).
75
75
76
-
-[Requirements for running VKS clusters](https://techdocs.broadcom.com/us/en/vmware-cis/vcf/vsphere-supervisor-services-and-standalone-components/latest/managing-vsphere-kubernetes-service/running-tkg-service-clusters.html)
@@ -239,12 +239,25 @@ By default, a Kubernetes cluster is created with a node pool that can run Linux
239
239
240
240
Then, once you have an Azure Arc-enabled Kubernetes cluster, you can [deploy Azure IoT Operations](howto-deploy-iot-operations.md).
241
241
242
-
### [VKS](#tab/vks)
242
+
### [TKG with a management cluster](#tab/tkgm)
243
243
244
-
For guidance on setting up a VKS cluster, see [Deploying VKS Service Clusters](https://techdocs.broadcom.com/us/en/vmware-cis/vcf/vsphere-supervisor-services-and-standalone-components/latest/managing-vsphere-kubernetes-service/running-tkg-service-clusters/deploying-tkg-service-clusters.html).
244
+
To prepare a TKG workload cluster, you need:
245
245
246
+
- A single-node or multi-node TKG workload cluster. For guidance, see the [Tanzu documentation](https://techdocs.broadcom.com/us/en/vmware-tanzu/standalone-components/tanzu-kubernetes-grid/2-5/tkg/workload-clusters-index.html).
247
+
248
+
### Update pod security admission settings
249
+
250
+
Before deploying Azure IoT Operations, you will need to update the Pod Security Admission settings on your TKG cluster. Applying this file will pre-create namespace labels and set pod security to `privileged`.
> When you initialize your Azure IoT Operations instance on a VKS cluster with its [pod security admission controller running in restricted mode](https://techdocs.broadcom.com/us/en/vmware-cis/vcf/vsphere-supervisor-services-and-standalone-components/latest/managing-vsphere-kuberenetes-service-clusters-and-workloads/managing-security-for-tkg-service-clusters/configure-psa-for-tkr-1-25-and-later.html) you must include the `--cm-config global.telemetry.logs.enabled=false` flag when you run `az iot ops init`.
260
+
-->
248
261
249
262
### Arc-enable your cluster
250
263
@@ -299,7 +312,7 @@ Connect your cluster to Azure Arc so that it can be managed remotely.
299
312
300
313
Save the output of this command to use in the next steps.
301
314
302
-
1. Connect to the VKS cluster. Edit the custom resource for the workload cluster with the issuer URL from the previous step.
315
+
1. Connect to the TKG management cluster. Edit the custom resource for the workload cluster with the issuer URL from the previous step.
|[K3s](https://www.rancher.com/products/k3s)| x86_64 | General availability |*1.33.6*|*Ubuntu 24.04*, <br> Red Hat Enterprise Linux (RHEL) 9.x |
27
-
|[vSphere Kubernetes Service (VKS)](https://techdocs.broadcom.com/us/en/vmware-cis/vcf/vsphere-supervisor-services-and-standalone-components/latest/release-notes/vmware-tanzu-kubernetes-grid-service-release-notes.html)| x86_64 | General availability |*1.32.7*|*VKS*|
|[RKE2](https://docs.rke2.io/)| x86_64 | General availability |*v1.35.0+rke2r1*|[Operating systems](https://docs.rke2.io/install/requirements#operating-systems)|
29
29
30
30
* The *minimum validated version* is the lowest version of the Kubernetes distribution that Microsoft uses to validate Azure IoT Operations deployments.
Copy file name to clipboardExpand all lines: articles/iot-operations/includes/supported-environments.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,4 +10,4 @@ ms.custom:
10
10
---
11
11
12
12
> [!IMPORTANT]
13
-
> Currently, K3s on Ubuntu 24.04 and vSphere Kubernetes Service are the only platforms for deploying Azure IoT Operations in production. To learn more, see [Supported environments](../deploy-iot-ops/overview-deploy.md#supported-environments).
13
+
> Currently, K3s on Ubuntu 24.04 and Tanzu Kubernetes Service are the only platforms for deploying Azure IoT Operations in production. To learn more, see [Supported environments](../deploy-iot-ops/overview-deploy.md#supported-environments).
0 commit comments