Anyone is using the ingress (for kubernetes) package ? I'm wondering why I meet the current issue : When I need to build an image for a service, my ingress gets a "connexion refused" error, and fails to create. I need to do a second

pulumi up

when everything else is ready to have it working. I'm using it exactly like in the examples. Any idea ? :s. All I saw is that if i'm pulling an image and not building it, everythings seems to work fine...

Hi Alann, you mean this -> https://www.pulumi.com/registry/packages/kubernetes-ingress-nginx/?

Hi ! Exactly ^^. I'm using the typescript wrapper but that's it.

Do you have by any chance an example repo?

Hmm, I can create a repo to isolate the issue if you want, but everything is a work in progress and there might be stuff which doesn't have anything to do with the issue ^^'

I can create one too. So as far as I understood, you deploy the ingress controller and then your services/deployment of your own app

Tbh, I'm new to everything around kubernetes, and I'm learning so I can get better at it ^^'. I'm fine developping around with docker-compose, but I want to understand the whole process of modern development under micro services context, so I'm trying to learn kubernetes basics trough Pulumi (as a dev.... :')). So to summarize , I have a folder called "services" with 2 services (one backend for auth with fastify, one frontend which is a vue 3 project). I have a folder named infrastructure with Pulumi and some helpers in TS to easily and automatically integrates any created services. The process is this : • I create a namespace • I create the Ingress controller • I have an automation process looking for each loadable services, dynamically loads them and : ◦ Build a local image (no push) ◦ Build the service (Cluster IP) ◦ Build the deployment • When everything is done, build the Ingress and inject configuration exposed by a loadable service. So far, only my auth service is declared "loadable", which means than the frontend is out of the equation.

yes!

Tell me if you need a dedicated repo, I'm fine with making a minimal project for it. It's already super kind of you to help me, and I don't want to eat your time like it's nothing 🙂

Hi @prehistoric-laptop-47240 it worked for me. Please have a look into https://github.com/dirien/pulumi-ingress-test Maybe I use a different code! Btw: I use Civo as Cluster.

Oh wow, thank you so much for your time and effort. I read how you created this project, and I have to admit, I don't see any conceptual difference... I'm wondering if it could be something about env, such as docker-desktop k8s integration... hmm...

Try to delete it by hand

Yes

I tried it on a cloud provider. On my docker-desktop I can' get the status to ready, as it is not updating the status of the ingress with the loadbalancer ip

I'm afraid I'm doing a beginner mistake... I was extracting the name for the ingress service name from a created service metadata name instead of giving it the same string I gave to generate the name. Maybe it's different ?

oh, yes. Either you fix the names so there is no hash at the end. Or you use the output of the service as input for the ingress service definition

I gave to the ingress, my service.metadata.name output<string>

could you try the default namespace too?

Oh, actually, it does work without namespace x)

so as far as I understood, you deploy the controlle into the default ns any your deployment into a specific ns

I'm having a namespace shared and used the ingress and all its services

ok I got smth similar

Actually, weird fact : I logged the inner string inside the Output type, and the actual name I give as a string, and they are equal, even when it doesn't work

So now it works!

😮 that could explain the randomness of the issue. Trying right now

ok. maybe some glitched resources