1032: Enable Istio mTLS globally on istio-system namespace
1 unresolved thread
1 unresolved thread
Package Merge Request
Package Changes
Add values to istio that drive mTLS globally
Package MR
big-bang/product/packages/istio-controlplane!175 (merged)
For Issue
Closes #1032 (closed)
Closes #1032 (closed)
Merge request reports
Activity
changed milestone to %2.12.0
added istio kindci priority6 statusreview labels
assigned to @charden
changed milestone to %2.13.0
added 7 commits
-
0fa5a856...c9fa5c40 - 6 commits from branch
master
- e429d813 - 1032: Enable Istio mTLS globally on istio-system namespace
-
0fa5a856...c9fa5c40 - 6 commits from branch
mentioned in commit 888d77a4
155 155 istio: 156 156 # -- Toggle deployment of Istio. 157 157 enabled: true 158 mtls: 159 # -- STRICT = Allow only mutual TLS traffic, 160 # PERMISSIVE = Allow both plain text and mutual TLS traffic 161 mode: STRICT Personal opinion as a BB user - STRICT for everything out of the box scares me a lot, since it forces strict on my mission apps, etc (it's also possibly why the master pipeline failed, if fortify was not ready for strict mtls
). I would greatly prefer PERMISSIVE default, but ability to switch to STRICT when I'm ready.
Please register or sign in to reply