-
Notifications
You must be signed in to change notification settings - Fork 7.6k
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 #588
[DO NOT MERGE] Auto PR to update dependencies of istio #588
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: Assign the PR to them by writing 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 |
@istio-testing: The following tests failed, say
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. |
Automatic merge from submit-queue Periodic Prow Job to Update Istio Dependency SHA An example PR created is istio/istio#588 Notice that it reads SHA from stable branch of each dependency. For the entire dependency update scheme to be automated, it also needs the fast-forward jobs that move stable up-to-date with master, which will be done in another PR shortly after. **Release note**: ```release-note NONE ```
Former-commit-id: 443146a991e1065f2ff880856a31943b30df26bf
Former-commit-id: 16405a990550596c8aa35c31a7586ab9f54c7a8f
* update egress proxy * add cds test * address comments
Automatic merge from submit-queue Periodic Prow Job to Update Istio Dependency SHA An example PR created is istio/istio#588 Notice that it reads SHA from stable branch of each dependency. For the entire dependency update scheme to be automated, it also needs the fast-forward jobs that move stable up-to-date with master, which will be done in another PR shortly after. **Release note**: ```release-note NONE ```
* Move gateway and coredns enablement in sample config * Update assets
This PR will be merged automatically once checks are successful.