Closed lacarvalho91 closed 3 months ago
Hoping theres a workaround 🙏
Hey @lacarvalho91,
Thank you for reporting this! The problem is on the runner side, but we will fix it on the hook side. Essentially, we put side-car into services context, which causes the out of bound exception... Sorry this happened, I'll introduce a fix soon :relaxed:
Also, sorry for the delay!
@nikola-jokic awesome that sounds promising. I was very much hoping it could be fixed on this side. Thank you 😊
@nikola-jokic when that PR is merged what needs to happen for it to be included in the runners (images) themselves?
We are experiencing the same behavior when attempting to enable istio at the namespace level:
kubectl label namespace $NAMESPACE istio-injection=enabled
We are looking to gather http-level observability metrics and are blocked at the moment.
When using k8s container mode and adding a sidecar to the hook template we consistently get the following workflow error:
The logs point to the runner:
This issue in the runner repo seems to be reporting the same thing. But I thought I should raise it here as it seems that sidecars just don't work with kubernetes mode, even though the examples have one defined and the ADR seems to suggest it is intended to work.
If we remove the sidecar then its fine.
We're using a very similar template to what is in the examples, we also tried one without the service container: