infra-azure-provisioning issueshttps://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/issues2023-02-14T12:44:18Zhttps://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/issues/253[BUG] "ApplicationGatewayRequestRoutingRulePriorityCannotBeEmpty" Errors in G...2023-02-14T12:44:18ZLucy Liu[BUG] "ApplicationGatewayRequestRoutingRulePriorityCannotBeEmpty" Errors in Gateway DeploymentDuring a greenfield Azure OSDU deployment from the master branch dated 1/27/2023, the "ApplicationGatewayRequestRoutingRulePriorityCannotBeEmpty" errors were observed in the Service Resources deployment step about Gateway resources, both...During a greenfield Azure OSDU deployment from the master branch dated 1/27/2023, the "ApplicationGatewayRequestRoutingRulePriorityCannotBeEmpty" errors were observed in the Service Resources deployment step about Gateway resources, both appgw and istiogw. Further investigation shows, due to the azurerm version upgrade, routing rule priority is a required parameter now for gateway resources. Adding them to the terraform config files manually fixed the errors.Arturo Hernandez [EPAM]Igor Zimovets (EPAM)shivani karipeArturo Hernandez [EPAM]https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/issues/254[BUG] "ZonalApplicationGatewayCannotReferenceNoZonePublicIP" Error in Gateway...2023-02-14T12:44:17ZLucy Liu[BUG] "ZonalApplicationGatewayCannotReferenceNoZonePublicIP" Error in Gateway DeploymentDuring a greenfield Azure OSDU deployment from the master branch dated 1/27/2023, the "ZonalApplicationGatewayCannotReferenceNoZonePublicIP" errors were observed in the Service Resources deployment step about Gateway resources, both appg...During a greenfield Azure OSDU deployment from the master branch dated 1/27/2023, the "ZonalApplicationGatewayCannotReferenceNoZonePublicIP" errors were observed in the Service Resources deployment step about Gateway resources, both appgw and istiogw. Further investigation shows, due to the azurerm version upgrade, this rule seems to be introduced for gateway resources. Adding zones for the public IP resources to the terraform config files for the gw and istiogw manually fixed the errors.Arturo Hernandez [EPAM]Igor Zimovets (EPAM)shivani karipeArturo Hernandez [EPAM]https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/issues/250502 Bad Gateway Error in OSDU Azure Instance Created through Greenfield Deplo...2023-02-10T23:11:23ZLucy Liu502 Bad Gateway Error in OSDU Azure Instance Created through Greenfield DeploymentAn OSDU Azure instance was created through greenfield deployment following the wiki in this project and [helm-charts-azure project](https://community.opengroup.org/osdu/platform/deployment-and-operations/helm-charts-azure). Testing in PO...An OSDU Azure instance was created through greenfield deployment following the wiki in this project and [helm-charts-azure project](https://community.opengroup.org/osdu/platform/deployment-and-operations/helm-charts-azure). Testing in POSTMan results in "502 Bad Gateway" error for all the requests sent to the deployed instance. The latest code (as of 1/5/2023) in master branch was used for deployment and DNS points to the deployed istio gateway. The same error was observed in another greenfield deployment in another region.shivani karipeNaresh Jampalashivani karipehttps://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/issues/218Enable pod security policies for AKS cluster2023-02-02T14:28:12ZBharathi SelvarajEnable pod security policies for AKS cluster**Azure Policy built-in definitions for Azure Kubernetes Service**
For new OSDU deployment on Azure, make sure the following security policies are enabled for AKS
[Built-in policy definitions for Azure Kubernetes Service - Azure Kuberne...**Azure Policy built-in definitions for Azure Kubernetes Service**
For new OSDU deployment on Azure, make sure the following security policies are enabled for AKS
[Built-in policy definitions for Azure Kubernetes Service - Azure Kubernetes Service | Microsoft Docs](https://docs.microsoft.com/en-us/azure/aks/policy-reference)
- [x] Enable AKS Policies for osdu-azure namespace
- [x] Enable AKS policies for istio-system namespace
- [x] Enable AKS policies for airflow2 namespace
- [x] Move csi secrets to kube-system as recommended by Microsoft docs [Docs](https://docs.microsoft.com/en-us/azure-stack/aks-hci/secrets-store-csi-driver#install-the-secrets-store-csi-driver)
- [x] Fix non compliant policies - Allow Authorized IP Ranges, Enable private clusters.
- [x] Documentation on how to enable the feature and fix compliance issues.M11 - Release 0.14Krishna Nikhil VedurumudiKrishna Nikhil Vedurumudihttps://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/issues/248data-partition terraform unsupported attribute error for resource "azurerm_ke...2023-01-18T16:19:21ZFabien Bosquetdata-partition terraform unsupported attribute error for resource "azurerm_key_vault_secret" "storage_account_blob_endpoint"I have an error when following the manual install of the azure infrastructure.
The issue appears when running `terraform plan` for the `data-partition` as described here.
https://community.opengroup.org/osdu/platform/deployment-and-oper...I have an error when following the manual install of the azure infrastructure.
The issue appears when running `terraform plan` for the `data-partition` as described here.
https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/blob/master/infra/templates/osdu-r3-mvp/data_partition/README.md
```
terraform plan -var-file custom.tfvars
╷
│ Warning: Deprecated attribute
│
│ on ../../../modules/providers/azure/aks/main.tf line 169, in resource "azurerm_kubernetes_cluster" "main":
│ 169: addon_profile[0].oms_agent[0].log_analytics_workspace_id
│
│ The attribute "log_analytics_workspace_id" is deprecated. Refer to the provider documentation for details.
│
│ (and one more similar warning elsewhere)
╵
╷
│ Warning: Argument is deprecated
│
│ with module.service_bus.azurerm_servicebus_namespace_authorization_rule.main,
│ on ../../../modules/providers/azure/service-bus/main.tf line 144, in resource "azurerm_servicebus_namespace_authorization_rule" "main":
│ 144: namespace_name = azurerm_servicebus_namespace.main.name
│
│ Deprecated in favor of "namespace_id"
│
│ (and 18 more similar warnings elsewhere)
╵
╷
│ Error: Unsupported attribute
│
│ on secrets.tf line 103, in resource "azurerm_key_vault_secret" "storage_account_blob_endpoint":
│ 103: value = module.storage_account.endpoint
│ ├────────────────
│ │ module.storage_account is a object
│
│ This object does not have an attribute named "endpoint".
```Arturo Hernandez [EPAM]shivani karipeArturo Hernandez [EPAM]https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/issues/251Terraform Script for Istio Gateway Missing "aks_dns_host" in Terraform Variab...2023-01-16T21:16:47ZLucy LiuTerraform Script for Istio Gateway Missing "aks_dns_host" in Terraform Variable ConfigurationIn Service Resource deployment step, terraform variable "aks_dns_host" needs to be allowed to be customized to match the actual DNS A record. It is missing in the default "infra\templates\osdu-r3-mvp\service_resources\terraform.tfvars" f...In Service Resource deployment step, terraform variable "aks_dns_host" needs to be allowed to be customized to match the actual DNS A record. It is missing in the default "infra\templates\osdu-r3-mvp\service_resources\terraform.tfvars" file and missing in the wiki customization script for "custom.tfvars" file. This leads to the wrong Host name (default contoso.com) being added to the Backend setting in the istio gateway deployed by the istio Helm Chart in later stage.Arturo Hernandez [EPAM]Arturo Hernandez [EPAM]https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/issues/236Use IstioGw + AppGw in terraform instead of AGIC2023-01-16T21:15:03ZArturo Hernandez [EPAM]Use IstioGw + AppGw in terraform instead of AGIC* Use istiogw instead of agic controller and test in glab, this might decrease downtime which seems to be happening. (Issue with the AGIC controller)
---
Current work done so far it was to enable by default istio AppGw in the terraform...* Use istiogw instead of agic controller and test in glab, this might decrease downtime which seems to be happening. (Issue with the AGIC controller)
---
Current work done so far it was to enable by default istio AppGw in the terraform code, however, as we are moving towards deprecate AGIC, we need to implement different module or create logic in module to modify the routing rules accordingly, as current terraform code, ignore http backend rules and so on, also we need to agreed on some static ip address to be used by default for istio gw and this internal ip address should be used as well in the helm-charts-azure.
It will require to handle correctly the letsencrypt/acme certificate issuer, which currently it is not working correctly and job in helm-charts-azure keeps failing constantly, we should attempt to fix the job as well as to make this certification smoother using maybe [istio-ingress-class](https://istio.io/latest/docs/ops/integrations/certmanager/#kubernetes-ingress).
Main issue it would be that AppGw should expose port 80 as well, therefore some rule might need be needed to handle the default 80 port or redirect to proper https service, means this change should be applied on infra and helmM16 - Release 0.19Arturo Hernandez [EPAM]shivani karipeArturo Hernandez [EPAM]https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/issues/249[BUG] Fix ApplicationGatewayKeyVaultSecretException from Istio Gateway Deploy...2022-12-19T23:37:07ZLucy Liu[BUG] Fix ApplicationGatewayKeyVaultSecretException from Istio Gateway DeploymentIn Greenfield Azure OSDU deployment, the ApplicationGatewayKeyVaultSecretException was observed during "Service Resource" deployment step resulting to Istio gateway resource created in a failed state. Detail error message:
Error: waitin...In Greenfield Azure OSDU deployment, the ApplicationGatewayKeyVaultSecretException was observed during "Service Resource" deployment step resulting to Istio gateway resource created in a failed state. Detail error message:
Error: waiting for create/update of Application Gateway: (Name "xxxx-gw" / Resource Group "xxxx-rg"): Code="ApplicationGatewayKeyVaultSecretException" Message="Problem occured while accessing and validating KeyVault Secrets associated with Application Gateway '/subscriptions/xxxx/resourceGroups/xxxx-rg/providers/Microsoft.Network/applicationGateways/xxxx-gw'. See details below:" Details=\[{"code":"0","message":"Operation returned an invalid status code 'Forbidden'"}\]M15 - Release 0.18Arturo Hernandez [EPAM]shivani karipeArturo Hernandez [EPAM]https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/issues/235Change ADO logic to use helm-charts-azure2022-10-04T10:52:54ZArturo Hernandez [EPAM]Change ADO logic to use helm-charts-azure**Requirements (Updated)**
We started initial migration for osdu-base/ osdu-istio helm chart to helm-charts-azure, this was affecting customers, we decided to rollback.
- [x] Need to rollback changes to use flux again for common and ch...**Requirements (Updated)**
We started initial migration for osdu-base/ osdu-istio helm chart to helm-charts-azure, this was affecting customers, we decided to rollback.
- [x] Need to rollback changes to use flux again for common and chart-* pipelines.
~~**Requirements (Deprecated)**~~
- [ ] ~~Refactor current azure devops pipeline to get the helm charts for each service from the helm-charts-azure repo, instead of the `devops/azure` directory.~~
- [ ] ~~Pipeline should create helm-chart in ACR as well to use that same helm-chart and common helm values to install new service instead of using flux.~~
- [ ] ~~Add test for helm charts, lint, template in the pipelines steps.~~
- [ ] ~~Allow option to choose osdu-azure subgroup install or single service install only.~~
**User Documentation**
- [ ] ~~Refactor if needed documentation about services deployment.~~M14 - Release 0.17Arturo Hernandez [EPAM]Aliaksei Kruk2Arturo Hernandez [EPAM]https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/issues/237Automation gaps in Release process - Phase 22022-09-29T19:33:37ZKrishna Nikhil VedurumudiAutomation gaps in Release process - Phase 2- [x] Create Service Groups in Helm charts structure to be able to deploy multiple services using single helm chart.
- [x] Build pipelines to update Service Group helm chart's version for any increment in patch version.
- [x] Conditio...- [x] Create Service Groups in Helm charts structure to be able to deploy multiple services using single helm chart.
- [x] Build pipelines to update Service Group helm chart's version for any increment in patch version.
- [x] Conditionally deploy individual services
- [x] Pipeline to deploy helm charts on demand
- [x] Open items from Phase 1
- [x] Refactor helm package codeM14 - Release 0.17Arturo Hernandez [EPAM]Arturo Hernandez [EPAM]https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/issues/239Swagger Sanity Phase 1: Swagger API to be tested as a part of integration tests.2022-09-29T13:44:54ZKomal MakkarSwagger Sanity Phase 1: Swagger API to be tested as a part of integration tests.
## Context
The swagger APIs are maintained as part of each service, for instance [Storage Swagger Controller](https://community.opengroup.org/osdu/platform/system/storage/-/blob/master/storage-core/src/main/java/org/opengroup/osdu/stor...
## Context
The swagger APIs are maintained as part of each service, for instance [Storage Swagger Controller](https://community.opengroup.org/osdu/platform/system/storage/-/blob/master/storage-core/src/main/java/org/opengroup/osdu/storage/swagger/HomeController.java).
These APIs should be tested in service integration test suite.
## Assumption
The swagger endpoint is a part of all services.
## Problem statement
The endpoint ends up being down for few services in few releases and the cost of discovery and fixing becomes high.
## Proposed solution
The service's IT suite should have a test for the swagger endpoint as well.
We can start with one positive case of 200, assuming no service has auth required for Swagger by design.
## Scope / Acceptance Criteria
The above effort will encapsulate the following
1. Swagger endpoint is reachable and returning a value.
# Target Release
@krveduru to add
# FAQ
N/A
## Useful references
N/AM14 - Release 0.17Yaraslau SushchykYaraslau Sushchykhttps://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/issues/127Elastic Search - Version 72022-09-15T23:49:37ZDaniel SchollElastic Search - Version 7Currently the Infrastructure Version for Elastic Search was Version 6. This has now been changed to Version 7 and updated in the Search Service.
https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/70
D...Currently the Infrastructure Version for Elastic Search was Version 6. This has now been changed to Version 7 and updated in the Search Service.
https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/70
Documentation Changes need to occur where Version 6 was noted.M4 - Release 0.7 - removeDaniel SchollDaniel Schollhttps://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/issues/59Create Documentation on Contributing to Ingestion Framework2022-09-15T23:49:37ZJasonCreate Documentation on Contributing to Ingestion FrameworkWe need to create documentation for developers on how they can contribute DAGS to OSDU on Azure. The desired location for this documentation is docs/contributing-to-ingestion-framework.md.We need to create documentation for developers on how they can contribute DAGS to OSDU on Azure. The desired location for this documentation is docs/contributing-to-ingestion-framework.md.https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/issues/58Create Documentation on Onboarding Client Applications2022-09-15T23:49:37ZJasonCreate Documentation on Onboarding Client ApplicationsWe need to create documentation for clients on how they can onboard with OSDU on Azure. The desired location for this documentation is docs/onboarding-client-applications.md.We need to create documentation for clients on how they can onboard with OSDU on Azure. The desired location for this documentation is docs/onboarding-client-applications.md.https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/issues/47Support blue-green deployments2022-09-15T12:09:38ZSherman YangSupport blue-green deploymentsEnhance deployment architecture to handle blue-green deployments. Infrastructure and pipelines need to be enhanced/updated to support blue-green deployments. This is needed to allow zero downtime upgrade/redeployments after changes or ke...Enhance deployment architecture to handle blue-green deployments. Infrastructure and pipelines need to be enhanced/updated to support blue-green deployments. This is needed to allow zero downtime upgrade/redeployments after changes or key rotations. It would also allow time to test the new deployments and fix issues before exposing the new deployments to clients.
https://docs.microsoft.com/en-us/samples/microsoft/aks-postgre-keyrotation/blue--green-secret-rotation-with-azure-keyvault-and-aks/DecemberDaniel SchollDaniel Schollhttps://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/issues/229External/proxy Dataset Service Onboarding2022-08-26T14:20:51ZArturo Hernandez [EPAM]External/proxy Dataset Service Onboarding**Service name**: `External Dataset for External Data source ingestion`
The following steps must be completed for a service to onboard with OSDU on Azure. Additionally, please add the `Service Onboarding` tag to this issue when it is cr...**Service name**: `External Dataset for External Data source ingestion`
The following steps must be completed for a service to onboard with OSDU on Azure. Additionally, please add the `Service Onboarding` tag to this issue when it is created.
For more information, visit our service onboarding documentation [here](https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/blob/master/docs/service-onboarding.md).
## Steps:
**Infrastructure and Initial Requirements**
- [x] Add any additional Azure cloud infrastructure (Cosmos containers, Storage containers, fileshares, etc.) to the Terraform template. [Link](https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/tree/master/infra/templates/osdu-r3-mvp). Note that if the infrastructure is a part of the data-partition template, you may need to add secrets to the keyvault that are partition specific; if doing so, update the createPartition REST request to include the keys that you have added so they are accessible in service code. [Link](https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/blob/master/tools/rest/partition.http#L48)
- [x] Create an ingress point for the service. [Link](https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/blob/master/charts/osdu-common/templates/appgw-ingress.yaml)
- [x] Add any test data that is required for the service integration tests. [Link](https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/tree/master/tools/test_data)
- [ ] Update `upload-data.py` to upload any new test data files you created. [Link](https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/blob/master/tools/test_data/upload-data.py).
- [x] Update the integration tester with any entitlements required to test the service. [Link](https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/blob/master/tools/test_data/user_info_1.json)
- [x] Add in any new secrets that the service needs to run. [Link](https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/blob/master/charts/osdu-common/templates/kv-secrets.yaml)
- [x] Create environment variable script to generate .yaml files to be used with Intellij [EnvFile](https://plugins.jetbrains.com/plugin/7861-envfile) plugin and .envrc files to be used with [direnv](https://direnv.net/). [Link](https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/tree/master/tools/variables)
**Gitlab Code and Documentation**
- [x] Complete the service code such that it passes all integration tests locally. There is some documentation on starting off implementing an Azure provider. [Link](./gitlab-service-readme-template.md)
- [x] Create helm charts for service. The charts for each service are located in the `devops/azure` directory. You can look at charts from other services as a model. The charts will be nearly identical except for the different environment variables, values, etc each service needs to run. [Link](./gitlab-service-guide.md)
- [x] Implement Istio for the service if this has not already been done. Here is an example MR that shows what steps are required. [Link](https://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/64)
- [x] Create an Istio auth policy in the `devops/azure/chart/templates` directory. Here is an example of an Istio auth policy that is generic and can be used by other services. [Link](https://community.opengroup.org/osdu/platform/system/storage/-/blob/master/devops/azure/chart/templates/azure-istio-auth-policy.yaml)
- [x] Add any variables that are required for the service integration tests to the Azure CI-CD file. [Link](https://community.opengroup.org/osdu/platform/ci-cd-pipelines/-/blob/master/cloud-providers/azure.yml)
- [x] Verify that the README for the Azure provider correctly and clearly describes how to run and test the service. There is a README template to help. [Link](./gitlab-service-readme-template.md)
- [x] Push any changes and verify that the Gitlab pipeline is passing in master.
**Development and Demo Azure Devops Pipelines**
- [x] Create development ADO pipeline at `devops/azure/development-pipeline.yml` in the service repo.
- [x] Verify development pipeline passes in ADO.
- [x] Create Demo ADO pipeline at `devops/azure/pipeline.yml` in the service repo.
- [x] Verify demo pipeline is passing in ADO.
**User Documentation**
- [x] Add the service to the mirror pipeline instructions. [Link](https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/blob/master/docs/code-mirroring.md)
- [x] Add the service to the manual deployment instructions. [Link](https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/tree/master/charts)
- [x] Add any required variables to the already existing variable group instructions for automated deployment. You should know if any variables need to be added to existing variable groups from creating the development and demo pipelines. [Link](https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/blob/master/docs/service-automation.md#create-osdu-service-libraries)
- [x] Add a variable group `Azure Service Release - $SERVICE_NAME` to the documentation. You should know what values to set for this variable group from creating the development and demo pipelines. [Link](https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/blob/master/docs/service-automation.md#create-osdu-service-libraries)
- [x] Add a step for creating the service pipeline at the bottom of the service-automation page. [Link](https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/blob/master/docs/service-automation.md#create-osdu-service-libraries)
- [x] Create a rest script with sample calls to the service for users. [Link](https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/tree/master/tools/rest)M13 - Release 0.16Rene von Borstel [EPAM]Arturo Hernandez [EPAM]Rene von Borstel [EPAM]https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/issues/158Add a new airflow variable for search service cursor url2022-08-23T11:19:22ZVineeth Guna [Microsoft]Add a new airflow variable for search service cursor urlWe need to add a new airflow variable AIRFLOW_VAR_CORE__SERVICE__SEARCH_WITH_CURSOR__URL pointing to OSDU search service query cursor API, as this is consumed in manifest ingestion
For reference check this MR - https://community.opengro...We need to add a new airflow variable AIRFLOW_VAR_CORE__SERVICE__SEARCH_WITH_CURSOR__URL pointing to OSDU search service query cursor API, as this is consumed in manifest ingestion
For reference check this MR - https://community.opengroup.org/osdu/platform/data-flow/ingestion/ingestion-dags/-/merge_requests/47 which is mergedhttps://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/issues/150Feature Change - Add alert rule for CPU usage of OSDU services2022-08-23T11:19:19ZVibhuti Sharma [Microsoft]Feature Change - Add alert rule for CPU usage of OSDU servicesWe need to add an alert rule which will alert when the CPU usage of any OSDU service is above a threshold value. Currently there are no alert rules configured in the infrastructure.
**Acceptance Criteria**
1) ADR to document the decisio...We need to add an alert rule which will alert when the CPU usage of any OSDU service is above a threshold value. Currently there are no alert rules configured in the infrastructure.
**Acceptance Criteria**
1) ADR to document the decision to add alert rules in the appropriate resource group.
2) Necessary code to add alert rule.
3) Create or update required documentationM6 - Release 0.9 - removeVibhuti Sharma [Microsoft]Vibhuti Sharma [Microsoft]https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/issues/168Close Release - Drop Release 0.92022-08-23T11:19:18ZMANISH KUMARClose Release - Drop Release 0.9Release 0.9 (Milestone M6) has dropped and we need to close out the Release.
#### Chart `partition-services`
- [x] Partition Service
#### Chart `security-services`
- [x] Entitlements V1 Service
- [x] Entitlements V2 Service
- [x] Legal...Release 0.9 (Milestone M6) has dropped and we need to close out the Release.
#### Chart `partition-services`
- [x] Partition Service
#### Chart `security-services`
- [x] Entitlements V1 Service
- [x] Entitlements V2 Service
- [x] Legal Service
- [x] Policy Service
#### Chart `core-services`
- [x] Storage Service
- [x] Indexer Queue
- [x] Indexer Service
- [x] Search Service
- [x] File Service
- [x] Register Service
- [x] Notification Service
- [x] Indexer Queue
#### Chart `reference-services`
- [x] Unit Service
- [x] CRS Catalog
- [x] CRS Conversion
#### Chart `ingest-services`
- [x] WKS
- [x] Workflow
#### Chart `seismic-services`
- [x] Seismic DDMS
#### Chart `wellbore-services`
- [x] Wellbore DDMSM6 - Release 0.9 - removehttps://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/issues/170BUG: Schema service update elastic for any new schema add2022-08-23T11:19:15ZMANISH KUMARBUG: Schema service update elastic for any new schema addSchema service has a bug that it doesn't update indices for new schema insertion which is being fixed by this issue.
The changes are merged using [MR](https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-p...Schema service has a bug that it doesn't update indices for new schema insertion which is being fixed by this issue.
The changes are merged using [MR](https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/merge_requests/268).M6 - Release 0.9 - removeAbhishek Kumar (SLB)Abhishek Kumar (SLB)