Chris Phillips’ Blog - API, Integration and Governance

In API Connect 10.0.5.3+ and 10.0.6.0+ we can register sub systems without the need for an external load balancer. This is only possible for Kubernetes, OpenShift and CloudPak for Integration.

Quick video to show the initial API Governacne function.

Deep health check of the API Manager

It is important for a load balancer to know if the application is running. Deep health checks are used to validate that not only webpages are running but also the underlying application is working.

In APIConnect 10.0.6.0 the governance function does not come automatically enabled. It must be enabled by modifying the CR.

API Governance is something I have talked about for a long time. Governance is a large topic but today we will cover standards and API Consistency. I have written a few times about API Consistency and its importance.

Recently I was asked to provide a sample custom policy for APIC that contained an XSLT.

When deploying a kubernetes application and a pod displays an event with

0/9 nodes are available: 9 node(s) had volume node affinity conflict

There are two common reasons for this.

Recently when visiting a customer, they were wanting a custom policy that could be used to do HMAC validation of payloads.

In brief HMAC is a tool to verify a payload programmatically. When the payload is passed it a signature is attached, in this case in a header. The HMAC algorithm then uses a secret key to generate the digest and that is compared against the signature passed.

I have spent years trying to find out how to get better logging from the OCP router. I am not going to steal credit, but go to this blog, its amazing! https://alexandre-vazquez.com/how-to-enable-access-logs-on-openshift-default-routes/

I have been asked almost daily for the last few weeks what is my preferred CICD took or process. My answer is always the same, given APIC has a rest interface the best tool is the one the team know.