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
When Istio auto-injection is enabled, the camel-k builder always wait for the Istio container to complete (which will never happen), and triggers the default 5 min timeout (though Buildah finished in around 1~2 min and after the timeout the build still succeeds).
Using #3309 built on a M1 Max Macbook, with self-built arm64 version of quarkus-mandrel (that does not seems the culprit?), Docker Desktop 4.9. Haven't tested other builds yet.
My install command is
exclude pods with the matching builder label in Istio configuration (neverInjectSelector afaik)
If you want to keep the injection I think you can I think you can also configure Istio to enforce waiting for the sidecar eg. by using holdApplicationUntilProxyStarts
When Istio auto-injection is enabled, the camel-k builder always wait for the Istio container to complete (which will never happen), and triggers the default 5 min timeout (though Buildah finished in around 1~2 min and after the timeout the build still succeeds).
Using #3309 built on a M1 Max Macbook, with self-built arm64 version of quarkus-mandrel (that does not seems the culprit?), Docker Desktop 4.9. Haven't tested other builds yet.
My install command is
The text was updated successfully, but these errors were encountered: