Chris Phillips’ Blog - API, Integration and Governance

WARNING: What is covered in this article is not supported. It is recommended that this is only used for a POC where Helm 2.x cannot be used.

This is a work around to a problem I have seen a couple of times. I expect this problem to be fixed in a future release of APIConnect.

When APICUP (the API Connect Installer) configures a DataPower Gateway to be deployed it internally generates a Helm chart. This Helm chart includes a stateful set that includes both an init container as well as the main container.

Out of the box the DataPower init container is set to be a busy box image deployed on docker hub. Therefore if the environment that is being used to host the Kubernetes deployment does not have internet access then it fails.

Thanks to Sara Hagger

DataPower is the gateway/runtime for API Connect. In order for API Connect to synchronise APIs with the Gateway it uses a new DataPower piece of function called the API Connect Gateway Service. When you deploy DataPower in Kubernetes with APIC UP a special log target is configured to store the API Connect Gateway Service logs. However on all other forms of DataPower this is needs to be enabled.

I have reuploaded my APIC Profiler video as Asciinema deletes videos after a week if there is not an owner assigned.

API Connect allows an Application to subscribe to one plan for a product. This is traditionally used to determine which rate limit they are allowed to subscribe to. A couple of years ago Chris wrote an article on how to use this for plan variable to route to specific endpoints. Istio provides the facility to route to different endpoints depending on header variables. This article shows how you can take the plan from a context variable and set it to a header to be picked up by Istio.

This is a very simple task. However one I occasionally get the syntax wrong for.

The scenario is you need to modify the environmental variable of a Kubernetes Pod/Deployment. In order to do this you must edit the Deployment. Once this is saved a new pod is spawned and the old pod is terminated. This is repeated until all pods have been updated. When modifying the deployment if you create a syntax error k8s does not save the config change.

In a few articles I have used Asciinema. I am not affiliated anyway with this tool just a big fan.

It is the youtube of the command prompt.

The service is free (As far as I have found). It allows you to record a terminal/bash session and upload it to their website. What it uploads is much smaller then a regular video. In addition if you want to copy and paste from the video, you can!