[Core][Serve] Support TailScale VPN #3458
Draft
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.
A revised version of #3276. If VPN is enabled, does not provision public IP for the cluster and use VPN Private IP.
TODO:
[to discuss] Maybe does not use Private IP in VPN to setup SkyPilot runtime env as it needs to wait until instance is upAfter discussion, we decided to go the current implementation.sky stop
+sky start
[to discuss] show use VPN or not inAfter discussion, we decided to skip it for now.sky status
Tested (run the relevant ones):
bash format.sh
All of the following is with this skypilot config, and client joined the VPN:
pytest tests/test_smoke.py
pytest tests/test_smoke.py::test_fill_in_the_name
bash tests/backward_comaptibility_tests.sh