-
Notifications
You must be signed in to change notification settings - Fork 710
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
update initialClusterVersion to 1.7.11-gke.1 #269
Conversation
- addressing kubeflow#268 - previously thought GCS read/write was also necessary for tensorflow/agents but does not appear to be the case so oauthScopes left unchanged.
Hi @cwbeitel. Thanks for your PR. I'm waiting for a kubernetes or tensorflow member to verify that this patch is reasonable to test. If it is, they should reply with I understand the commands that are listed here. 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. |
py/deploy.py
Outdated
@@ -45,7 +45,7 @@ def setup(args): | |||
], | |||
}, | |||
# TODO(jlewi): Stop pinning GKE version once 1.8 becomes the default. | |||
"initialClusterVersion": "1.8.1-gke.1", | |||
"initialClusterVersion": "1.7.11-gke.1", |
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.
We should be using 1.8. for CRD and GPU support.
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.
Cool it looks from gcloud container get-server-config
that '1.8.5-gke.0' and '1.8.4-gke.1' are the two 1.8+ versions supported. Preference?
but does not appear to be the case so oauthScopes left unchanged.
This change is