Adding onto what Greg said, the new computer server pod will try to instantiate a sas-programming-environment container. Due to the size of the container, it takes a long time to download the container to a node if it is not already present. The error you are seeing may be because the creation of the container is longer than the compute service is willing to wait (usually 60 seconds).
To get around this problem, the sas-prepull service will make sure sas-programming-environment containers are pre-downloaded to all nodes that have the "workload.sas.com/class=compute" label on the Kubernetes node.
So you can either keep retrying the context in SAS/Studio until the container is fully downloaded to a node or label the node so that the sas-prepull service will put the container on the node for you.
... View more