-
Notifications
You must be signed in to change notification settings - Fork 0
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
feat(istio): enable CNI in Istio configuration #274
base: main
Are you sure you want to change the base?
Conversation
99f55c0
to
2140463
Compare
On-behalf-of: @SAP [email protected] Signed-off-by: Angel Kafazov <[email protected]>
On-behalf-of: @SAP [email protected] Signed-off-by: Angel Kafazov <[email protected]>
On-behalf-of: @SAP [email protected] Signed-off-by: Angel Kafazov <[email protected]>
On-behalf-of: @SAP [email protected] Signed-off-by: Angel Kafazov <[email protected]>
2140463
to
b49785d
Compare
Lets clarify if we should / need to the istio cni component. Also if we use it, if we should change the way we use the init sidecar of the containers |
istio-init is replaced by the istio-cni. We need this only for MacOS and Podman, but since it works everywhere we can opt to keep it as default? |
4817f0f
to
9d39b87
Compare
9d39b87
to
87b18fc
Compare
baee0b2
to
ee27716
Compare
87b18fc
to
296fe1c
Compare
Description
The local-setup fails on MacOS when docker is used via podman and underlying FedoraOS vm.
The used
kindnet
CNI remains, as istio-cni to designed to work with it. When using it, the istio-init is not used but istio-proxy still is and it works with the Istio-CNI and not with iptables.Additional info: https://istio.io/latest/docs/setup/additional-setup/cni/
Changes:
openmfp-system
namespace