Merge pull request #109867 from zr-msft/zr-aks-1703061-rm-osba

[AKS] remove OSBA docs and add redirects

Author: megvanhuygen

.openpublishing.redirection.json

@@ -50523,6 +50523,16 @@
     {
       "source_path": "articles/sql-database/sql-database-managed-instance-index.yml",
       "redirect_url": "/azure/sql-database/sql-database-managed-instance"
+    },
+    {
+      "source_path": "articles/aks/integrate-azure.md",
+      "redirect_url": "/azure/aks/",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/aks/use-cosmosdb-osba-mongo-app.md",
+      "redirect_url": "/azure/aks/",
+      "redirect_document_id": false
     }
   ]
 }

articles/aks/TOC.yml

@@ -314,10 +314,6 @@
           maintainContext: true
     - name: Run applications with Helm
       href: kubernetes-helm.md
-    - name: Use Open Service Broker for Azure
-      href: integrate-azure.md
-    - name: Use Cosmos DB API for MongoDB with OSBA
-      href: use-cosmosdb-osba-mongo-app.md
     - name: Use OpenFaaS
       href: openfaas.md
     - name: Run Spark jobs

articles/aks/certificate-rotation.md

@@ -27,7 +27,7 @@ AKS generates and uses the following certificates, Certificate Authorities, and
 * Each kubelet also creates a Certificate Signing Request (CSR), which is signed by the Cluster CA, for communication from the kubelet to the API server.
 * The etcd key value store has a certificate signed by the Cluster CA for communication from etcd to the API server.
 * The etcd key value store creates a CA that signs certificates to authenticate and authorize data replication between etcd replicas in the AKS cluster.
-* The API aggregator uses the Cluster CA to issue certificates for communication with other APIs, such as Open Service Broker for Azure. The API aggregator can also have its own CA for issuing those certificates, but it currently uses the Cluster CA.
+* The API aggregator uses the Cluster CA to issue certificates for communication with other APIs. The API aggregator can also have its own CA for issuing those certificates, but it currently uses the Cluster CA.
 * Each node uses a Service Account (SA) token, which is signed by the Cluster CA.
 * The `kubectl` client has a certificate for communicating with the AKS cluster.