Deployed fbefcca with MkDocs version: 1.1.2

Azure · Sep 13, 2024 · 6ce7d16 · 6ce7d16
1 parent 398bf40
commit 6ce7d16
Show file tree

Hide file tree

Showing 6 changed files with 27 additions and 73 deletions.
diff --git a/how-tos/deploy-AGIC-with-Workload-Identity-using-helm/index.html b/how-tos/deploy-AGIC-with-Workload-Identity-using-helm/index.html
@@ -102,27 +102,25 @@
                     </li>
                     <li class="toctree-l1 current"><a class="reference internal current" href="./">How to deploy AGIC via Helm using Workload Identity</a>
     <ul class="current">
-    <li class="toctree-l2"><a class="reference internal" href="#1-add-the-agic-helm-repository">1. Add the AGIC Helm repository</a>
+    <li class="toctree-l2"><a class="reference internal" href="#1-set-environment-variables">1. Set environment variables</a>
     </li>
-    <li class="toctree-l2"><a class="reference internal" href="#2-set-environment-variables">2. Set environment variables</a>
+    <li class="toctree-l2"><a class="reference internal" href="#2-create-resource-group-aks-cluster-and-identity">2. Create resource group, AKS cluster and identity</a>
     </li>
-    <li class="toctree-l2"><a class="reference internal" href="#3-create-resource-group-aks-cluster-and-identity">3. Create resource group, AKS cluster and identity</a>
+    <li class="toctree-l2"><a class="reference internal" href="#3-export-the-oidcissuerprofileissuerurl">3. Export the oidcIssuerProfile.issuerUrl</a>
     </li>
-    <li class="toctree-l2"><a class="reference internal" href="#4-export-the-oidcissuerprofileissuerurl">4. Export the oidcIssuerProfile.issuerUrl</a>
+    <li class="toctree-l2"><a class="reference internal" href="#4-create-federated-identity-credential">4. Create federated identity credential</a>
     </li>
-    <li class="toctree-l2"><a class="reference internal" href="#5-create-federated-identity-credential">5. Create federated identity credential</a>
+    <li class="toctree-l2"><a class="reference internal" href="#5-obtain-the-clientid-of-the-identity-created-before-that-is-needed-for-the-next-step">5. Obtain the ClientID of the identity created before that is needed for the next step</a>
     </li>
-    <li class="toctree-l2"><a class="reference internal" href="#6-obtain-the-clientid-of-the-identity-created-before-that-is-needed-for-the-next-step">6. Obtain the ClientID of the identity created before that is needed for the next step</a>
+    <li class="toctree-l2"><a class="reference internal" href="#6-export-the-application-gateway-resource-id">6. Export the Application Gateway resource ID</a>
     </li>
-    <li class="toctree-l2"><a class="reference internal" href="#7-export-the-application-gateway-resource-id">7. Export the Application Gateway resource ID</a>
+    <li class="toctree-l2"><a class="reference internal" href="#7-add-contributor-role-for-the-identity-over-the-application-gateway">7. Add Contributor role for the identity over the Application Gateway</a>
     </li>
-    <li class="toctree-l2"><a class="reference internal" href="#8-add-contributor-role-for-the-identity-over-the-application-gateway">8. Add Contributor role for the identity over the Application Gateway</a>
+    <li class="toctree-l2"><a class="reference internal" href="#8-in-helm-configyaml-specify">8. In helm-config.yaml specify</a>
     </li>
-    <li class="toctree-l2"><a class="reference internal" href="#9-in-helm-configyaml-specify">9. In helm-config.yaml specify</a>
+    <li class="toctree-l2"><a class="reference internal" href="#9-get-the-aks-cluster-credentials">9. Get the AKS cluster credentials</a>
     </li>
