README needs an update

[edan-bainglass]

Collecting notes here from recent tests by myself and @mikibonacci to be used in a follow up PR to update the docs

[edan-bainglass]

The SSH key needs to be at least 2048 bit. At least on my WSL system, the default behavior was far less. The following did the trick:

ssh-keygen -t rsa -b 4096 -f ~/.ssh/<ssh-key-name> -N ""

[mikibonacci]

(1)DNS issue (the page is loading but blank):

• first, deploy with https: enabled: false, then bind the external IP (i.e. kubectl get svc -n $namespace… and get the proxy.public external IP + creating an additional DNS address in aiidalab.io Recordsets - type A, 300 seconds)… then ping the DNS until it is reachable (try to ping also the IP, and to access the IP in google private browsing mode)
• then, deploy again with enabled: true
• Remember to set the github app! in aiidalab repo -> developer settings -> OAuth apps

(2) Insufficient CPU to spin up a user page

• The issue I had with the insufficient CPUs when logging in was that actually the VM of the nodes is of type Standard_D2s_v3 (https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/general-purpose/dsv3-series?tabs=sizebasic#sizes-in-series), which has a max of 2 vCPUs and 8 GB of Ram. I cannot provide 2CPUs per user, as the machine has only 2 CPUs. If the user needs more resources, we need larger VM. In the demo-server, the nodes are divided into two pools (one for system and one for users, the first not scaling, at variance with the second pool), and machines are actually Standard_D8s_v5. In this way, we can accomodate more than one user per VM with more resources.
  NOTE: if you change the VM model, maybe you need to recreate the hub storage (delete and deploy), if you get errors like inconsistent volume.

(3) limit user pods to a given nodepool on azure. in the values.yaml, under both singleuser and hub:

nodeSelector:
            agentpool: users