No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

image.png

When cresting ingress I got this message and it take very long time to run and eventually I go this error message: `  error: 2 errors occurred:
        * resource public/nginx-ingress-ingress-nginx-controller was successfully created, but the Kubernetes API server reported that it failed to fully initialize or become live: 'nginx-ingress-ingress-nginx-controller' 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`

_Please let me know if anyone has a fix fo this issue._

Can you share your code?

Pulumi is absolutely compatible with AKS. _Many_ of our customers are using it. :slightly_smiling_face:

K8sIngress.ts

Here is my code converted from Yaml file using pulumi tool

<@UDEJ1F5SQ> How is it? this is my blocker now. Please help.

Even when convert to helm resource I got the same issue. I have give up with pulumi kubernetes and go back with yaml files. :man-facepalming:

hey <@UPV65KV08> I didn't see this thread. Can you also share your deployment code as well, ie the thing that's creating your deployment? it looks like this issue is coming from the service you're deploying not targeting the correct deployment

Hi <@UCWG26BH7> I just try to create the nginx control using pulumi heml only. I successfully created by below command. However when converted  to pulumi code I got above error.
```# Add the ingress-nginx repository
helm repo add ingress-nginx <https://kubernetes.github.io/ingress-nginx>

# Use Helm to deploy an NGINX ingress controller
helm install nginx-ingress ingress-nginx/ingress-nginx \
    --namespace default \
    --set controller.replicaCount=2 \
    --set controller.nodeSelector."beta\.kubernetes\.io/os"=linux \
    --set controller.service.externalTrafficPolicy=Local \
    --set defaultBackend.nodeSelector."beta\.kubernetes\.io/os"=linux \
    --set controller.service.loadBalancerIP="MPublicIP" \
    --set controller.service.annotations."service\.beta\.kubernetes\.io/azure-load-balancer-resource-group"="aks_group" \
    --set controller.service.annotations."service\.beta\.kubernetes\.io/azure-dns-label-name"="aks"
	```

Here is the parameter I passed in
```ingressCreator({name:'nginx-ingress', namespace:'default', publicIp:'20.30.40.50", provider, dnsLabel:'steven'});```

your helm values don't look entirely correct. once you depkoy, can you use kubectl to check the namespace is correct for all resources (ie everything is in the same namespace?)

actually, It can deploy to azure every work fine on AKS. Only problem is because the error threw at pulumi side and so that the deployment got failed. I not able to go next steps.

<@UCWG26BH7> Maybe my Helm is not correct. Please share if do you have any sample for reference.