-    <li class="toctree-l2"><a class="reference internal" href="#10get-the-aks-cluster-credentials">10.Get the AKS cluster credentials</a>
-    </li>
-    <li class="toctree-l2"><a class="reference internal" href="#11-install-the-helm-chart">11. Install the helm chart</a>
+    <li class="toctree-l2"><a class="reference internal" href="#10-install-the-helm-chart">10. Install the helm chart</a>
     </li>
     </ul>
                     </li>
@@ -224,46 +222,42 @@ <h1 id="how-to-deploy-agic-via-helm-using-workload-identity">How to deploy AGIC
 <p>This assumes you have an existing Application Gateway. If not, you can create it with command:</p>
 <p><code>bash
 az network application-gateway create -g myResourceGroup -n myApplicationGateway --sku Standard_v2 --public-ip-address myPublicIP --vnet-name myVnet --subnet mySubnet --priority 100</code></p>
-<h2 id="1-add-the-agic-helm-repository">1. Add the AGIC Helm repository</h2>
-<p><code>bash
-helm repo add application-gateway-kubernetes-ingress https://appgwingress.blob.core.windows.net/ingress-azure-helm-package/
-helm repo update</code></p>
-<h2 id="2-set-environment-variables">2. Set environment variables</h2>
+<h2 id="1-set-environment-variables">1. Set environment variables</h2>
 <p><code>bash
 export RESOURCE_GROUP="myResourceGroup"
 export APPLICATION_GATEWAY_NAME="myApplicationGateway"
 export USER_ASSIGNED_IDENTITY_NAME="myIdentity"
 export FEDERATED_IDENTITY_CREDENTIAL_NAME="myFedIdentity"</code></p>
-<h2 id="3-create-resource-group-aks-cluster-and-identity">3. Create resource group, AKS cluster and identity</h2>
+<h2 id="2-create-resource-group-aks-cluster-and-identity">2. Create resource group, AKS cluster and identity</h2>
 <p><code>bash
 az group create --name "${RESOURCE_GROUP}"  --location eastus
 az aks create -g "${RESOURCE_GROUP}" -n myAKSCluster --node-count 1 --enable-oidc-issuer --enable-workload-identity 
 az identity create --name "${USER_ASSIGNED_IDENTITY_NAME}" --resource-group "${RESOURCE_GROUP}"</code></p>
-<h2 id="4-export-the-oidcissuerprofileissuerurl">4. Export the oidcIssuerProfile.issuerUrl</h2>
+<h2 id="3-export-the-oidcissuerprofileissuerurl">3. Export the oidcIssuerProfile.issuerUrl</h2>
 <p><code>bash
 export AKS_OIDC_ISSUER="$(az aks show -n myAKSCluster -g "${RESOURCE_GROUP}" --query "oidcIssuerProfile.issuerUrl" -otsv)"</code></p>
-<h2 id="5-create-federated-identity-credential">5. Create federated identity credential</h2>
+<h2 id="4-create-federated-identity-credential">4. Create federated identity credential</h2>
 <p><strong>Note</strong>: the name of the service account that gets created after the helm installation is “ingress-azure” and the following command assumes it will be deployed in “default” namespace. Please change the namespace name in the next command if you deploy the AGIC related Kubernetes resources in other namespace.</p>
 <p><code>bash
 az identity federated-credential create --name ${FEDERATED_IDENTITY_CREDENTIAL_NAME} --identity-name ${USER_ASSIGNED_IDENTITY_NAME} --resource-group ${RESOURCE_GROUP} --issuer ${AKS_OIDC_ISSUER} --subject system:serviceaccount:default:ingress-azure</code></p>
-<h2 id="6-obtain-the-clientid-of-the-identity-created-before-that-is-needed-for-the-next-step">6. Obtain the ClientID of the identity created before that is needed for the next step</h2>
+<h2 id="5-obtain-the-clientid-of-the-identity-created-before-that-is-needed-for-the-next-step">5. Obtain the ClientID of the identity created before that is needed for the next step</h2>
 <p><code>bash
 az identity show --resource-group "${RESOURCE_GROUP}" --name "${USER_ASSIGNED_IDENTITY_NAME}" --query 'clientId' -otsv</code></p>
