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
I setup istio using helm chart and everything works well so far. However, I tried to enable the envoy access logs using helm ugrade which i set the meshConfig.accessLogFile="/dev/stdout"
I can see there is changes, and I can now view the envoy access log but there are times when I tried to curl from pod-to-pod, it returns this error:
"upstream connect error or disconnect/reset before headers. retried and the latest reset reason: remote connection failure, transport failure reason: TLS_error:|268435581:SSL routines:OPENSSL_internal:CERTIFICATE_VERIFY_FAILED:TLS_error_end:TLS_error_en"
I think this error might cause by the root CA cert is now recreate via helm upgrade, and therefore the pods can't verify the CA cert. I managed to resolve this by deleting my application pod deployment yaml, and reapply again.
Is this a bug or that's how it supposedly work where any changes on helm template would require me to delete deployment and reapply again to reset the CA cert?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I setup istio using helm chart and everything works well so far. However, I tried to enable the envoy access logs using helm ugrade which i set the meshConfig.accessLogFile="/dev/stdout"
I can see there is changes, and I can now view the envoy access log but there are times when I tried to curl from pod-to-pod, it returns this error:
"upstream connect error or disconnect/reset before headers. retried and the latest reset reason: remote connection failure, transport failure reason: TLS_error:|268435581:SSL routines:OPENSSL_internal:CERTIFICATE_VERIFY_FAILED:TLS_error_end:TLS_error_en"
I think this error might cause by the root CA cert is now recreate via helm upgrade, and therefore the pods can't verify the CA cert. I managed to resolve this by deleting my application pod deployment yaml, and reapply again.
Is this a bug or that's how it supposedly work where any changes on helm template would require me to delete deployment and reapply again to reset the CA cert?
Beta Was this translation helpful? Give feedback.
All reactions