SkyPilot: Run AI and batch jobs on any infra (Kubernetes or 12+ clouds). Get unified execution, cost savings, and high GPU availability via a simple interface.
Recently added in https://github.com/skypilot-org/skypilot/issues/1354, we can specify the default security_group_name for aws resources. However, when launching serve, there are two conflicts which occur between the serve config requirements and the sky config requirements:
The serve resources requires a port in the serve config.
ValueError: Must only specify one port in resources. Each replica will use the port specified as application ingress port.
Security group names cannot be referenced if port is in a resource.
ValueError: Cannot specify ports when AWS security group name is specified.
This could be resolved by allowing the serve config to specify the security_group_name for the resource as well.
Moreover, it would be ideal to be able to specify different security groups for the head and worker nodes as ray already provides this capability.
Recently added in https://github.com/skypilot-org/skypilot/issues/1354, we can specify the default
security_group_name
for aws resources. However, when launching serve, there are two conflicts which occur between the serve config requirements and the sky config requirements:port
in the serve config.port
is in a resource.This could be resolved by allowing the serve config to specify the
security_group_name
for the resource as well.Moreover, it would be ideal to be able to specify different security groups for the head and worker nodes as ray already provides this capability.
Thanks!