-
Notifications
You must be signed in to change notification settings - Fork 74
Explicitly disallow istio sidecar injection for certain workloads #1476
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: yolocs The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
The following jobs failed:
Automatically retrying due to test flakiness... |
The following jobs failed:
Automatically retrying due to test flakiness... |
/retest |
3 similar comments
/retest |
/retest |
/retest |
/lgtm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For my own edification, which of our infrastructure pieces should have the side car?
Only ingress? Why not fanout/retry, which send to other possibly side-car'ed Pods?
@Harwayne Fanout/retry are pull based so no inbound policy enforcement is needed. We haven't clearly identified how to use istio for outbound traffic to other sidecar'ed pods (there are several possibilities though). So to minimize impact, I choose to disable sidecar for fanout/retry at the moment. You think it's a better idea to enable them now? |
/retest |
1 similar comment
/retest |
Hi @yolocs I need to have the istio sidecars enabled for all these workloads, where do I set the allowIstioSidecar: true value? Thank you |
@upodroid The parameter is internal. E.g. https://github.com/google/knative-gcp/blob/master/pkg/reconciler/brokercell/brokercell.go#L238 If you can create an issue, I will help make the change :) |
Fixes #1474
Proposed Changes
Release Note
Docs