Sounds like a bug

Question

Sounds like a bug Creating a headless service with the example on the statefulset page on AKS will always be stuck in Finding available pods

quiet-wolf-18467 · Answer

Code seems fine to me Can you describe the service and share the output please

echoing-activity-32278 · Answer

``` kubernetes core v1 Service example api qa error 2 errors occurred the Kubernetes API server reported that example example api qa failed to fully initialize or become live example api qa 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```

echoing-activity-32278 · Answer

Reason is that the statefulset will only be created after the service becomes ready since the statefulset depends on the service s name However the service depends on the statefulset to become ready causing a circular dependency While the doc <https www pulumi com registry packages kubernetes api docs core v1 service ~ text=The 20endpoints 20objects 20target 20some 20number 20of 20living 20objects|https www pulumi com registry packages kubernetes api docs core v1 service ~ text=The 20endpoints 20objects e 20number 20of 20living 20objects> says headless service does not depend on the statefulset to become alive this is not true on AKS

echoing-activity-32278 · Answer

If I directly refer to the service name instead of through service metadata name <https www pulumi com registry packages kubernetes api docs apps v1 statefulset ~ text=web 22 2C 0A 20 20 20 20 7D 2C 0A 20 20 20 20spec 3A 20 7B 0A 20 20 20 20 20 20 20 20selector 3A 20 7B 0A 20 20 20 20 20 20 20 20 20 20 20 20matchLabels 3A 20 7B 0A 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20app 3A 20 22nginx 22 2C 0A 20 20 20 20 20 20 20 20 20 20 20 20 7D 2C 0A 20 20 20 20 20 20 20 20 7D 2C serviceName 3A 20nginxService metadata name 2C replicas 3A 203 2C 0A 20 20 20 20 20 20 20 20template 3A 20 7B 0A 20 20 20 20 20 20 20 20 20 20 20 20metadata 3A 20 7B 0A 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20labels 3A 20 7B 0A 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20app|https www pulumi com registry packages kubernetes api docs apps v1 statefulset ~ text=web 22 2C 0A 20 20 20 2 20 20 20 20 20 20 20 20 20 20app> then everything is fine

quiet-wolf-18467 · Answer

Services are always considered ready in Kubernetes

quiet-wolf-18467 · Answer

If Pulumi is waiting for endpoints that could be a provoke here Let me run the example myself and I ll open a bug report if needed Thanks for bringing to our attention

fast-florist-41572 · Answer

< quiet wolf 18467> I believe it is a bug I m also provisioning a helm chart that relies on a headless service ClusterIP None and getting the following error gt the Kubernetes API server reported that default kratos courier failed to fully initialize or become live kratos courier timed out waiting to be Ready gt Service does not target any Pods Selected Pods may not be ready or field spec selector may not match labels on any Pods

fast-florist-41572 · Answer

I think it actually relates to this line gt <https github com pulumi pulumi kubernetes blob 876eaea150e4c50f8b53f3345bd060139780626e provider pkg await service go L392>

fast-florist-41572 · Answer

It assumes that the selectors must be empty but I don t think that is true

quiet-wolf-18467 · Answer

I m back at work tomorrow and will run some tests on this We ll fix it if it s broken grinning

fast-florist-41572 · Answer

thumbsup Enjoy the last time off slightly smiling face

quiet-wolf-18467 · Answer

As a workaround for now you can add an annotation to your resource to skip the await behaviour

quiet-wolf-18467 · Answer

`<http pulumi com skipAwait True|pulumi com skipAwait True>`

fast-florist-41572 · Answer

< quiet wolf 18467> thanks it was actually an error in helm chart I was trying to install They are incorrectly creating the headless service which has a selector but doesn t get assigned an endpoint