Skip to content
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

[DO NOT MERGE] Auto PR to update dependencies of istio #688

Closed

Conversation

istio-testing
Copy link
Collaborator

This PR will be merged automatically once checks are successful.

@istio-merge-robot
Copy link

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
We suggest the following additional approver: andraxylia

Assign the PR to them by writing /assign @andraxylia in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these OWNERS Files:

You can indicate your approval by writing /approve in a comment
You can cancel your approval by writing /approve cancel in a comment

@istio-testing
Copy link
Collaborator Author

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name Commit Details Rerun command
prow/e2e-suite-rbac-no_auth.sh eedd4a2 link /test e2e-suite-rbac-no_auth
prow/e2e-suite-no_rbac-no_auth.sh eedd4a2 link /test e2e-suite-no_rbac-no_auth

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/test-infra repository. I understand the commands that are listed here.

@rshriram rshriram closed this Sep 7, 2017
@rshriram rshriram deleted the autoUpdateDeps_b464ff7fad4122567a7c086291fc70a2 branch September 12, 2017 02:36
howardjohn added a commit to howardjohn/istio that referenced this pull request Jan 12, 2020
We cannot be cloning from github blindly, as this will break our private
security builds. This PR adds an option to pass an INSTALLER_DIR option
to the scripts and skip the cloning. Additionally, do not run vfsgen
when you do docker build. This should be an explicit step, otherwise the
code magically changes during a build and you spend all day debugging
it.
luksa added a commit to luksa/istio that referenced this pull request Apr 11, 2024
…Istio CNI (istio#688)

* [cni] MAISTRA-2132 Support deployment of multiple plugin versions in Istio CNI (istio#271)

Includes:

  * MAISTRA-2135 Add unit tests for our CNI binary-prefix work (istio#325)

  * MAISTRA-2137 Make network namespace setup executable name configurable (istio#273)

    To support the deployment of multiple CNI plugin versions, the name of the
    executable that is invoked to set up the network namespace must be configurable.

  * OSSM-1430: CNI: Watch for modified files with a prefix (istio#510)

    Because our CNI pod contains more than one container, and they write to
    the same directory, and they watch for changes on those directories,
    changes made by one container trigger the watch on the other, which will
    responde by copying the files to the directory, which will in turn
    trigger the watcher of the other container in an endless loop.

    This leads to high CPU usage on the node.

    This PR changes the logic to only monitor for files that have the
    desired prefix. Thus, for example, the 2.2 container will only react to
    changes to files whose names  start with "v2-2". This avoid this race
    condition and achieve the same end result.

* [cni] MAISTRA-2051 use correct UID/GID in istio-iptables

* OSSM-2082 CNI installer now creates the net.d directory if necessary (istio#638)

* fix(lint): replaces deprecated pkg io/ioutil

* fix: reverts back to t.TempDir() calls

Co-authored-by: Marko Lukša <marko.luksa@gmail.com>
Co-authored-by: rcernich <rcernich@redhat.com>
dgn pushed a commit to dgn/istio that referenced this pull request Jun 13, 2024
…Istio CNI (istio#688)

* [cni] MAISTRA-2132 Support deployment of multiple plugin versions in Istio CNI (istio#271)

Includes:

  * MAISTRA-2135 Add unit tests for our CNI binary-prefix work (istio#325)

  * MAISTRA-2137 Make network namespace setup executable name configurable (istio#273)

    To support the deployment of multiple CNI plugin versions, the name of the
    executable that is invoked to set up the network namespace must be configurable.

  * OSSM-1430: CNI: Watch for modified files with a prefix (istio#510)

    Because our CNI pod contains more than one container, and they write to
    the same directory, and they watch for changes on those directories,
    changes made by one container trigger the watch on the other, which will
    responde by copying the files to the directory, which will in turn
    trigger the watcher of the other container in an endless loop.

    This leads to high CPU usage on the node.

    This PR changes the logic to only monitor for files that have the
    desired prefix. Thus, for example, the 2.2 container will only react to
    changes to files whose names  start with "v2-2". This avoid this race
    condition and achieve the same end result.

* [cni] MAISTRA-2051 use correct UID/GID in istio-iptables

* OSSM-2082 CNI installer now creates the net.d directory if necessary (istio#638)

* fix(lint): replaces deprecated pkg io/ioutil

* fix: reverts back to t.TempDir() calls

Co-authored-by: Marko Lukša <marko.luksa@gmail.com>
Co-authored-by: rcernich <rcernich@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants