Merge pull request #273489 from MicrosoftDocs/main

4/26 11:00 AM IST Publish

Author: Saisang

.openpublishing.publish.config.json

@@ -356,6 +356,12 @@
       "branch": "main",
       "branch_mapping": {}
     },
+    {
+      "path_to_root": "azure-functions-python-worker",
+      "url": "https://github.com/Azure/azure-functions-python-worker",
+      "branch": "dev",
+      "branch_mapping": {}
+    },    
     {
       "path_to_root": "functions-openapi-turbine-repair",
       "url": "https://github.com/Azure-Samples/functions-openapi-turbine-repair",

articles/azure-arc/kubernetes/extensions-release.md

@@ -1,6 +1,6 @@
 ---
 title: "Available extensions for Azure Arc-enabled Kubernetes clusters"
-ms.date: 03/22/2024
+ms.date: 04/25/2024
 ms.topic: how-to
 description: "See which extensions are currently available for Azure Arc-enabled Kubernetes clusters and view release notes."
 ---
@@ -121,11 +121,11 @@ The most recent version of the Flux v2 extension and the two previous versions (
 > [!NOTE]
 > When a new version of the `microsoft.flux` extension is released, it may take several days for the new version to become available in all regions.
 
-### 1.8.3 (March 2024)
+### 1.8.4 (March 2024)
 
 Flux version: [Release v2.1.2](https://github.com/fluxcd/flux2/releases/tag/v2.1.2)
 
-- source-controller: v1.1.2
+- source-controller: v1.2.5
 - kustomize-controller: v1.1.1
 - helm-controller: v0.36.2
 - notification-controller: v1.1.0
@@ -134,9 +134,9 @@ Flux version: [Release v2.1.2](https://github.com/fluxcd/flux2/releases/tag/v2.1
 
 Changes made for this version:
 
-- The log-level parameters for controllers are now customizable. For more information, see [Configurable log-level parameters](tutorial-use-gitops-flux2.md#configurable-log-level-parameters).
+- Updated source-controller to v1.2.5
 
-### 1.8.2 (February 2024)
+### 1.8.3 (March 2024)
 
 Flux version: [Release v2.1.2](https://github.com/fluxcd/flux2/releases/tag/v2.1.2)
 
@@ -149,9 +149,9 @@ Flux version: [Release v2.1.2](https://github.com/fluxcd/flux2/releases/tag/v2.1
 
 Changes made for this version:
 
-- Improve the identity token generation logic to handle token generation failures
+- The log-level parameters for controllers are now customizable. For more information, see [Configurable log-level parameters](tutorial-use-gitops-flux2.md#configurable-log-level-parameters).
 
-### 1.8.1 (November 2023)
+### 1.8.2 (February 2024)
 
 Flux version: [Release v2.1.2](https://github.com/fluxcd/flux2/releases/tag/v2.1.2)
 
@@ -164,8 +164,7 @@ Flux version: [Release v2.1.2](https://github.com/fluxcd/flux2/releases/tag/v2.1
 
 Changes made for this version:
 
-- Upgrades Flux to [v2.1.2](https://github.com/fluxcd/flux2/releases/tag/v2.1.2)
-- Updates to each `fluxConfiguration` status are now relayed back to Azure once every minute, provided there are any changes to report
+- Improve the identity token generation logic to handle token generation failures
 
 ## Dapr extension for Azure Kubernetes Service (AKS) and Arc-enabled Kubernetes
 

articles/azure-arc/kubernetes/workload-management.md

@@ -270,31 +270,31 @@ However, only the `drone` and `large` cluster types were selected by the schedul
 
 ### Understand deployment target assignment manifests
 
-Before you continue, take a closer look at the generated assignment manifests for the `functional-test` deployment target. There are `namespace.yaml`, `config.yaml` and `reconciler.yaml` manifest files.
+Before you continue, take a closer look at the generated assignment manifests for the `functional-test` deployment target. There are `namespace.yaml`, `platform-config.yaml` and `reconciler.yaml` manifest files.
 
 `namespace.yaml` defines a namespace that will be created on any `drone` cluster where the `hello-world` application runs.
  
 ```yaml
 apiVersion: v1
 kind: Namespace
 metadata:
+  name: "dev-drone-hello-world-app-functional-test" 
   labels:
-    deploymentTarget: hello-world-app-functional-test
-    environment: dev
+    environment: "dev"
+    workspace: "kaizen-app-team"
+    workload: "hello-world-app"
+    deploymentTarget: "hello-world-app-functional-test"
     someLabel: some-value
-    workload: hello-world-app
-    workspace: kaizen-app-team
-  name: dev-kaizen-app-team-hello-world-app-functional-test
 ```
 
-`config.yaml` contains all platform configuration values available on any `drone` cluster that the application can use in the `Dev` environment.
+`platform-config.yaml` contains all platform configuration values available on any `drone` cluster that the application can use in the `Dev` environment.
  
 ```yaml
 apiVersion: v1
 kind: ConfigMap
 metadata:
   name: platform-config
-  namespace: dev-kaizen-app-team-hello-world-app-functional-test
+  namespace: dev-drone-hello-world-app-functional-test
 data:
   CLUSTER_NAME: Drone
   DATABASE_URL: mysql://restricted-host:3306/mysqlrty123
@@ -309,29 +309,29 @@ data:
 apiVersion: source.toolkit.fluxcd.io/v1beta2
 kind: GitRepository
 metadata:
-  name: hello-world-app-functional-test
+  name: "hello-world-app-functional-test"
   namespace: flux-system
 spec:
-  interval: 30s
+  interval: 15s
+  url: "https://github.com/eedorenko/kalypso-tut-test-app-gitops"
   ref:
-    branch: dev
+    branch: "dev"
   secretRef:
-    name: repo-secret
-  url: https://github.com/<GitHub org>/<prefix>-app-gitops
+      name: repo-secret    
 ---
 apiVersion: kustomize.toolkit.fluxcd.io/v1beta2
 kind: Kustomization
 metadata:
-  name: hello-world-app-functional-test
+  name: "hello-world-app-functional-test"
   namespace: flux-system
 spec:
   interval: 30s
-  path: ./functional-test
-  prune: true
+  targetNamespace: "dev-drone-hello-world-app-functional-test"
   sourceRef:
     kind: GitRepository
-    name: hello-world-app-functional-test
-  targetNamespace: dev-kaizen-app-team-hello-world-app-functional-test
+    name: "hello-world-app-functional-test"
+  path: "./functional-test" 
+  prune: true
 ```
 
 > [!NOTE]
@@ -419,7 +419,7 @@ The generated manifests are added to a pull request to the `stage` branch waitin
 To test the application manually on the `Dev` environment before approving the PR to the `Stage` environment, first verify how the `functional-test` application instance works on the `drone` cluster:
 
 ```bash
-kubectl port-forward svc/hello-world-service -n dev-kaizen-app-team-hello-world-app-functional-test 9090:9090 --context=drone
+kubectl port-forward svc/hello-world-service -n dev-drone-hello-world-app-functional-test 9090:9090 --context=drone
 
 # output:
 # Forwarding from 127.0.0.1:9090 -> 9090
@@ -434,7 +434,7 @@ While this command is running, open `localhost:9090` in your browser. You'll see
 The next step is to check how the `performance-test` instance works on the `large` cluster:
 
 ```bash
-kubectl port-forward svc/hello-world-service -n dev-kaizen-app-team-hello-world-app-performance-test 8080:8080 --context=large
+kubectl port-forward svc/hello-world-service -n dev-large-hello-world-app-performance-test 8080:8080 --context=large
 
 # output:
 # Forwarding from 127.0.0.1:8080 -> 8080
@@ -449,13 +449,13 @@ Once you're satisfied with the `Dev` environment, approve and merge the PR to th
 Run the following command for the `drone` cluster and open `localhost:8001` in your browser:
  
 ```bash
-kubectl port-forward svc/hello-world-service -n stage-kaizen-app-team-hello-world-app-uat-test 8001:8000 --context=drone
+kubectl port-forward svc/hello-world-service -n stage-drone-hello-world-app-uat-test 8001:8000 --context=drone
 ```
 
 Run the following command for the `large` cluster and open `localhost:8002` in your browser:
 
 ```bash
-kubectl port-forward svc/hello-world-service -n stage-kaizen-app-team-hello-world-app-uat-test 8002:8000 --context=large
+kubectl port-forward svc/hello-world-service -n stage-large-hello-world-app-uat-test 8002:8000 --context=large
 ```
 
 The application instance on the `large` cluster shows the following greeting page:
@@ -503,8 +503,8 @@ Once the new configuration has arrived to the `large` cluster, check the `uat-te
 running the following commands:
 
 ```bash
-kubectl rollout restart deployment hello-world-deployment -n stage-kaizen-app-team-hello-world-app-uat-test --context=large
-kubectl port-forward svc/hello-world-service -n stage-kaizen-app-team-hello-world-app-uat-test 8002:8000 --context=large
+kubectl rollout restart deployment hello-world-deployment -n stage-large-hello-world-app-uat-test --context=large
+kubectl port-forward svc/hello-world-service -n stage-large-hello-world-app-uat-test 8002:8000 --context=large
 ```
 
 You'll see the updated database url:
@@ -532,6 +532,7 @@ metadata:
 spec:
   reconciler: arc-flux
   namespaceService: default
+  configType: configmap
 EOF
 
 git add .

articles/azure-cache-for-redis/cache-overview-vector-similarity.md

@@ -16,13 +16,15 @@ For a tutorial on how to use Azure Cache for Redis and Azure OpenAI to perform v
 
 ## Scope of Availability
 
-This table contains the information for TLS availability in different tiers.
+Vector search capabilities in Redis require [Redis Stack](https://redis.io/docs/latest/operate/oss_and_stack/stack-with-enterprise/), specifically the [RediSearch](https://redis.io/docs/interact/search-and-query/) module. This capability is only available in the [Enterprise tiers of Azure Cache for Redis](./cache-redis-modules.md).
+
+This table contains the information for vector search availability in different tiers.
 
 |Tier      | Basic / Standard  | Premium  |Enterprise | Enterprise Flash  |
 |--------- |:------------------:|:----------:|:---------:|:---------:|
 |Available | No          | No       |  Yes  | Yes (preview) |
 
-Vector search capabilities in Redis require [Redis Stack](https://redis.io/docs/latest/operate/oss_and_stack/stack-with-enterprise/), specifically the [RediSearch](https://redis.io/docs/interact/search-and-query/) module. This capability is only available in the [Enterprise tiers of Azure Cache for Redis](./cache-redis-modules.md).
+
 
 ## What are vector embeddings?