Closed planetf1 closed 3 years ago
Many people have hit this issue - not just with istio, but other sidecars. This is now being designed to go into base kubernetes, probably 1.16. Initial discussion was in https://github.com/kubernetes/kubernetes/issues/25908 but See https://github.com/kubernetes/enhancements/issues/753 for the proposed implementation
Note the tail end of the discussion 'Please keep in mind, this KEP is very important for Istio !
It's a show stopper for all projects using service frameworks with coordinated bootstrap/shutdown (akka cluster, lagom etc.) together with istio service mesh'
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 20 days if no further activity occurs. Thank you for your contributions.
still valid
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 20 days if no further activity occurs. Thank you for your contributions.
The VDC environment will need significant re-work to adapt to the many changes made in Egeria to better support metadata integration. Additionally the helm charts used for the lab & a simple base config have evolved to better support different types of services, exposing of ports, persistent storage etc.
As such specific incremental changes to the current - now old - charts do not really add value.
As such closing for now
If istio is enabled in the vdc charts, the init* jobs will have an additional istio proxy. However this proxy will be running & not exit when for example the postgres data loading has completed.
There is some discussion of the relationship between sidecars such as istio & jobs at https://github.com/istio/istio/issues/6324
For now mitigation is to disable istio (which isn't yet default in any case) However istio is needed even in jobs as it will monitor & permit/deny traffic between the pods.