pgskipper-check

To check pgskipper-operator health, validate CRD readiness across patronicores.netcracker.com and patroniservices.netcracker.com, verify Helm release states, inspect CR statuses, and review operator deployments, pods, and cluster events for remediation guidance.

A pgskipper-operator health check includes validating CRD establishment, assessing Helm release status and revision history, verifying Custom Resource states, inspecting operator deployments and pod logs, and analyzing relevant Kubernetes events.

Yes, you can use this health check for pgskipper-operator in CI pipelines because it enforces a structured, repeatable workflow that validates CRDs, Helm releases, CR statuses, and operator components suitable for automated environments.

To diagnose pgskipper-operator deployment issues, assess Helm releases for the operator by checking their status and revision history, then correlate these findings with CR statuses, pod conditions, and Kubernetes cluster events for actionable remediation.

If pgskipper-operator Custom Resources are not becoming ready, verify CRD establishment across patronicores.netcracker.com and patroniservices.netcracker.com, inspect operator deployment logs, and review Kubernetes events to identify configuration or component failures.

Yes, the pgskipper-operator health check validates Patroni and Patroni-like resources by verifying CRD readiness, checking Custom Resource statuses, and reviewing operator deployments and cluster events to ensure proper operation.