-
Notifications
You must be signed in to change notification settings - Fork 549
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
[k8s] Use SERVICE_ACCOUNT
as default remote_identity, add checks for autodown support
#3527
Conversation
… LOCAL_CREDENTIALS
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.
Thanks for fixing this @romilbhardwaj! Mostly look good to me except for the name of the feature. We may want to generalize it a bit instead of limiting it to autodown.
sky/clouds/cloud.py
Outdated
@@ -43,6 +43,7 @@ class CloudImplementationFeatures(enum.Enum): | |||
OPEN_PORTS = 'open_ports' | |||
STORAGE_MOUNTING = 'storage_mounting' | |||
HOST_CONTROLLERS = 'host_controllers' # Can run jobs/serve controllers | |||
AUTODOWN = 'autodown' |
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.
How about we just call it AUTOSTOP
or AUTO_TEARDOWN
as autostop and autodown should have similar requirements for the cloud to 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.
Between these two options, I'll change it to AUTO_TEARDOWN
since it would be confusing for a cloud (Kubernetes) to have AUTOSTOP
but not STOP
feature.
Thanks for the comments @Michaelvll!
|
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.
Thanks @romilbhardwaj! LGTM with a fix for the auto_terminate setting.
Co-authored-by: Zhanghao Wu <[email protected]>
Makes
SERVICE_ACCOUNT
default remote identity for Kubernetes. This helps with lesser config required for exec based clusters (GKE), and does not cause issues since we anyway need to create an SA for the ssh jump pod.Also adds checks for autodown support, and disable autodown when using exec based auth with
LOCAL_CREDENTIALS
on Kubernetes clusters.bash format.sh
pytest -v tests/test_smoke.py::test_autodown
pytest -v tests/test_smoke.py::test_autodown --kubernetes
sky serve up -n http http_server.yaml
and verify autodown afterwards