-
Notifications
You must be signed in to change notification settings - Fork 91
Transparent proxy injection into existing K8s clusters #335
Comments
Please reference the upstream issue from Kubernetes. We might get it for 1.7. |
Depends on kubernetes/community#132 |
I opened this issue, hopefully we can enhance PodPreset and re-use functionality: |
There are two aspects of proxy injection: inserting a sidecar and programming iptables. Rephrased the title to be about the first item. |
this is an epic so maybe it should cover both ? |
Yes, it's an epic and covers everything. You can open issues and group them under this epic. |
The title matches the roadmap item, let's leave it as it is. |
epic should not be closed yet |
This is done. P1 enhancements are possible, but they will need to be prioritized. |
What's the status on this? Istios documentation says it's not ready but all the pull requests and issues are merged and closed respectively. |
@Promaethius can you provide a link to where it says it's not ready ? |
Issue moved to istio/istio #1365 via ZenHub |
-use-initializer
flag tobin/e2e.sh
. The feature will by enabled by default in istio/pilot after Additional sidecar injection enhancements #1104 is merged. The initializer is cluster scoped so any bugs could affect the entire test cluster. We should be prepared to revert to default-off and manually delete the initializer configuration. ClusterPool testing feature will help here (cc @sebastienvas). The feature can be enabled in istio/istio after istio/pilot switch over is complete.TODO
The text was updated successfully, but these errors were encountered: