-
Notifications
You must be signed in to change notification settings - Fork 176
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
Remove IP_FAMILY env in favor of IP_FAMILIES #5572
Conversation
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.
keep DNM until istio/istio.io#16174 (review) merges. istio one already merged
Signed-off-by: Faseela K <[email protected]>
@sridhargaddam : I see usage of IP_FAMILY in sail-operator jobs, I have not explored how it is being used, feel free to change it if sail-operator wants to follow similar IP_FAMILIES approach |
0b9a748
to
c1c9e48
Compare
Signed-off-by: Faseela K <[email protected]>
Yes @kfaseela. I've taken care of it in Sail Operator itself without having to update the test-infra |
@kfaseela: Updated the
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Does this require a change? https://github.com/istio/test-infra/blob/master/prow/config/jobs/sail-operator.yaml#L50 |
|
To be merged once istio/istio#54421 is merged