Merge pull request #233905 from MicrosoftDocs/release-arc-data

v-alje · web-flow · commit 0e2b5674210c · 2023-04-11T13:53:02.000-07:00
Publish Azure Arc-data April 2024 release
diff --git a/articles/azure-arc/data/includes/azure-arc-data-preview-release.md b/articles/azure-arc/data/includes/azure-arc-data-preview-release.md
@@ -5,11 +5,10 @@ ms.service: azure-arc
 ms.topic: include
 ms.date: 12/7/2022
 ---
-<!---
-At this time, a test or preview build is not available for the next release.
--->
 
+At this time, a test or preview build is not available for the next release.
 
+<!---
 April 2023 preview release is now available.
 
 |Component|Value|
@@ -45,3 +44,4 @@ April 2023 preview release is now available.
 - Arc SQL Server | Azure Policy to enable best practices assessment at scale
 - Arc PostgreSQL | Ensure postgres extensions work per database/role.
 - Arc PostgreSQL | Upload metrics/logs to Azure Monitor
+-->
diff --git a/articles/azure-arc/data/managed-instance-disaster-recovery.md b/articles/azure-arc/data/managed-instance-disaster-recovery.md
diff --git a/articles/azure-arc/data/media/business-continuity/dag.png b/articles/azure-arc/data/media/business-continuity/dag.png
diff --git a/articles/azure-arc/data/media/business-continuity/distributed-availability-group.png b/articles/azure-arc/data/media/business-continuity/distributed-availability-group.png
diff --git a/articles/azure-arc/data/release-notes.md b/articles/azure-arc/data/release-notes.md
@@ -17,6 +17,23 @@ ms.custom: references_regions, devx-track-azurecli, event-tier1-build-2022
 
 This article highlights capabilities, features, and enhancements recently released or improved for Azure Arc-enabled data services.
 
