gorgeous-country-4302605/18/2021, 2:09 PM
- postgresql to be more specific.
is created and pods appear as expected and based from logs etc everything is just fine including volume bindings etc. This is also true from Pulumi side when running
to an empty cluster.
creation hangs up however and it finally gives up with the following error:
I am however absolutely certain that yes, there are specified nodes available and also that those pods are indeed running. I've been banging my head against the wall with this problem for some time now and would appreciate ideas. As an interesting detail if running
kubernetes:core/v1:Service (postgres): error: 2 errors occurred: * the Kubernetes API server reported that "default/postgres" failed to fully initialize or become live: 'postgres' timed out waiting to be Ready * Service does not target any Pods. Selected Pods may not be ready, or field '.spec.selector' may not match labels on any Pods
again also the
update seems to hang. I'll provide code snippets regarding this issue to a thread under this message.
and changed my
to allow using deployments. Also changed my
. Let's see if this has any effect on this...
. It's not in the code or at the cluster at this point but apparently it is in Pulumi state
, but again it gets stuck