-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ingress .status.loadBalancer field was not updated with a hostname/IP address with traefik ingress controller configured as NodePort #1812
Comments
Seems to be related to #1810 - since as mentioned there, v1 ingress has been added to await logic which was silently being skipped in the past.
That is a bit of red-herring - the provider tries to inject a useful message for the failure but clearly this doesn't apply in all cases. The specific issue seems to be this: If its created by the helm chart, you might want to create the ingress object after the helm chart is ready (add |
Closing in favor of #1810 |
Yes, the service exists. It's a service for serving frontend and the frontend can be accessed through browser. Also confirmed with
Yes, it depends on |
I had the same issue in my playground project. Then I deleted pulumi stack and all resources and recreated it. Since then issue dissipated. I had a feeling that everything started after 2 pulumi up commands were running in the same time and one failed. I tried pulumi refresh which ended successfully, but the issue were still there. |
Sorry I am not sure I understand. Is the problem still there? Are you saying refreshing caused the dissipated problem to reoccur? Can you make sure you are running with v3.12.2 of the Kubernetes provider or newer? |
Hello!
Issue details
After upgrading from 3.9.0 to version 3.10.1 (3.10.0 is also affected) the following messages in
stdout
are received when creatingIngress
object:These messages appear and stay like this until timeout kicks in and generates similar error message:
Happens in local environment using
k3d v5.1.0
andtraefik
helm chartv10.6.2
.It's important to mention that the deployment, service, ingress and ingress controller are working as expected because I can access them throughout my
localhost
(I've destroyed and recreated the cluster to eliminate possible working state because of previous deployments).The great mystery is why pulumi expects
status.loadBalancer
field when myingress-controller
is configured asNodePort
, notLoadBalancer
.The workaround is to use
'pulumi.com/skipAwait': 'true'
annotation on theIngress
object so this is most likely related to recent changes in await logic #1795Steps to reproduce
k3d
(most likely works with other local cluster providers likekind
)Deployment
andService
object (can be defaultnginx
image)Ingress
resource connected to previously definedService
withouthost
. Example:traefik
helmv3.Chart
configured as aNodePort
notLoadBalancer
Expected: Deployment should progress and finish successfully
Actual: After 10 minute timeout the deployment fails
The text was updated successfully, but these errors were encountered: