Troubleshooting
Guidance for diagnosing and resolving common issues
failed to call webhook
When operating within a GKE Private Cluster, an additional firewall rule is required when installing PerfectScale Automation Agent.
A new firewall rule will permit the Control Plane address range to communicate with the Cluster Pod IPv4 address range on port 8443.
Refer to the official documentation for detailed instructions:
Autoscaler debugging
To diagnose issues with the PerfectScale Autoscaler, start by checking the logs of the serve pod. If none of the following logs are present: patched, empty patch, or failed to marshal patch:, it may indicate that the API server is unable to reach the PerfectScale Autoscaler serve pod, and most likely it is an infrastructure-related issue.
Here are some common scenarios where this might happen:
Network policies at the Kubernetes level (e.g., Calico) are blocking access.
Network policies blocking traffic from the API server to Kubernetes pods (e.g., GCP custom security groups).
An interceptor (such as Istio) intercepts requests but does not forward them to the serve pod.
If you see error logs from the serve pod, such as messages starting with failed to marshal patch: or empty patch, please contact support, and we will assist you.
Last updated