Vinicius D. Cerutti
Vinicius D. Cerutti
This seems to be probably related to a Kubernetes version update in the cloud providers side, as a recent issue encountered the same problem with qhub-3.14. #1163
@costrouc @iameskild this error doesn't seem to show up anymore, has anyone spotted this recently?
This happened again this week. Not sure what caused but the conda-store mounts were affecting the dask-gateway pod spawning this time. I followed the fix suggested by @costrouc of resetting...
For now, this will need to be added to the FAQ of Nebari with instructions on how to reset the general node
Hi @HarshCasper, this issue normally happens when: - The first deployment did not fully complete, more specifically Keycloak is not in a running state - Or, when you run `qhub...
> I also had `qhub destroy` on GCP fail for me (v0.4.3). This was the end of my logs: > > ``` > [terraform]: Destroy complete! Resources: 1 destroyed. >...
@costrouc Tokens and the above configuration were all completed. I am working on a basic function to call the API.
It needs to be tested with `QHUB_IMAGE_TAG=sha-563ef5c` for the docker images, waiting for 0.4.4 release.
Blocked by https://github.com/ideonate/cdsdashboards/issues/107, I was able to test this locally, though lets-encrypt didn't want to cooperate providing a valid cert... so I was unable to properly "see" the dashboard. Still,...
This is ready for review, when testing please be sure to use the latest available image from main