-<h2 id="7-export-the-application-gateway-resource-id">7. Export the Application Gateway resource ID</h2>
+<h2 id="6-export-the-application-gateway-resource-id">6. Export the Application Gateway resource ID</h2>
 <p><code>bash
 export APP_GW_ID="$(az network application-gateway show --name "${APPLICATION_GATEWAY_NAME}"  --resource-group "${RESOURCE_GROUP}"  --query 'id' --output tsv)"</code></p>
-<h2 id="8-add-contributor-role-for-the-identity-over-the-application-gateway">8. Add Contributor role for the identity over the Application Gateway</h2>
+<h2 id="7-add-contributor-role-for-the-identity-over-the-application-gateway">7. Add Contributor role for the identity over the Application Gateway</h2>
 <p><code>bash
 az role assignment create --assignee &lt;identityClientID&gt; --scope "${APP_GW_ID}" --role Contributor</code></p>
-<h2 id="9-in-helm-configyaml-specify">9. In helm-config.yaml specify</h2>
+<h2 id="8-in-helm-configyaml-specify">8. In helm-config.yaml specify</h2>
 <p><code>yaml
 armAuth:
     type: workloadIdentity
     identityClientID: &lt;identityClientID&gt;</code></p>
-<h2 id="10get-the-aks-cluster-credentials">10.Get the AKS cluster credentials</h2>
+<h2 id="9-get-the-aks-cluster-credentials">9. Get the AKS cluster credentials</h2>
 <p><code>bash
 az aks get-credentials -g "${RESOURCE_GROUP}" -n myAKSCluster</code></p>
-<h2 id="11-install-the-helm-chart">11. Install the helm chart</h2>
+<h2 id="10-install-the-helm-chart">10. Install the helm chart</h2>
 <p><code>bash
 helm install ingress-azure \
   -f helm-config.yaml \

diff --git a/how-tos/helm-upgrade/index.html b/how-tos/helm-upgrade/index.html
@@ -204,42 +204,10 @@ <h1 id="upgrading-agic-using-helm">Upgrading AGIC using Helm</h1>
 <p><strong><em>NOTE:</em></strong> <a href="https://aka.ms/agc">Application Gateway for Containers</a> has been released, which introduces numerous performance, resilience, and feature changes. Please consider leveraging Application Gateway for Containers for your next deployment.</p>
 </blockquote>
 <p>The Azure Application Gateway Ingress Controller for Kubernetes (AGIC) can be upgraded
-using a Helm repository hosted on Azure Storage.</p>
-<p>Before we begin the upgrade procedure, ensure that you have added the required repository:</p>
-<ul>
-<li>
-<p>View your currently added Helm repositories with:</p>
-<p><code>bash
-helm repo list</code></p>
-</li>
-<li>
-<p>Add the AGIC repo with:</p>
-<p><code>bash
-helm repo add \
-    application-gateway-kubernetes-ingress \
-    https://appgwingress.blob.core.windows.net/ingress-azure-helm-package/</code></p>
-</li>
-</ul>
+using a Helm repository hosted on MCR.</p>
 <h2 id="upgrade">Upgrade</h2>
 <ol>
 <li>
