Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit 2b17f81

Browse files
authored
Merge pull request #13 from rickijen/apim-on-ase
Deploy APIM Gateway on ASE and import Claims API
2 parents 62ed972 + d2d5d2c commit 2b17f81

File tree

3 files changed

+20
-4
lines changed

3 files changed

+20
-4
lines changed

‎extensions/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,4 +19,4 @@ The extensions below explore advanced features of AKS (Kubernetes) and additiona
1919

2020
- [Deploy Claims API to **Azure Stack Edge**](./azure-stack-edge)
2121

22-
In this sub-project, we will deploy the same Claims Web API to the [Kubernetes cluster on Azure Stack Edge (ASE)](https://docs.microsoft.com/en-us/azure/databox-online/azure-stack-edge-gpu-kubernetes-overview). The container is built on a Ubuntu [virtual machine on ASE](https://docs.microsoft.com/en-us/azure/databox-online/azure-stack-edge-gpu-deploy-virtual-machine-portal) and pushed to the private [edge container registry on ASE](https://docs.microsoft.com/en-us/azure/databox-online/azure-stack-edge-gpu-edge-container-registry).
22+
In this sub-project, we will deploy the same Claims Web API to the [Kubernetes cluster on Azure Stack Edge (ASE)](https://docs.microsoft.com/en-us/azure/databox-online/azure-stack-edge-gpu-kubernetes-overview). The container is built on a Ubuntu [virtual machine on ASE](https://docs.microsoft.com/en-us/azure/databox-online/azure-stack-edge-gpu-deploy-virtual-machine-portal) and pushed to the private [edge container registry on ASE](https://docs.microsoft.com/en-us/azure/databox-online/azure-stack-edge-gpu-edge-container-registry). Once the API is deployed, we will also deploy an [API Management self-hosted gateway](https://docs.microsoft.com/en-us/azure/api-management/self-hosted-gateway-overview) to the [Arc-enabled Kubernetes cluster](https://docs.microsoft.com/en-us/azure/databox-online/azure-stack-edge-gpu-deploy-arc-kubernetes-cluster) and publish the Claims API in APIM.

‎extensions/azure-stack-edge/README.md

Lines changed: 19 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
**Functional Architecture:**
44

5-
![alt tag](../../images/EXT-ase-arch.png)
5+
![alt tag](../../images/EXT-ase-apim-arch.png)
66

77
Prerequisites:
88
* 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.
@@ -44,8 +44,24 @@ X-Pod-IpAddr: 172.27.114.62
4444

4545
[{"claimItemId":100,"claimStatus":"02","claimType":"InstClaim","senderID":"CLPCSVNTEST2","receiverID":"APPCSVNTEST1","originatorID":"ORGNCSVTEST1","destinationID":"DESMEDSTEST1","claimInputMethod":"E","subscriberInfo":[{"subscriberInfoId":100,"subscriberRelationship":"18","subscriberPolicyNumber":"12345","insuredGroupName":"MD000004","subscriberLastName":"Doe","subscriberFirstName":"John","subscriberMiddleName":"","subscriberIdentifierSSN":"489-88-7001","subscriberAddressLine1":"5589 Hawthorne Way","subscriberAddressLine2":"","subscriberCity":"Sacramento","subscriberState":"CA","subscriberPostalCode":"95835","subscriberCountry":"US","subDateOfBirth":"12-19-1984","subscriberGender":"Male","payerName":"","patientLastName":"","patientFirstName":"","patientSSN":"489-88-7001","patientMemberID":"12345","patientDOB":"12-19-1984","patientGender":"Male","catgOfService":"Consultation","claimItemId":100}],"claimNumber":"1234121235","totalClaimCharge":1234.50,"patientStatus":"01","patientAmountDue":0.00,"serviceDate":"0001年01月01日T00:00:00","policyNumber":"898435","claimPaidDate":"2021年02月03日T00:06:38.4030071","serviceLineDetails":[{"serviceLineDetailsId":100,"statementDate":"2018年10月31日T08:30:00","lineCounter":1,"serviceCodeDescription":"INPT","lineChargeAmount":15000.00,"drugCode":"UN","drugUnitQuantity":23,"pharmacyPrescriptionNumber":"123897","serviceType":"Consultation","providerCode":"72","providerLastName":"Longhorn","providerFirstName":"Dr. James","providerIdentification":"20120904-20120907","inNetworkIndicator":true,"claimItemId":100}],"planPayment":[{"planPaymentId":100,"primaryPayerID":"MEDICAID","cobServicePaidAmount":15000.00,"serviceCode":"ABC","paymentDate":"2021年02月03日T00:00:00","claimAdjGroupCode":"HIPAA","claimAdjReasonCode":"CO","claimAdjAmount":500.00,"claimAdjQuantity":"3","claimItemId":100}]}]
4646
```
47+
At this point, we have successfully deployed Claims API to the ASE. In the following steps, we will add API Management functionalities to this lab.
4748

48-
Notes:
49+
12. [Deploy APIM](https://docs.microsoft.com/en-us/azure/api-management/get-started-create-service-instance) in Azure and create a new API: "Claims API" and define the backend endpoint by specifying the k8s internal endpoint for Claims API: "http://claims-api-svc.claims-api-dev".
50+
![image](https://user-images.githubusercontent.com/15071173/123028500-49b2b080-d394-11eb-9013-56735ddd6354.png)
51+
![image](https://user-images.githubusercontent.com/15071173/123028245-f93b5300-d393-11eb-8f71-d3b6d736c3ec.png)
52+
13. Make sure you have followed instructions to [enable Arc for K8S on ASE](https://docs.microsoft.com/en-us/azure/databox-online/azure-stack-edge-gpu-deploy-arc-kubernetes-cluster): ![image](https://user-images.githubusercontent.com/15071173/123027251-5f26db00-d392-11eb-9978-fdd7c1b2c0eb.png)
53+
14. Install Azure Arc extension: API Management gateway (preview) in k8s namespace "apim":
54+
![image](https://user-images.githubusercontent.com/15071173/123027012-fa6b8080-d391-11eb-8523-fdcf2bbd78b2.png)
55+
15. Add "Claims API" to the APIM Gateway:
56+
![image](https://user-images.githubusercontent.com/15071173/123029055-5c79b500-d395-11eb-8d55-6f93bab2f243.png)
57+
16. Confirm the APIM Gateway service is running:
58+
![image](https://user-images.githubusercontent.com/15071173/123027359-8f6e7980-d392-11eb-87f1-23b5aa5afa09.png)
59+
17. Use Postman to send a request to APIM Gateway:
60+
![image](https://user-images.githubusercontent.com/15071173/123029586-34d71c80-d396-11eb-9d8a-a08fa736ebab.png)
61+
18. Examin the APIM gateway metrics:
62+
![image](https://user-images.githubusercontent.com/15071173/123029833-96978680-d396-11eb-84ff-cd41bdb20b39.png)
63+
64+
**Notes**:
4965
* 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:
5066
```bash
5167
azureuser@Ubuntu1804:~$ kubectl get secrets -n claims-api-dev
@@ -73,5 +89,5 @@ metadata:
7389
uid: 1ce2902e-78b3-433b-a289-f6c0fa2b655c
7490
type: kubernetes.io/dockerconfigjson
7591
```
76-
* Seeing is believing:
92+
* Finally, **seeing is believing**:
7793
![InkedEXT-ase-redondo_LI](https://user-images.githubusercontent.com/15071173/113322952-34b10e80-92ca-11eb-890c-c065b3d37433.jpg)

‎images/EXT-ase-apim-arch.png

267 KB
Loading[フレーム]

0 commit comments

Comments
(0)

AltStyle によって変換されたページ (->オリジナル) /