Anchore Upgrade Jobs Stuck in Upgrading Release When Istio SideCar Injection Enabled #183
Comments
HN23
pushed a commit
that referenced
this issue
Jan 10, 2024
* add feeds workspace dir to fixPermissions init container * bump chart version * use sh not bash Signed-off-by: Brady Todhunter <[email protected]> --------- Signed-off-by: Brady Todhunter <[email protected]>
Btodhunter
pushed a commit
that referenced
this issue
Jan 10, 2024
* add feeds workspace dir to fixPermissions init container * bump chart version * use sh not bash --------- Signed-off-by: Brady Todhunter <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When Anchore is deployed into a namespace or cluster that has Istio Sidecar Injection enabled and the upgrade jobs fire, the jobs run indefinitely (stuck in 'upgrading release').
This appears to be a known issue:
Handling Istio Sidecars in Kubernetes Jobs
Jobs are Broken (they Never Complete) · Issue #11045 · istio/istio
Better support for sidecar containers in batch jobs · Issue #6324 · istio/istio
Recommendations (https://discuss.istio.io/t/best-practices-for-jobs/4968) seem to point to calling
curl -sf -XPOST http://127.0.0.1:15020/quitquitquitafter the job has completed.While supporting this type of configuration in the upgrade job would be implementation specific, has there been any consideration for introducing logic to the job chart(s) to handle this scenario?
The text was updated successfully, but these errors were encountered: