Update ambassador and statsd to 0.30.1 as part of 0.1 release #513
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Deployed kubeflow on a new cluster and tested new ambassador by deploying an inception model and routing traffic through ambassador Related to #506
|
/cc @jlewi |
|
Looks like there was a jsonnet failure. |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jlewi The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
yanniszark
pushed a commit
to arrikto/kubeflow
that referenced
this pull request
Nov 1, 2019
…ents (kubeflow#513) * On GCP use BackendConfig to set the backend timeout and other improvements. * As of GKE 1.13 we can now set the backend timeout using a BackendConfig https://cloud.google.com/kubernetes-engine/docs/how-to/configure-backend-service * BasicAuth doesn't have a backendconfig so we need to add one. * In BasicAuth we are still using Ambassador to handle the auth. * Improve the setup_backend.sh script for IAP * This script is only updating the JWT based on IAP; there's no reason the script should be checking if the backend timeout is set. * Make the script run for ever to avoid confusing container restarts * Related to kubeflow#4269 backend timeout not set * Related to kubeflow#4043 crash looping of iap enabler and backend_updater pods. * Update tests. * Update Ambassador test.
saffaalvi
pushed a commit
to StatCan/kubeflow
that referenced
this pull request
Feb 11, 2021
…ow#513) * Update ambassador and statsd to 0.30.1 as part of 0.1 release Deployed kubeflow on a new cluster and tested new ambassador by deploying an inception model and routing traffic through ambassador Related to kubeflow#506 * Fix jsonnet test
elenzio9
pushed a commit
to arrikto/kubeflow
that referenced
this pull request
Oct 31, 2022
Co-authored-by: hackerboy01 <penglei031303@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Deployed kubeflow on a new cluster and tested new ambassador by
deploying an inception model and routing traffic through ambassador
Related to #506
This change is