+## April 12, 2023
+
+### Image tag
+
+`v1.18.0_2023-04-11`
+
+For complete release version information, see [Version log](version-log.md#april-11-2023).
+
+New for this release:
+
+- Azure Arc-enabled SQL Managed Instance
+  - Direct mode for failover groups is generally available az CLI
+
+- Arc PostgreSQL
+  - Ensure postgres extensions work per database/role
+  - Arc PostgreSQL | Upload metrics/logs to Azure Monitor
+
 ## March 14, 2023
 
 ### Image tag
diff --git a/articles/azure-arc/data/sizing-guidance.md b/articles/azure-arc/data/sizing-guidance.md
diff --git a/articles/azure-arc/data/toc.yml b/articles/azure-arc/data/toc.yml
@@ -233,7 +233,11 @@ items:
             - name: Reprovision replica
               href: reprovision-replica.md
         - name: Troubleshoot
-          href: troubleshoot-managed-instance.md
+          items:
+            - name: General
+              href: troubleshoot-managed-instance.md
+            - name: Configuration
+              href: troubleshoot-managed-instance-configuration.md
 - name: Azure Arc-enabled PostgreSQL (preview) 
   items:
     - name: Overview
diff --git a/articles/azure-arc/data/troubleshoot-managed-instance-configuration.md b/articles/azure-arc/data/troubleshoot-managed-instance-configuration.md
@@ -0,0 +1,81 @@
+---
+title: Troubleshoot configuration - Azure Arc-enabled SQL Managed Instance
+description: Describes how to troubleshoot configuration. Includes steps to provide configuration files for Azure Arc-enabled SQL Managed Instance Azure Arc-enabled data services
+author: MikeRayMSFT
+ms.author: mikeray
+ms.topic: troubleshooting-general 
+ms.date: 04/10/2023
+---
+
+# User-provided configuration files
+
+Arc data services provide management of configuration settings and files in the system. The system generates configuration files such as `mssql.conf`, `mssql.json`, `krb5.conf` using the user-provided settings in the custom resource spec and some system-determined settings. The scope of what settings are supported and what changes can be made to the configuration files using the custom resource spec evolves over time. You may need to try changes in the configuration files that aren't possible through the settings on the custom resource spec.
+
+To alleviate this problem, you can provide configuration file content for a selected set of files through a Kubernetes `ConfigMap`. The information in the `ConfigMap` effectively overrides the file content that the system would have otherwise generated. This content allows you to try some configuration settings.
+
+For Arc SQL Managed Instance, the supported configuration files that you can override using this method are:
+
+- `mssql.conf`
+- `mssql.json`
+- `krb5.conf`
+
+## Steps to provide override configuration files
+
+1. Prepare the content of the configuration file
+
+   Prepare the content of the file that you would like to provide an override for.
+
+1. Create a `ConfigMap`
+
+   Create a `ConfigMap` spec to store the content of the configuration file. The key in the `ConfigMap` dictionary should be the name of the file, and the value should be the content.
+
+   You can provide file overrides for multiple configuration files in one `ConfigMap`.
+
+   The `ConfigMap` must be in the same namespace as the SQL Managed Instance.
+
+   The following spec shows an example of how to provide an override for mssql.conf file:
+
+   ```json
+   apiVersion: v1
+   kind: ConfigMap
+   metadata:
+     name: sqlmifo-cm
+     namespace: test
+   data:
+     mssql.conf: "[language]\r\nlcid = 1033\r\n\r\n[licensing]\r\npid = GeneralPurpose\r\n\r\n[network]\r\nforceencryption = 0\r\ntlscert = /var/run/secrets/managed/certificates/mssql/mssql-certificate.pem\r\ntlsciphers = ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES128-SHA256:ECDHE-RSA-AES256-SHA384\r\ntlskey = /var/run/secrets/managed/certificates/mssql/mssql-privatekey.pem\r\ntlsprotocols = 1.2\r\n\r\n[sqlagent]\r\nenabled = False\r\n\r\n[telemetry]\r\ncustomerfeedback = false\r\n\r\n"
+   ```
+
+   Apply the `ConfigMap` in Kubernetes using `kubectl apply -f <filename>`.
+
+1. Provide the name of the ConfigMap in SQL Managed Instance spec
+
+   In SQL Managed Instance spec, provide the name of the ConfigMap in the field `spec.fileOverrideConfigMap`.
+
+   The SQL Managed Instance `apiVersion` must be at least v12 (released in April 2023).
+
+   The following SQL Managed Instance spec shows an example of how to provide the name of the ConfigMap.
+
+   ```json
+   apiVersion: sql.arcdata.microsoft.com/v12
+   kind: SqlManagedInstance
+   metadata:
+     name: sqlmifo
+     namespace: test
+   spec:
+     fileOverrideConfigMap: sqlmifo-cm
+     ...
+   ```
+
+   Apply the SQL Managed Instance spec in Kubernetes. This action leads to the delivery of the provided configuration files to Arc SQL Managed Instance container.
+
+1. Check that the files are downloaded in the `arc-sqlmi` container.
+
+   The locations of supported files in the container are:
+
+   - `mssql.conf`: `/var/run/config/mssql/mssql.conf`
+   - `mssql.json`: `/var/run/config/mssql/mssql.json`
+   - `krb5.conf`: `/etc/krb5.conf`
+
+## Next steps
+
+[Get logs to troubleshoot Azure Arc-enabled data services](troubleshooting-get-logs.md)
diff --git a/articles/azure-arc/data/upload-logs.md b/articles/azure-arc/data/upload-logs.md
@@ -248,7 +248,7 @@ Once your logs are uploaded, you should be able to query them using the log quer
 2. Select Logs in the left panel.
 3. Select Get Started (or select the links on the Getting Started page to learn more about Log Analytics if you are new to it).
 4. Follow the tutorial to learn more about Log Analytics if this is your first time using Log Analytics.
-5. Expand Custom Logs at the bottom of the list of tables and you will see a table called 'sql_instance_logs_CL'.
+5. Expand Custom Logs at the bottom of the list of tables and you will see a table called 'sql_instance_logs_CL' or 'postgresInstances_postgresql_logs_CL'.
 6. Select the 'eye' icon next to the table name.
 7. Select the 'View in query editor' button.
 8. You'll now have a query in the query editor that will show the most recent 10 events in the log.
@@ -258,7 +258,7 @@ Once your logs are uploaded, you should be able to query them using the log quer
 
 If you want to upload metrics and logs on a scheduled basis, you can create a script and run it on a timer every few minutes. Below is an example of automating the uploads using a Linux shell script.
 
-In your favorite text/code editor, add the following script to the file and save as a script executable file - such as .sh for Linux/Mac, or .cmd, .bat, or .ps1 for Windows.
+In your favorite text/code editor, add the following script to the file and save as a script executable file - such as `.sh` (Linux/Mac), `.cmd`, `.bat`, or `.ps1` (Windows).
 
 ```azurecli
 az arcdata dc export --type logs --path logs.json --force --k8s-namespace arc
diff --git a/articles/azure-arc/data/upload-metrics-and-logs-to-azure-monitor.md b/articles/azure-arc/data/upload-metrics-and-logs-to-azure-monitor.md
@@ -16,9 +16,6 @@ ms.topic: how-to
 
 Periodically, you can export out usage information for billing purposes, monitoring metrics, and logs and then upload it to Azure. The export and upload of any of these three types of data will also create and update the data controller, and SQL managed instance resources in Azure.
 
-> [!NOTE]
-> At this time, you can't upload usage data, metrics, or logs for Azure Arc-enabled PostgreSQL server preview.
-
 Before you can upload usage data, metrics, or logs you need to:
 
 * Install tools 
diff --git a/articles/azure-arc/data/upload-metrics.md b/articles/azure-arc/data/upload-metrics.md
@@ -24,7 +24,7 @@ If you have multiple sites that have Azure Arc data services, you can use Azure
 
 ## Upload metrics for Azure Arc data controller in **direct** mode
 
-In the **direct** connected mode, metrics upload can only be setup in **automatic** mode. This automatic upload of metrics can be setup either during deployment of Azure Arc data controller or post deployment.
+In the **direct** connected mode, metrics upload can only be set up in **automatic** mode. This automatic upload of metrics can be set up either during deployment of Azure Arc data controller or post deployment.
 The Arc data services extension managed identity is used for uploading metrics. The managed identity needs to have the **Monitoring Metrics Publisher** role assigned to it. 
 
 > [!NOTE]
@@ -209,11 +209,11 @@ To view your metrics, navigate to the [Azure portal](https://portal.azure.com).
 
 You can view CPU utilization on the Overview page or if you want more detailed metrics you can click on metrics from the left navigation panel
 
-Choose sql server as the metric namespace:
+Choose sql server or postgres as the metric namespace.
 
-Select the metric you want to visualize (you can also select multiple):
+Select the metric you want to visualize (you can also select multiple).
 
-Change the frequency to last 30 minutes:
+Change the frequency to last 30 minutes.
 
 > [!NOTE]
 > You can only upload metrics only for the last 30 minutes. Azure Monitor rejects metrics older than 30 minutes.
@@ -222,7 +222,7 @@ Change the frequency to last 30 minutes:
 
 If you want to upload metrics and logs on a scheduled basis, you can create a script and run it on a timer every few minutes. Below is an example of automating the uploads using a Linux shell script.
 
-In your favorite text/code editor, add the following script to the file and save as a script executable file such as .sh (Linux/Mac) or .cmd, .bat, .ps1.
+In your favorite text/code editor, add the following script to the file and save as a script executable file such as `.sh` (Linux/Mac), `.cmd`, `.bat`, or `.ps1`.
 
 ```azurecli
 az arcdata dc export --type metrics --path metrics.json --force  --k8s-namespace arc
diff --git a/articles/azure-arc/data/using-extensions-in-postgresql-server.md b/articles/azure-arc/data/using-extensions-in-postgresql-server.md
@@ -19,7 +19,7 @@ PostgreSQL is at its best when you use it with extensions.
 [!INCLUDE [azure-arc-data-preview](../../../includes/azure-arc-data-preview.md)]
 
 ## Supported extensions
-For this preview, the following standard [`contrib`](https://www.postgresql.org/docs/14/contrib.html) extensions are already deployed in the containers of your Azure Arc-enabled PostgreSQL server:
+The following extensions are deployed by default in the containers of your Azure Arc-enabled PostgreSQL server, some of them are standard [`contrib`](https://www.postgresql.org/docs/14/contrib.html) extensions:
 - `address_standardizer_data_us` 3.3.1
 - `adminpack` 2.1
 - `amcheck` 1.3
@@ -82,16 +82,24 @@ For this preview, the following standard [`contrib`](https://www.postgresql.org/
 
 Updates to this list will be posted as it evolves over time.
 
-## Create an Arc-enabled PostgreSQL server with extensions enabled
-You can create an Arc-enabled PostgreSQL server with any of the supported extensions enabled by passing a comma separated list of extensions to the `--extensions` parameter of the `create` command. *NOTE:* Extensions are enabled on the database for the admin user that was supplied when the server was created:
+## Enable extensions in Arc-enabled PostgreSQL server
+You can create an Arc-enabled PostgreSQL server with any of the supported extensions enabled by passing a comma separated list of extensions to the `--extensions` parameter of the `create` command. 
+
 ```azurecli
 az postgres server-arc create -n <name> --k8s-namespace <namespace> --extensions "pgaudit,pg_partman" --use-k8s
 ```
+*NOTE*: Enabled extensions are added to the configuration ``shared_preload_libraries``. Extensions must be installed in your database before you can use it. To install a particular extension, you should run the [`CREATE EXTENSION`](https://www.postgresql.org/docs/current/sql-createextension.html) command. This command loads the packaged objects into your database.
+
+For example, connect to your database and issue the following PostgreSQL command to install pgaudit extension:
+
+```SQL
+CREATE EXTENSION pgaudit;
+```
 
-## Add or remove extensions
+## Update extensions
 You can add or remove extensions from an existing Arc-enabled PostgreSQL server.
 
-First describe the server to get the current list of extensions:
+You can run the kubectl describe command to get the current list of enabled extensions:
 ```console
 kubectl describe postgresqls <server-name> -n <namespace>
 ```
@@ -100,14 +108,33 @@ If there are extensions enabled the output contains a section like this:
   config:
     postgreSqlExtensions: pgaudit,pg_partman
 ```
-Add new extensions by appending them to the existing list, or remove extensions by removing them from the existing list. Pass the desired list to the update command. For example, to add `pgcrypto` and remove `pg_partman` from the server in the example above:
+
+Check whether the extension is installed after connecting to the database by running following PostgreSQL command:
+```SQL
+select * from pg_extension;
+```
+
+Enable new extensions by appending them to the existing list, or remove extensions by removing them from the existing list. Pass the desired list to the update command. For example, to add `pgcrypto` and remove `pg_partman` from the server in the example above:
+
 ```azurecli
 az postgres server-arc update -n <name> --k8s-namespace <namespace> --extensions "pgaudit,pgrypto" --use-k8s
 ```
 
-## Show the list of enabled extensions
-Connect to your server with the client tool of your choice and run the standard PostgreSQL query:
-```console
+Once allowed extensions list is updated. Connect to the database and install newly added extension by the following command:
+
+```SQL
+CREATE EXTENSION pgcrypto;
+```
+
+Similarly, to remove an extension from an existing database issue the command [`DROP EXTENSION`](https://www.postgresql.org/docs/current/sql-dropextension.html) :
+
+```SQL
+DROP EXTENSION pg_partman;
+```
+
+## Show the list of installed extensions
+Connect to your database with the client tool of your choice and run the standard PostgreSQL query:
+```SQL
 select * from pg_extension;
 ```
 
diff --git a/articles/azure-arc/data/version-log.md b/articles/azure-arc/data/version-log.md
@@ -17,6 +17,32 @@ ms.topic: conceptual
 
 This article identifies the component versions with each release of Azure Arc-enabled data services.
 
+## April 11, 2023
+
+|Component|Value|
+|-----------|-----------|
+|Container images tag |`v1.18.0_2023-04-11`|
+|**CRD names and version:**| |
+|`activedirectoryconnectors.arcdata.microsoft.com`| v1beta1, v1beta2, v1|
+|`datacontrollers.arcdata.microsoft.com`| v1beta1, v1 through v5|
+|`exporttasks.tasks.arcdata.microsoft.com`| v1beta1, v1, v2|
+|`failovergroups.sql.arcdata.microsoft.com`| v1beta1, v1beta2, v1, v2|
+|`kafkas.arcdata.microsoft.com`| v1beta1 through v1beta4|
+|`monitors.arcdata.microsoft.com`| v1beta1, v1, v2|
+|`postgresqls.arcdata.microsoft.com`| v1beta1 through v1beta6|
+|`postgresqlrestoretasks.tasks.postgresql.arcdata.microsoft.com`| v1beta1|
+|`sqlmanagedinstances.sql.arcdata.microsoft.com`| v1beta1, v1 through v12|
+|`sqlmanagedinstancemonitoringprofiles.arcdata.microsoft.com`| v1beta1, v1beta2|
+|`sqlmanagedinstancereprovisionreplicatasks.tasks.sql.arcdata.microsoft.com`| v1beta1|
+|`sqlmanagedinstancerestoretasks.tasks.sql.arcdata.microsoft.com`| v1beta1, v1|
+|`telemetrycollectors.arcdata.microsoft.com`| v1beta1 through v1beta5|
+|`telemetryrouters.arcdata.microsoft.com`| v1beta1 through v1beta5|
+|`redis.arcdata.microsoft.com`| v1beta1|
+|Azure Resource Manager (ARM) API version|2023-01-15-preview|
+|`arcdata` Azure CLI extension version|1.4.13 ([Download](https://aka.ms/az-cli-arcdata-ext))|
+|Arc-enabled Kubernetes helm chart extension version|1.18.0|
+|Azure Arc Extension for Azure Data Studio<br/>`arc`<br/>`azcli`|<br/>1.8.0 ([Download](https://aka.ms/ads-arcdata-ext))</br>1.8.0 ([Download](https://aka.ms/ads-azcli-ext))|
+
 ## March 14, 2023
 
 |Component|Value|
