You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: extensions/azure-stack-edge/README.md
+50-9Lines changed: 50 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,29 +8,70 @@ Prerequisites:
8
8
* You have access to a [fully functional ASE with internet access and allocated sufficient IP address space for k8s services](https://docs.microsoft.com/en-us/azure/databox-online/azure-stack-edge-gpu-deploy-configure-network-compute-web-proxy#enable-compute-network) exopsed on your local network.
9
9
*[Create a new user and namespace with proper RBAC on ASE k8s](https://docs.microsoft.com/en-us/azure/databox-online/azure-stack-edge-gpu-create-kubernetes-cluster).
10
10
*[Enable edge container registry on ASE](https://docs.microsoft.com/en-us/azure/databox-online/azure-stack-edge-gpu-edge-container-registry).
11
-
* Install Helm3 on your build agent.
11
+
*[Install latest stable Helm](https://helm.sh/docs/intro/install/) on your build agent.
12
+
* Your build agent should have network connectivity to reach the k8s cluster on ASE.
12
13
***Optional**: You can [create a VM on ASE](https://docs.microsoft.com/en-us/azure/databox-online/azure-stack-edge-gpu-deploy-virtual-machine-portal) and use it as the ADO agent for building and deploying the Claims API.
13
14
14
15
Steps:
15
-
1. Create a new branch (e.g. "ase-test") on GitHub.
16
-
2. Checkout the new branch.
16
+
1.[Create a new branch](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository) (e.g. "ase-test") on GitHub.
17
+
2.[Checkout](https://git-scm.com/book/en/v2/Git-Branching-Basic-Branching-and-Merging) the new branch.
17
18
3. Rename your existing claims-api directory to **aks-aspnet-sqldb-rest/claims-api.orig**.
18
19
4. Copy **aks-aspnet-sqldb-rest/extensions/azure-stack-edge/claims-api** to **aks-aspnet-sqldb-rest/claims-api**.
19
-
5. Make necessary changes under "imageCredentials" in **values.yaml**.
20
+
5. Make necessary changes (registry url, username, password, email) under "imageCredentials" in **values.yaml**.
20
21
6. Commit and push changes to new branch.
21
-
7. Go to the ADO project and update the build pipeline using new branch (instead of master).
22
-
8. Create a new container registry service connection for your edge container registry and update the build pipeline (e.g. "https://ecr.dbe-70c9r53.microsoftdatabox.com:31001/").
23
-
9. Create a new Kubernetes service connection using the kubeconfig file for the user who's grant access to the namespace for deployment.
22
+
7. Go to the ADO project and update the build pipeline using your new branch (instead of master):
8. Create a new container registry service connection for your edge container registry and update the build pipeline (e.g. "https://ecr.dbe-70c9r53.microsoftdatabox.com:31001/"):
* Since we are using the edge container registry instead of ACR, we will need to create imagePullSecret on k8s to store the credentials. This is handled by helm 3 charts.
49
+
* Since we are using the edge container registry (ECR) instead of ACR, we will need to create imagePullSecret on k8s to store the ECR credential "**regcred**", see below:
50
+
```bash
51
+
azureuser@Ubuntu1804:~$ kubectl get secrets -n claims-api-dev
0 commit comments