-
Notifications
You must be signed in to change notification settings - Fork 1k
Feat: Migrated to Istio 1.26.1 and merged istio and istio cni #3153
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 1 commit
429b2cc
b1ffa69
f469eec
d470cd6
975fe33
5b7e93c
fe5b32a
f8c2d3b
71d6943
06080c1
8404060
c37efbf
44230f4
3844f43
dddb033
d56e54f
8d89832
073098a
cbfa44d
b7af4f8
7ab891a
fee6a65
c04fe0c
82fbdc4
7d830f6
e16e9b2
4fcf756
1e4ac35
dffec6c
e91a3d7
26cde01
1ab6a58
37c0335
c090f49
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,13 @@ | ||
--- | ||
# Allow traffic within kubeflow-user-example-com namespace for testing, do we need it here or shall i add just in GHA worklow, since its just for the test? | ||
apiVersion: security.istio.io/v1beta1 | ||
kind: AuthorizationPolicy | ||
metadata: | ||
name: allow-test-namespace-traffic | ||
namespace: kubeflow-user-example-com | ||
spec: | ||
action: ALLOW | ||
rules: | ||
- from: | ||
- source: | ||
namespaces: ["kubeflow-user-example-com"] |
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Please redo this from scratch. It should only patch out the CNI enablement in the sidecar. Nothing else. More than 30 line sin total is probably not the right way. Especially more than 20.000 lines. We dont want to maintain this many lines. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. What did you do with
Why did you add this? WHy is it needed to disable istio-cni? where is the simple inline delete patch for the daemonset? |
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.
Why is this needed? i think the profile controller creates it by default