-<p>Refresh the AGIC Helm repository to get the latest release:</p>
-<p><code>bash
-helm repo update</code></p>
-</li>
-<li>
-<p>View available versions of the <code>application-gateway-kubernetes-ingress</code> chart:</p>
-<p><code>bash
-helm search repo -l application-gateway-kubernetes-ingress</code></p>
-<p>Sample response:</p>
-<p><code>bash
-NAME                                                    CHART VERSION   APP VERSION     DESCRIPTION
-application-gateway-kubernetes-ingress/ingress-azure    1.0.0           1.0.0           Use Azure Application Gateway as the ingress for an Azure...
-application-gateway-kubernetes-ingress/ingress-azure    0.7.0-rc1       0.7.0-rc1       Use Azure Application Gateway as the ingress for an Azure...
-application-gateway-kubernetes-ingress/ingress-azure    0.6.0           0.6.0           Use Azure Application Gateway as the ingress for an Azure...</code></p>
-<p>Latest available version from the list above is: <code>0.7.0-rc1</code></p>
-</li>
-<li>
 <p>View the Helm charts currently installed:</p>
 <p><code>bash
 helm list</code></p>

diff --git a/index.html b/index.html
@@ -263,5 +263,5 @@ <h2 id="reporting-issues">Reporting Issues</h2>
 
 <!--
 MkDocs version : 1.1.2
-Build Date UTC : 2024-09-13 18:32:51.957615+00:00
+Build Date UTC : 2024-09-13 18:38:12.628609+00:00
 -->
diff --git a/search/search_index.json b/search/search_index.json
diff --git a/setup/install/index.html b/setup/install/index.html
@@ -245,7 +245,7 @@ <h1 id="register-required-resource-providers-on-azure">Register required resourc
 </li>
 <li>
 <p>Install Helm</p>
-<p><a href="https://github.com/helm/helm">Helm</a> is an open-source packaging tool that is used to install ALB controller.</p>
+<p><a href="https://github.com/helm/helm">Helm</a> is an open-source packaging tool that is used to install AGIC.</p>
 <blockquote>
 <p>Helm is already available in Azure Cloud Shell.  If you are using Azure Cloud Shell, no additional Helm installation is necessary.</p>
 </blockquote>
@@ -335,9 +335,9 @@ <h2 id="install-application-gateway-ingress-controller">Install Application Gate
 sleep 60</p>
 <p>echo "Set up federation with AKS OIDC issuer"
 AKS_OIDC_ISSUER="<span class="arithmatex"><span class="MathJax_Preview">(az aks show -n "</span><script type="math/tex">(az aks show -n "</script></span>AKS_NAME" -g "<span class="arithmatex"><span class="MathJax_Preview">RESOURCE_GROUP" --query "oidcIssuerProfile.issuerUrl" -o tsv)"
-az identity federated-credential create --name "azure-alb-identity" \
+az identity federated-credential create --name "agic" \
     --identity-name "</span><script type="math/tex">RESOURCE_GROUP" --query "oidcIssuerProfile.issuerUrl" -o tsv)"
-az identity federated-credential create --name "azure-alb-identity" \
+az identity federated-credential create --name "agic" \
     --identity-name "</script></span>IDENTITY_RESOURCE_NAME" \
     --resource-group <span class="arithmatex"><span class="MathJax_Preview">RESOURCE_GROUP \
     --issuer "</span><script type="math/tex">RESOURCE_GROUP \
@@ -359,15 +359,7 @@ <h2 id="install-application-gateway-ingress-controller">Install Application Gate
 <p>Assignment of the managed identity immediately after creation may result in an error that the principalId does not exist. Allow about a minute of time to elapse for the identity to replicate in Microsoft Entra ID prior to delegating the identity.</p>
 </blockquote>
 <ol>
-<li>
-<p>Add the AGIC Helm repository:</p>
-<p><code>bash
-helm repo add application-gateway-kubernetes-ingress https://appgwingress.blob.core.windows.net/ingress-azure-helm-package/
-helm repo update</code></p>
-</li>
-<li>
-<p>Install ALB Controller using Helm</p>
-</li>
+<li>Install AGIC using Helm</li>
 </ol>
 <h3 id="for-new-deployments">For new deployments</h3>
 <p>AGIC can be installed by running the following commands:</p>

diff --git a/sitemap.xml.gz b/sitemap.xml.gz