-
Notifications
You must be signed in to change notification settings - Fork 893
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
istio-cni by default #2907
base: master
Are you sure you want to change the base?
istio-cni by default #2907
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@hansinikarunarathne can you take a look at the ray tests? |
0bd1717
to
9f57cbc
Compare
I asked @MaxKavun to check from our end. He should have some findings this week. |
I've done some checks
|
9f57cbc
to
d676269
Compare
Hello @MaxKavun ,I rebased the PR. You can also create PRs against my branch to fix the remaining 3 items from the tasklist in the first post and the istioctl warnings. |
The kuberay-operator needs to disable the init container injection as specified here: |
Thank you, do you mind creating a PR for this? |
@MaxKavun @biswajit-9776 can you take a look at
|
Signed-off-by: juliusvonkohout <45896133+juliusvonkohout@users.noreply.github.com>
Signed-off-by: juliusvonkohout <45896133+juliusvonkohout@users.noreply.github.com>
When istio is enabled, the kuberay-operator must disable the init container injection. See https://docs.ray.io/en/latest/cluster/kubernetes/k8s-ecosystem/istio.html#step-3-optional-enable-istio-mtls-strict-mode Signed-off-by: Michael Fraenkel <929377+fraenkel@users.noreply.github.com>
3e4bcf7
to
e57c0c4
Compare
manifests/.github/workflows/pss_test.yaml
Lines 35 to 45 in 26d970d
@tarekabouzeid @kimwnasptd @DnPlas @kromanow94