Conversation
Document Remote clusters configuration
Co-authored-by: Alessandro Degano <40891147+aledegano@users.noreply.github.com>
|
|
||
| _If you already have automatic volume provisioning setup in your cluster, you may skip this._ | ||
|
|
||
| For example, to install cinder-csi: |
There was a problem hiding this comment.
Remove the example as it is:
- Very specific
- Probably not complete, as it is missing authentication necessary for the node plugin to cinder
Instead, I would suggest to simply list a few, example, storageclasses commonly used (cinder-csi, azure etc...)
There was a problem hiding this comment.
As discussed yesterday, I just removed the example, as this is too specific to the cloud provider, and it makes no sense to document multiple ways of achieving the same things.
The cloud provider documentation should take care of that, and we won't be able to keep up to date with these anyway.
| - [ ] Dedicated **Namespace** for the user sessions (for example `renku-user-sessions`) | ||
| - [ ] Dedicated **ServiceAccount** (for example `renku-session-manager`) with the following rights | ||
|
|
||
| ```yaml |
There was a problem hiding this comment.
This role, along with a SA and the RoleBinding should go in the chart, no reason for the admins to have to create it out-of-band.
There was a problem hiding this comment.
Applied in SwissDataScienceCenter/amalthea#1088, and adapted the documentation here.
There was a problem hiding this comment.
The problem is that this has very little to do with either Amalthea or the full Renku deployment. So it can go in a separate helm chart. But for now the easiest is to manage it out of band.
| Here as an example on how to create one, adapt as required: | ||
|
|
||
| - ```bash | ||
| kubectl create priorityclass renku-user-sessions-priority --value=1000 --description="default priority for renku sessions" |
There was a problem hiding this comment.
This should go in the helm chart, possibly with opt-out, no need to have admins manage this out-of-band.
There was a problem hiding this comment.
Applied in SwissDataScienceCenter/amalthea#1088, and updated the documentation
There was a problem hiding this comment.
Lets just start with managing this out of band. We can adapt it later. With the elimination of CSI rclone things will be easier. And if we add this to the amalthea helm chart then we need to document really well what it is for.
Address comment by removing the example, as this is too specific to the cloud provider.
comments about priority class and the service account, tied to SwissDataScienceCenter/amalthea#1088
3 participants
Document Remote clusters configuration