The newbie cloud architect diary

$ kubectl create namespace gravitee
namespace/gravitee created
$ kubens gravitee
Context "microk8s" modified.
Active namespace is "gravitee".

• Gravitee Gateway (not part of the evaluation)
• Gravitee Management API
• Gravitee Management UI
• Gravitee Portal UI
• MongoDB replica-set (optional dependency)
• Elasticsearch cluster (optional dependency)

$ helm repo add elastic https://helm.elastic.co
$ helm install \
    -f https://raw.githubusercontent.com/elastic/helm-charts/master/elasticsearch/examples/microk8s/values.yaml \
    --name elasticsearch elastic/elasticsearch \
    --set replicas=1,minimumMasterNodes=1
$ curl "http://$(kubectl describe \
    svc elasticsearch-master | \
    grep Endpoints | grep 9200 | \
    awk '{print $2}')/_cat/health?pretty"
1599226906 13:41:46 elasticsearch green 1 1 0 0 0 0 0 0 - 100.0%

$ helm repo add graviteeio https://helm.gravitee.io
$ helm repo update
$ helm install --name graviteeio-apim graviteeio/apim3 \
    --set mongodb-replicaset.enabled=true \
    --set mongodb-replicaset.replicas=1 \
    --set es.endpoints="{http://elasticsearch-master.gravitee.svc.cluster.local:9200}"

Note that the APIM services are mapped by some Ingress route resources:

$ kubectl get ing
NAME                                   HOSTS              ADDRESS   PORTS     AGE
graviteeio-apim-apim3-api-management   apim.example.com             80, 443   8m
graviteeio-apim-apim3-api-portal       apim.example.com             80, 443   8m
graviteeio-apim-apim3-gateway          apim.example.com             80, 443   8m
graviteeio-apim-apim3-portal           apim.example.com             80, 443   8m
graviteeio-apim-apim3-ui               apim.example.com             80, 443   8m

Mapping paths:

$ alling=$(kubectl get ing | grep -v NAME | cut -d' ' -f1
$ for i in ${alling[@]}; do \
    echo "$i -> $(kubectl describe \
        ing $i | grep '                    /' | awk '{print $1}')"; \
  done

graviteeio-apim-apim3-api-management -> apim.example.com/management
graviteeio-apim-apim3-api-portal -> apim.example.com/portal
graviteeio-apim-apim3-gateway -> apim.example.com/gateway
graviteeio-apim-apim3-portal -> apim.example.com/
graviteeio-apim-apim3-ui -> apim.example.com/console(/|$)(.*)

$ helm install --name nginx-ingress stable/nginx-ingress \
    --set rbac.create=true \
    --set controller.publishService.enabled=true

And map the hostname api.example.com with Load balancer IP:

$ echo "$(kubectl get svc | grep nginx-ingress-controller \
     | awk '{print $3}') apim.example.com" | sudo tee -a /etc/hosts

$ sensible-browser https://apim.example.com/console/#

• Adjust the Portal layout (Settings > PORTAL > Theme)
• Create API categories (Settings > PORTAL > Categories)
• 
  

• Add a new API from default page (APIs > (Portal) > GENERAL > Details > +).
• Import from link petstore-oas3.yaml and activate the checkbox "Create policies on paths" from "Swagger import configurations".
• Start the API using the button from the "Danger zone".
• Optionally, you can:
• Add a custom picture (APIs > (Portal) > GENERAL > Details).
• Add a Swagger documentation (APIs > (Portal) > DOCUMENTATION > pages).
• Add free labels or select some centrally defined categories.

• Add a "Petstore plan" (APIs > (Portal) > PLANS > Plans > +)
• Activate auto-validation and click NEXT
• Select "Api-key"-based authentication and click NEXT
• Skip the Gateway restrictions by clicking NEXT
• Add "Api key" to the policy chain and click SAVE
• Click on the blue cloud icon to publish the API Plan
• Configure the API Proxy settings (APIs > Proxy)
• Change the context path to /petstore (GENERAL > Entrypoint)
• Enable Cross-origin resource sharing, allow * host and GET method (GENERAL >  CORS)
• Change the endpoint to http://petstore.swagger.io/v2/store/inventory (BACKEND SERVICES >  Endpoints)
• You can optionally activate Health checks in order to monitor the availability of the API service endpoint

• Click on PUBLISH API within the "Danger zone"
• You can keep the API private if accessing the Portal with the same user, or MAKE PUBLIC otherwise.

$ sensible-browser https://apim.example.com/

$ curl "https://apim.example.com/petstore" \
    -H "X-Gravitee-Api-Key:4fafce1d-6080-4654-b6d7-c5aa4ec0611c"