Closed mausch closed 9 months ago
@mausch sorry to hear you are having trouble.
This error you are seeing indicates a DNS issue in your environment. Per the Kubernetes "DNS for Services and Pods" docs:
Any Pods exposed by a Service have the following DNS resolution available:
pod-ip-address.service-name.my-namespace.svc.cluster-domain.example.
Therefore, postgres-repo-host-0.postgres-pods.postgres.svc.kubernetes
should properly resolve.
I recommend debugging DNS resolution in your environment so see if any issues exist, e.g. per the following docs:
https://kubernetes.io/docs/tasks/administer-cluster/dns-debugging-resolution/
Otherwise, this does not appear to be an issue with PGO itself (e.g. since stanza creation is working just fine in a variety of Kubernetes environments).
We have not heard back, so I am closing this issue. If you need further assistance, feel free to respond here or ask a question in our Discord server.
Overview
With this rather trivial PostgresCluster:
The pgo logs show this error:
Pod
postgres-repo-host-0
is running without any visible issues. No idea where thispostgres-repo-host-0.postgres-pods.postgres.svc.kubernetes
hostname comes from? It should bepostgres-repo-host-0.postgres.svc.cluster.local
.Also not sure what the consequences are. I see thousands of failures in
pg_stat_archiver
, would this cause that?Environment
Please provide the following details: