You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@jkralik please track #168 for ACME retries which we're currently completing. That's essentially a more wholistic way to solve this in a standard compliant way.
Subject of the issue
When acme server challenging acme client (lego) it gets error:
It is caused by ingress when during container startup with updated docker image.
Your environment - kubectl version
Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.3", GitCommit:"2d3c76f9091b6bec110a5e63777c332469e0cba2", GitTreeState:"clean", BuildDate:"2019-08-19T11:13:54Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.2", GitCommit:"c97fe5036ef3df2967d086711e6c0c405941e14b", GitTreeState:"clean", BuildDate:"2019-10-15T19:09:08Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"linux/amd64"
Expected behaviour
Use retry-able http client (https://github.com/hashicorp/go-retryablehttp) for acme http challenge.
Actual behaviour
Randomly acme client doesn't obtain certificate for updated container.
Additional context
When I replaced
certificates/acme/authority.go
Line 265 in 967e86a
It is works as is expected.
The text was updated successfully, but these errors were encountered: