Skip to content

Commit

Permalink
Helm: Change the chart to deploy 2.8.2 version of Azure IIoT platform. (
Browse files Browse the repository at this point in the history
  • Loading branch information
karok2m authored Mar 23, 2022
1 parent f9f2591 commit adbf998
Show file tree
Hide file tree
Showing 7 changed files with 71 additions and 68 deletions.
2 changes: 1 addition & 1 deletion deploy/helm/azure-industrial-iot/Chart.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -15,4 +15,4 @@ maintainers:
- name: Karapet Kostandyan
email: [email protected]
icon: https://raw.githubusercontent.com/Azure/Industrial-IoT/main/docs/media/microsoft-symbol.png
appVersion: 2.8.1
appVersion: 2.8.2
4 changes: 2 additions & 2 deletions deploy/helm/azure-industrial-iot/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -457,7 +457,7 @@ The following details of the Azure Log Analytics Workspace would be required:
## Installing the Chart
This chart installs `2.8.1` version of components by default.
This chart installs `2.8.2` version of components by default.
To install the chart first ensure that you have added `azure-iiot` repository:
Expand Down Expand Up @@ -519,7 +519,7 @@ values.
| Parameter | Description | Default |
|---------------------|------------------------------------------|---------------------|
| `image.registry` | URL of Docker Image Registry | `mcr.microsoft.com` |
| `image.tag` | Image tag | `2.8.1` |
| `image.tag` | Image tag | `2.8.2` |
| `image.pullPolicy` | Image pull policy | `IfNotPresent` |
| `image.pullSecrets` | docker-registry secret names as an array | `[]` |
Expand Down
2 changes: 1 addition & 1 deletion deploy/helm/azure-industrial-iot/values.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ image:
# image.registry is URL of Docker registry from where images will be pulled.
registry: mcr.microsoft.com
# image.tag defines which version of Docker images to pull.
tag: 2.8.1
tag: 2.8.2
# image.pullPolicy defines value of imagePullPolicy of deployments.
pullPolicy: IfNotPresent
# image.pullSecrets defined docker-registry secrets that should be used for private container registries.
Expand Down
12 changes: 6 additions & 6 deletions docs/deploy/howto-add-aks-to-ps1.md
Original file line number Diff line number Diff line change
Expand Up @@ -309,7 +309,7 @@ Note the following values in the YAML file:

```yaml
image:
tag: 2.8.1
tag: 2.8.2
loadConfFromKeyVault: true
Expand Down Expand Up @@ -349,8 +349,8 @@ deployment:
hostName: aks-cluster-ip.westeurope.cloudapp.azure.com
```

> **NOTE**: Please note that we have used `2.8.1` as the value of `image:tag` configuration parameter
> above. That will result in `2.8.1` version of microservices and edge modules to be deployed. If you want
> **NOTE**: Please note that we have used `2.8.2` as the value of `image:tag` configuration parameter
> above. That will result in `2.8.2` version of microservices and edge modules to be deployed. If you want
> to deploy a different version of the platform, please specify it as the value of `image:tag` parameter.

#### Passing Azure resource details through YAML file
Expand Down Expand Up @@ -391,7 +391,7 @@ Note the following values in the YAML file:

```yaml
image:
tag: 2.8.1
tag: 2.8.2
azure:
tenantId: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
Expand Down Expand Up @@ -480,8 +480,8 @@ deployment:
hostName: aks-cluster-ip.westeurope.cloudapp.azure.com
```

> **NOTE**: Please note that we have used `2.8.1` as the value of `image:tag` configuration parameter
> above. That will result in `2.8.1` version of microservices and edge modules to be deployed. If you want
> **NOTE**: Please note that we have used `2.8.2` as the value of `image:tag` configuration parameter
> above. That will result in `2.8.2` version of microservices and edge modules to be deployed. If you want
> to deploy a different version of the platform, please specify it as the value of `image:tag` parameter.

#### Installing `azure-industrial-iot` Helm chart
Expand Down
12 changes: 6 additions & 6 deletions docs/deploy/howto-deploy-aks.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,11 +28,11 @@
* [User Interface](#user-interface)
* [Resources](#resources)

`Microsoft.Azure.IIoT.Deployment` is a command line application for deploying the Azure Industrial IoT solution,
`Microsoft.Azure.IIoT.Deployment` is a command line application for deploying the Azure Industrial IoT solution,
which deploys the required Azure infrastructure resources and microservices required by the Azure Industrial IoT solution.
By default, it deploys `2.8.1` version of Azure Industrial IoT microservices.

The main difference between the [script based deployment](howto-deploy-all-in-one.md) option is that
The main difference between the [script based deployment](howto-deploy-all-in-one.md) option is that
`Microsoft.Azure.IIoT.Deployment` deploys microservices to an Azure
Kubernetes Service (AKS) cluster, while `deploy.ps1` runs the entire platform as a web application.

Expand Down Expand Up @@ -346,11 +346,11 @@ You will still need to run the application once before granting the consent and
[10:33:44 INF] Created Azure Public IP for AKS cluster.
[10:33:44 INF] Pushing IIoT configuration parameters to Key Vault...
[10:33:45 DBG] Uploading data to Azure Blob ...
[10:33:45 DBG] Uploadede data to Azure Blob.
[10:33:45 DBG] Uploaded data to Azure Blob.
[10:33:45 DBG] Uploading data to Azure Blob ...
[10:33:45 DBG] Uploadede data to Azure Blob.
[10:33:45 DBG] Uploaded data to Azure Blob.
[10:33:45 DBG] Uploading data to Azure Blob ...
[10:33:45 DBG] Uploadede data to Azure Blob.
[10:33:45 DBG] Uploaded data to Azure Blob.
[10:46:13 INF] Pushed IIoT configuration parameters to Key Vault.
Use the following credentials to login to jumpbox:
Expand All @@ -359,7 +359,7 @@ You will still need to run the application once before granting the consent and
```
Please save this username and password as you will need them to login to jumpbox VM from where Helm
charts have beed deployed. Note that VM is de-allocated after successful deployment, but you can easily
charts have been deployed. Note that VM is de-allocated after successful deployment, but you can easily
start it.
9. After that you would be provided with an option to save connection details of deployed resources to
Expand Down
3 changes: 3 additions & 0 deletions docs/deploy/howto-deploy-helm.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,8 @@ of our microservices:
Platform microservices.
- `0.4.1` version of `azure-industrial-iot` Helm chart to deploy `2.8.1` version of Azure Industrial IoT
Platform microservices.
- `0.4.2` version of `azure-industrial-iot` Helm chart to deploy `2.8.2` version of Azure Industrial IoT
Platform microservices.

## Installing The Chart

Expand All @@ -30,6 +32,7 @@ Kubernetes cluster:
- For `0.3.2` version of the Chart: [Azure Industrial IoT Helm Chart v0.3.2](https://github.com/Azure/Industrial-IoT/blob/helm_0.3.2/deploy/helm/azure-industrial-iot/README.md)
- For `0.4.0` version of the Chart: [Azure Industrial IoT Helm Chart v0.4.0](https://github.com/Azure/Industrial-IoT/blob/helm_0.4.0/deploy/helm/azure-industrial-iot/README.md)
- For `0.4.1` version of the Chart: [Azure Industrial IoT Helm Chart v0.4.1](https://github.com/Azure/Industrial-IoT/blob/helm_0.4.1/deploy/helm/azure-industrial-iot/README.md)
- For `0.4.2` version of the Chart: [Azure Industrial IoT Helm Chart v0.4.2](https://github.com/Azure/Industrial-IoT/blob/helm_0.4.2/deploy/helm/azure-industrial-iot/README.md)

For latest documentation and chart sources please check [deploy/helm/azure-industrial-iot/](../../deploy/helm/azure-industrial-iot/)
directory on `main` branch.
Expand Down
Loading

0 comments on commit adbf998

Please sign in to comment.