We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I have upgraded my gke cluster from 1.10.5-gke.4 to 1.10.6-gke.2.
Now GLBC is not making appropriate changes to the load balancer configuration in google cloud whenever I add or make changes to ingress resources.
After ingress resource modification I see events like below.
Normal UpdateCertificate 15m cert-manager Successfully updated Certificate "foo-tls" Normal ADD 12m loadbalancer-controller dev/foo Normal ADD 6m loadbalancer-controller dev/foo
But loadbalancer didn't add any new forwarding rules to it. Some times it works when I delete and recreate the ingress resource all together.
I can confirm that I'm not out of quota on any resource.
The text was updated successfully, but these errors were encountered:
See #471
Sorry, something went wrong.
Yeah, that must be it. Thank you
No branches or pull requests
I have upgraded my gke cluster from 1.10.5-gke.4 to 1.10.6-gke.2.
Now GLBC is not making appropriate changes to the load balancer configuration in google cloud whenever I add or make changes to ingress resources.
After ingress resource modification I see events like below.
But loadbalancer didn't add any new forwarding rules to it.
Some times it works when I delete and recreate the ingress resource all together.
I can confirm that I'm not out of quota on any resource.
The text was updated successfully, but these errors were encountered: