You can check the health status and version information of Manager, Worker, Cache, Integration, and Portal modules in the Apinizer platform. You can perform healthcheck and version checks from within Kubernetes using internal service names or from outside Kubernetes using external access URLs. You can verify that the system is working correctly, diagnose potential issues early, and access critical information during troubleshooting processes.
You can perform healthcheck and version checks for Apinizer modules using two main methods:
From Within Kubernetes
From Outside Kubernetes
Performed by sending requests through internal service names using the curl command from a pod within the cluster. This method is ideal for diagnosing intra-cluster communication problems.
If your modules are exposed externally (NodePort, LoadBalancer, Ingress), performed by sending requests directly to access URLs from your local machine or server. This method is useful for testing general accessibility and external integrations.
If your Apinizer modules are configured to be accessible from outside Kubernetes (for example, services of type NodePort, LoadBalancer, or through an Ingress Controller), you can send requests directly using an HTTP client like Postman or curl from your local terminal.For Apinizer modules’ services exposed externally with NodePort service type, access can be provided from any client through Kubernetes Node IP addresses and Node Ports. The following table presents the details of Apinizer services:
Cache Module: The Cache module is not exposed externally by default in installations (ClusterIP service type). Therefore, if you want to perform health-check and version-check directly from outside Kubernetes, the Cache service’s port 8090 must be configured to be accessible externally.
