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
Describe the bug
the annotations in the service section are applied to both the vault and the vault-internal services and there is not way to distinguish between the two.
When deploying to OpenShift and the annotation is used to request a certificate, this causes a race condition because two services are trying to modify the same secret (containing the certificate)
try to connect to the vault instance via the vault service. 50% of the times the connection will fails because the cert cannot be validated.
Suggested solution: allow for a way to attribute annotations to individual services.
Also when did this change? As a workaround one could use the old version in which this used to work.
The text was updated successfully, but these errors were encountered:
no I don't recall the old version, actually people have looked into this and said that the issue was there since the beginning, so probably I was just lucky.
Describe the bug
the annotations in the service section are applied to both the
vault
and thevault-internal
services and there is not way to distinguish between the two.When deploying to OpenShift and the annotation is used to request a certificate, this causes a race condition because two services are trying to modify the same secret (containing the certificate)
To Reproduce
Steps to reproduce the behavior:
with these options:
try to connect to the vault instance via the vault service. 50% of the times the connection will fails because the cert cannot be validated.
Suggested solution: allow for a way to attribute annotations to individual services.
Also when did this change? As a workaround one could use the old version in which this used to work.
The text was updated successfully, but these errors were encountered: