-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding Conda-Store to QHub #967
Conversation
Hello @costrouc, I will have a look and review this |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is just one thing I could find and I noticed that you used, var.conda-store-image
I couldn't spot its reference anywhere, and you seem to use that to retrieve the tag and name components from it
external-url = var.endpoint | ||
|
||
{% if cookiecutter.certificate.type == "existing" %} | ||
certificate-secret-name = "{{ cookiecutter.certificate.secret_name }}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will follow the same approach we did for clearml right? when using a provisioned certificate
...kiecutter.repo_directory }}/infrastructure/modules/kubernetes/services/conda-store/worker.tf
Show resolved
Hide resolved
...{ cookiecutter.repo_directory }}/infrastructure/modules/kubernetes/services/minio/outputs.tf
Show resolved
Hide resolved
Service Unavailable when deploying on GCP,
|
This must be because you are using an older Docker image for hub. It needs to include qhub-jupyterhub-theme v0.3.3 as is specified on main here. So you need to work out which tag of quansight/qhub-jupyterhub is needed to pick this up. In theory this is |
That might be the case Dan, thanks for the pointer |
Hi @costrouc , I just tested the deployment for this PR it seems that there might be some changes with the Jupyterhub docker image as the following error showed up during deployment:
Using the main one instead resulted in any issues. |
Hi @costrouc, by some reason the icons for some buttons are not showing up correctly |
Just finished testing, all seems fine with conda-store. I will proceed to test the minio port changes, then will test on GCP as well to confirm. My only concern is within the issue with the main jupyterhub image.. ps. Also, not sure about this one, but there might be a duplicate constraint somewhere in the postsql config: |
* FEAT: Add additional port to handle Minio object storage * Add missing vars * Update minio entrypoint and disable tls * Exclude traitlets config from pre-commit * Update conda-store minio service eternal endpoint Co-authored-by: viniciusdc <vinivdc2009@hotmail.com>
Per #987 minio is AGPLv3 which means might we can't include it. |
Changes:
This PR bring the new Conda-Store to QHub. In the process of adding Conda-Store we needed a database along with s3 storage. This requires adding the minio and postgres helm charts included in this PR.
Put an
x
in the boxes that applyTesting
Requires testing
In case you checked yes, did you write tests?