Kasm on Kubernetes + Agents on OpenStack: 'No resources are available' when starting workspaces

[vasartori]

Hello all,

I'm testing different ways to deploy Kasm to find which setup best fits my workloads. Currently, I’m running Kasm on top of Kubernetes, and the Kasm Docker Agents on OpenStack (not on the same Kubernetes network).

I’m able to access Kasm, and the agents are able to register with Kasm. Agents can also download the images.

However, when we try to start a workspace, the following message appears: "No resources are available". Looking at the Kasm Agent interface, we can see that there is no resource consumption on the instance.

In the pool configuration, I’m using the same values that I use when deploying under virtual machines — in that setup, everything works fine.

By the way, here is the autoscale configuration:

P.S.: Machines were launched with the following flavor:

+----------------------------+--------------------------------------+
| Field                      | Value                                |
+----------------------------+--------------------------------------+
| OS-FLV-DISABLED:disabled   | False                                |
| OS-FLV-EXT-DATA:ephemeral  | 0                                    |
| access_project_ids         | None                                 |
| description                | None                                 |
| disk                       | 30                                   |
| id                         | 122c5ee5-214f-4888-a12e-47edcb90c15b |
| name                       | xlarge                               |
| os-flavor-access:is_public | True                                 |
| properties                 |                                      |
| ram                        | 8192                                 |
| rxtx_factor                | 1.0                                  |
| swap                       | 0                                    |
| vcpus                      | 4                                    |
+----------------------------+--------------------------------------+

We are also using an open security group:

[j-travis]

Here is a guide that may help you diagnose the problem: https://kasmweb.com/docs/latest/guide/troubleshooting/no_resources_available.html