Cloned2Preserve
/
TrueChartsClone
mirror of https://github.com/truecharts/charts.git
1
0
Fork 0
Code
TrueChartsClone/charts/stable/jupyter/values.yaml

69 lines
2.2 KiB
YAML
Raw Normal View History

feat(jupyter): Add Jupyter (#3616) * Initial work for Jupyter notebook * Fixed some things I forgot to change from base * Added readme and changelog * Update charts/incubator/jupyter/values.yaml * Update charts/incubator/jupyter/values.yaml * remove autogenerated content * lint * fix persistence and service * Add some config options and try to fix permissions I added some of the config options supported by the container. I also tried to fix permissions by setting UID and GID, but this doesn't seem to have worked * Changed container to run as root I changed the pod security so that it would run as root in order for it to deploy with proper folder permissions. From my understanding while the pod is running as root the actual jupyter process is running as user 568 since I set the uid and gid to 568. * update IDs * some improvements * typo * update image repo * update questions * this is not needed, as users can select auto perms on persistance section * Update charts/incubator/jupyter/questions.yaml Signed-off-by: Stavros Kois <47820033+stavros-k@users.noreply.github.com> * Update charts/incubator/jupyter/Chart.yaml Signed-off-by: Stavros Kois <47820033+stavros-k@users.noreply.github.com> Signed-off-by: Stavros Kois <47820033+stavros-k@users.noreply.github.com> Co-authored-by: Kjeld Schouten-Lebbing <kjeld@schouten-lebbing.nl> Co-authored-by: Stavros Kois <47820033+stavros-k@users.noreply.github.com> Co-authored-by: Stavros kois <s.kois@outlook.com>
2022-09-18 06:47:51 -04:00
image:
repository: tccr.io/truecharts/jupyter-base
pullPolicy: IfNotPresent
chore(deps): update jupyter to v2023-06 (minor) (#9954)
2023-06-26 13:38:21 -04:00
tag: v2023-06@sha256:c8fa65de92ae1294d14c91ad62df0ca32441623941b74ec5c4fecc1819189437
fix(jupyter): fix image names
2023-01-07 06:55:04 -05:00
minimalImage:
feat(jupyter): Add Jupyter (#3616) * Initial work for Jupyter notebook * Fixed some things I forgot to change from base * Added readme and changelog * Update charts/incubator/jupyter/values.yaml * Update charts/incubator/jupyter/values.yaml * remove autogenerated content * lint * fix persistence and service * Add some config options and try to fix permissions I added some of the config options supported by the container. I also tried to fix permissions by setting UID and GID, but this doesn't seem to have worked * Changed container to run as root I changed the pod security so that it would run as root in order for it to deploy with proper folder permissions. From my understanding while the pod is running as root the actual jupyter process is running as user 568 since I set the uid and gid to 568. * update IDs * some improvements * typo * update image repo * update questions * this is not needed, as users can select auto perms on persistance section * Update charts/incubator/jupyter/questions.yaml Signed-off-by: Stavros Kois <47820033+stavros-k@users.noreply.github.com> * Update charts/incubator/jupyter/Chart.yaml Signed-off-by: Stavros Kois <47820033+stavros-k@users.noreply.github.com> Signed-off-by: Stavros Kois <47820033+stavros-k@users.noreply.github.com> Co-authored-by: Kjeld Schouten-Lebbing <kjeld@schouten-lebbing.nl> Co-authored-by: Stavros Kois <47820033+stavros-k@users.noreply.github.com> Co-authored-by: Stavros kois <s.kois@outlook.com>
2022-09-18 06:47:51 -04:00
repository: tccr.io/truecharts/jupyter-minimal
pullPolicy: IfNotPresent
chore(deps): update container image tccr.io/truecharts/jupyter-minimal to v2023-06 (#9956)
2023-06-26 14:38:37 -04:00
tag: v2023-06@sha256:8eddaeda7da981bbe72dd4c2732f2fd9f5745a005a4b218da129ac1140732291
fix(jupyter): fix image names
2023-01-07 06:55:04 -05:00
rImage:
feat(jupyter): Add Jupyter (#3616) * Initial work for Jupyter notebook * Fixed some things I forgot to change from base * Added readme and changelog * Update charts/incubator/jupyter/values.yaml * Update charts/incubator/jupyter/values.yaml * remove autogenerated content * lint * fix persistence and service * Add some config options and try to fix permissions I added some of the config options supported by the container. I also tried to fix permissions by setting UID and GID, but this doesn't seem to have worked * Changed container to run as root I changed the pod security so that it would run as root in order for it to deploy with proper folder permissions. From my understanding while the pod is running as root the actual jupyter process is running as user 568 since I set the uid and gid to 568. * update IDs * some improvements * typo * update image repo * update questions * this is not needed, as users can select auto perms on persistance section * Update charts/incubator/jupyter/questions.yaml Signed-off-by: Stavros Kois <47820033+stavros-k@users.noreply.github.com> * Update charts/incubator/jupyter/Chart.yaml Signed-off-by: Stavros Kois <47820033+stavros-k@users.noreply.github.com> Signed-off-by: Stavros Kois <47820033+stavros-k@users.noreply.github.com> Co-authored-by: Kjeld Schouten-Lebbing <kjeld@schouten-lebbing.nl> Co-authored-by: Stavros Kois <47820033+stavros-k@users.noreply.github.com> Co-authored-by: Stavros kois <s.kois@outlook.com>
2022-09-18 06:47:51 -04:00
repository: tccr.io/truecharts/jupyter-r
pullPolicy: IfNotPresent
chore(deps): update jupyter (#9912)
2023-06-25 22:00:36 -04:00
tag: v2023-06@sha256:50c60da5a6f62a9e4462a31046197d6bce4719a07c6b2c758e69994b7c06e9bc
fix(jupyter): fix image names
2023-01-07 06:55:04 -05:00
scipyImage:
feat(jupyter): Add Jupyter (#3616) * Initial work for Jupyter notebook * Fixed some things I forgot to change from base * Added readme and changelog * Update charts/incubator/jupyter/values.yaml * Update charts/incubator/jupyter/values.yaml * remove autogenerated content * lint * fix persistence and service * Add some config options and try to fix permissions I added some of the config options supported by the container. I also tried to fix permissions by setting UID and GID, but this doesn't seem to have worked * Changed container to run as root I changed the pod security so that it would run as root in order for it to deploy with proper folder permissions. From my understanding while the pod is running as root the actual jupyter process is running as user 568 since I set the uid and gid to 568. * update IDs * some improvements * typo * update image repo * update questions * this is not needed, as users can select auto perms on persistance section * Update charts/incubator/jupyter/questions.yaml Signed-off-by: Stavros Kois <47820033+stavros-k@users.noreply.github.com> * Update charts/incubator/jupyter/Chart.yaml Signed-off-by: Stavros Kois <47820033+stavros-k@users.noreply.github.com> Signed-off-by: Stavros Kois <47820033+stavros-k@users.noreply.github.com> Co-authored-by: Kjeld Schouten-Lebbing <kjeld@schouten-lebbing.nl> Co-authored-by: Stavros Kois <47820033+stavros-k@users.noreply.github.com> Co-authored-by: Stavros kois <s.kois@outlook.com>
2022-09-18 06:47:51 -04:00
repository: tccr.io/truecharts/jupyter-scipy
pullPolicy: IfNotPresent
chore(deps): update jupyter (#9912)
2023-06-25 22:00:36 -04:00
tag: v2023-06@sha256:c6a1d5e3e7223119683adf9ed37ba5c631be1b62d2057f0d5a0afe99c82ee9c3
fix(jupyter): fix image names
2023-01-07 06:55:04 -05:00
tensorflowImage:
feat(jupyter): Add Jupyter (#3616) * Initial work for Jupyter notebook * Fixed some things I forgot to change from base * Added readme and changelog * Update charts/incubator/jupyter/values.yaml * Update charts/incubator/jupyter/values.yaml * remove autogenerated content * lint * fix persistence and service * Add some config options and try to fix permissions I added some of the config options supported by the container. I also tried to fix permissions by setting UID and GID, but this doesn't seem to have worked * Changed container to run as root I changed the pod security so that it would run as root in order for it to deploy with proper folder permissions. From my understanding while the pod is running as root the actual jupyter process is running as user 568 since I set the uid and gid to 568. * update IDs * some improvements * typo * update image repo * update questions * this is not needed, as users can select auto perms on persistance section * Update charts/incubator/jupyter/questions.yaml Signed-off-by: Stavros Kois <47820033+stavros-k@users.noreply.github.com> * Update charts/incubator/jupyter/Chart.yaml Signed-off-by: Stavros Kois <47820033+stavros-k@users.noreply.github.com> Signed-off-by: Stavros Kois <47820033+stavros-k@users.noreply.github.com> Co-authored-by: Kjeld Schouten-Lebbing <kjeld@schouten-lebbing.nl> Co-authored-by: Stavros Kois <47820033+stavros-k@users.noreply.github.com> Co-authored-by: Stavros kois <s.kois@outlook.com>
2022-09-18 06:47:51 -04:00
repository: tccr.io/truecharts/jupyter-tensorflow
pullPolicy: IfNotPresent
chore(deps): update jupyter (#9912)
2023-06-25 22:00:36 -04:00
tag: v2023-06@sha256:75173cedf225891b2d12cb8421a8e976895efcb3c32c3a06a62c0e2ac61f9cce
fix(jupyter): fix image names
2023-01-07 06:55:04 -05:00
datascienceImage:
feat(jupyter): Add Jupyter (#3616) * Initial work for Jupyter notebook * Fixed some things I forgot to change from base * Added readme and changelog * Update charts/incubator/jupyter/values.yaml * Update charts/incubator/jupyter/values.yaml * remove autogenerated content * lint * fix persistence and service * Add some config options and try to fix permissions I added some of the config options supported by the container. I also tried to fix permissions by setting UID and GID, but this doesn't seem to have worked * Changed container to run as root I changed the pod security so that it would run as root in order for it to deploy with proper folder permissions. From my understanding while the pod is running as root the actual jupyter process is running as user 568 since I set the uid and gid to 568. * update IDs * some improvements * typo * update image repo * update questions * this is not needed, as users can select auto perms on persistance section * Update charts/incubator/jupyter/questions.yaml Signed-off-by: Stavros Kois <47820033+stavros-k@users.noreply.github.com> * Update charts/incubator/jupyter/Chart.yaml Signed-off-by: Stavros Kois <47820033+stavros-k@users.noreply.github.com> Signed-off-by: Stavros Kois <47820033+stavros-k@users.noreply.github.com> Co-authored-by: Kjeld Schouten-Lebbing <kjeld@schouten-lebbing.nl> Co-authored-by: Stavros Kois <47820033+stavros-k@users.noreply.github.com> Co-authored-by: Stavros kois <s.kois@outlook.com>
2022-09-18 06:47:51 -04:00
repository: tccr.io/truecharts/jupyter-datascience
pullPolicy: IfNotPresent
chore(deps): update jupyter to v2023-06 (minor) (#9954)
2023-06-26 13:38:21 -04:00
tag: v2023-06@sha256:64de96bed278d0f503adb9f9efbc51871b375ffc432ec0c22651ae8d15610b25
fix(jupyter): fix image names
2023-01-07 06:55:04 -05:00
pysparkImage:
update renovate
2023-01-07 06:03:14 -05:00
repository: tccr.io/truecharts/jupyter-pyspark
feat(jupyter): Add Jupyter (#3616) * Initial work for Jupyter notebook * Fixed some things I forgot to change from base * Added readme and changelog * Update charts/incubator/jupyter/values.yaml * Update charts/incubator/jupyter/values.yaml * remove autogenerated content * lint * fix persistence and service * Add some config options and try to fix permissions I added some of the config options supported by the container. I also tried to fix permissions by setting UID and GID, but this doesn't seem to have worked * Changed container to run as root I changed the pod security so that it would run as root in order for it to deploy with proper folder permissions. From my understanding while the pod is running as root the actual jupyter process is running as user 568 since I set the uid and gid to 568. * update IDs * some improvements * typo * update image repo * update questions * this is not needed, as users can select auto perms on persistance section * Update charts/incubator/jupyter/questions.yaml Signed-off-by: Stavros Kois <47820033+stavros-k@users.noreply.github.com> * Update charts/incubator/jupyter/Chart.yaml Signed-off-by: Stavros Kois <47820033+stavros-k@users.noreply.github.com> Signed-off-by: Stavros Kois <47820033+stavros-k@users.noreply.github.com> Co-authored-by: Kjeld Schouten-Lebbing <kjeld@schouten-lebbing.nl> Co-authored-by: Stavros Kois <47820033+stavros-k@users.noreply.github.com> Co-authored-by: Stavros kois <s.kois@outlook.com>
2022-09-18 06:47:51 -04:00
pullPolicy: IfNotPresent
chore(deps): update jupyter (#9912)
2023-06-25 22:00:36 -04:00
tag: v2023-06@sha256:f8d400a33b58634b899d96bc6969c70c685e1f513aa6510440237fa082843d31
fix(jupyter): fix image names
2023-01-07 06:55:04 -05:00
allsparkImage:
feat(jupyter): Add Jupyter (#3616) * Initial work for Jupyter notebook * Fixed some things I forgot to change from base * Added readme and changelog * Update charts/incubator/jupyter/values.yaml * Update charts/incubator/jupyter/values.yaml * remove autogenerated content * lint * fix persistence and service * Add some config options and try to fix permissions I added some of the config options supported by the container. I also tried to fix permissions by setting UID and GID, but this doesn't seem to have worked * Changed container to run as root I changed the pod security so that it would run as root in order for it to deploy with proper folder permissions. From my understanding while the pod is running as root the actual jupyter process is running as user 568 since I set the uid and gid to 568. * update IDs * some improvements * typo * update image repo * update questions * this is not needed, as users can select auto perms on persistance section * Update charts/incubator/jupyter/questions.yaml Signed-off-by: Stavros Kois <47820033+stavros-k@users.noreply.github.com> * Update charts/incubator/jupyter/Chart.yaml Signed-off-by: Stavros Kois <47820033+stavros-k@users.noreply.github.com> Signed-off-by: Stavros Kois <47820033+stavros-k@users.noreply.github.com> Co-authored-by: Kjeld Schouten-Lebbing <kjeld@schouten-lebbing.nl> Co-authored-by: Stavros Kois <47820033+stavros-k@users.noreply.github.com> Co-authored-by: Stavros kois <s.kois@outlook.com>
2022-09-18 06:47:51 -04:00
repository: tccr.io/truecharts/jupyter-all-spark
pullPolicy: IfNotPresent
chore(deps): update jupyter to v2023-06 (minor) (#9954)
2023-06-26 13:38:21 -04:00
tag: v2023-06@sha256:f76d9e0f56db226b75fa8134daddf0001e0221e0fafc2382ac2611d64b820e85
feat(jupyter): Add Jupyter (#3616) * Initial work for Jupyter notebook * Fixed some things I forgot to change from base * Added readme and changelog * Update charts/incubator/jupyter/values.yaml * Update charts/incubator/jupyter/values.yaml * remove autogenerated content * lint * fix persistence and service * Add some config options and try to fix permissions I added some of the config options supported by the container. I also tried to fix permissions by setting UID and GID, but this doesn't seem to have worked * Changed container to run as root I changed the pod security so that it would run as root in order for it to deploy with proper folder permissions. From my understanding while the pod is running as root the actual jupyter process is running as user 568 since I set the uid and gid to 568. * update IDs * some improvements * typo * update image repo * update questions * this is not needed, as users can select auto perms on persistance section * Update charts/incubator/jupyter/questions.yaml Signed-off-by: Stavros Kois <47820033+stavros-k@users.noreply.github.com> * Update charts/incubator/jupyter/Chart.yaml Signed-off-by: Stavros Kois <47820033+stavros-k@users.noreply.github.com> Signed-off-by: Stavros Kois <47820033+stavros-k@users.noreply.github.com> Co-authored-by: Kjeld Schouten-Lebbing <kjeld@schouten-lebbing.nl> Co-authored-by: Stavros Kois <47820033+stavros-k@users.noreply.github.com> Co-authored-by: Stavros kois <s.kois@outlook.com>
2022-09-18 06:47:51 -04:00
jupyter:
jupyter_cmd: lab
restartable: true
service:
main:
ports:
main:
port: 10300
feat(stable): BREAKING CHANGE migrate to new common part 1 (#7900) **Description** Part 1 of the migration to new common on the stable train. This basically breaks most/all charts requiring a reinstall on SCALE as well. Helm users shouldn't need a reinstall but could migrate their values.yaml modification manually besides backing-up and porting the databases. There be Dragons basically, as we obviously cannot 100% go over each-and-every single app in the stable train like we did in the enterprise train. **⚙️ Type of change** - [x] ⚙️ Feature/App addition - [x] 🪛 Bugfix - [x] ⚠️ Breaking change (fix or feature that would cause existing functionality to not work as expected) - [x] 🔃 Refactor of current code **🧪 How Has This Been Tested?** Via CI and manually validation in a lot of cases where the CI did not correctly check things. Additional catalog item creation tooling for local testing has been added as well. **📃 Notes:** There will be issues in the future but we should get as much working well as we can. **✔️ Checklist:** - [x] ⚖️ My code follows the style guidelines of this project - [x] 👀 I have performed a self-review of my own code - [x] #️⃣ I have commented my code, particularly in hard-to-understand areas - [x] 📄 I have made corresponding changes to the documentation - [x] ⚠️ My changes generate no new warnings - [x] 🧪 I have added tests to this description that prove my fix is effective or that my feature works - [x] ⬆️ I increased versions for any altered app according to semantic versioning **➕ App addition** If this PR is an app addition please make sure you have done the following. - [ ] 🪞 I have opened a PR on [truecharts/containers](https://github.com/truecharts/containers) adding the container to TrueCharts mirror repo. - [ ] 🖼️ I have added an icon in the Chart's root directory called `icon.png` --- _Please don't blindly check all the boxes. Read them and only check those that apply. Those checkboxes are there for the reviewer to see what is this all about and the status of this PR with a quick glance._
2023-04-11 06:07:17 -04:00
protocol: http
feat(jupyter): Add Jupyter (#3616) * Initial work for Jupyter notebook * Fixed some things I forgot to change from base * Added readme and changelog * Update charts/incubator/jupyter/values.yaml * Update charts/incubator/jupyter/values.yaml * remove autogenerated content * lint * fix persistence and service * Add some config options and try to fix permissions I added some of the config options supported by the container. I also tried to fix permissions by setting UID and GID, but this doesn't seem to have worked * Changed container to run as root I changed the pod security so that it would run as root in order for it to deploy with proper folder permissions. From my understanding while the pod is running as root the actual jupyter process is running as user 568 since I set the uid and gid to 568. * update IDs * some improvements * typo * update image repo * update questions * this is not needed, as users can select auto perms on persistance section * Update charts/incubator/jupyter/questions.yaml Signed-off-by: Stavros Kois <47820033+stavros-k@users.noreply.github.com> * Update charts/incubator/jupyter/Chart.yaml Signed-off-by: Stavros Kois <47820033+stavros-k@users.noreply.github.com> Signed-off-by: Stavros Kois <47820033+stavros-k@users.noreply.github.com> Co-authored-by: Kjeld Schouten-Lebbing <kjeld@schouten-lebbing.nl> Co-authored-by: Stavros Kois <47820033+stavros-k@users.noreply.github.com> Co-authored-by: Stavros kois <s.kois@outlook.com>
2022-09-18 06:47:51 -04:00
targetPort: 8888
persistence:
data:
enabled: true
mountPath: /home/jovyan/work
portal:
feat(stable): BREAKING CHANGE migrate to new common part 1 (#7900) **Description** Part 1 of the migration to new common on the stable train. This basically breaks most/all charts requiring a reinstall on SCALE as well. Helm users shouldn't need a reinstall but could migrate their values.yaml modification manually besides backing-up and porting the databases. There be Dragons basically, as we obviously cannot 100% go over each-and-every single app in the stable train like we did in the enterprise train. **⚙️ Type of change** - [x] ⚙️ Feature/App addition - [x] 🪛 Bugfix - [x] ⚠️ Breaking change (fix or feature that would cause existing functionality to not work as expected) - [x] 🔃 Refactor of current code **🧪 How Has This Been Tested?** Via CI and manually validation in a lot of cases where the CI did not correctly check things. Additional catalog item creation tooling for local testing has been added as well. **📃 Notes:** There will be issues in the future but we should get as much working well as we can. **✔️ Checklist:** - [x] ⚖️ My code follows the style guidelines of this project - [x] 👀 I have performed a self-review of my own code - [x] #️⃣ I have commented my code, particularly in hard-to-understand areas - [x] 📄 I have made corresponding changes to the documentation - [x] ⚠️ My changes generate no new warnings - [x] 🧪 I have added tests to this description that prove my fix is effective or that my feature works - [x] ⬆️ I increased versions for any altered app according to semantic versioning **➕ App addition** If this PR is an app addition please make sure you have done the following. - [ ] 🪞 I have opened a PR on [truecharts/containers](https://github.com/truecharts/containers) adding the container to TrueCharts mirror repo. - [ ] 🖼️ I have added an icon in the Chart's root directory called `icon.png` --- _Please don't blindly check all the boxes. Read them and only check those that apply. Those checkboxes are there for the reviewer to see what is this all about and the status of this PR with a quick glance._
2023-04-11 06:07:17 -04:00
open:
enabled: true
securityContext:
container:
readOnlyRootFilesystem: false
runAsNonRoot: false
runAsUser: 0
runAsGroup: 0
workload:
main:
podSpec:
containers:
main:
fix(apps): fix various issues (#8095)
2023-04-19 19:19:46 -04:00
imageSelector: image
feat(stable): BREAKING CHANGE migrate to new common part 1 (#7900) **Description** Part 1 of the migration to new common on the stable train. This basically breaks most/all charts requiring a reinstall on SCALE as well. Helm users shouldn't need a reinstall but could migrate their values.yaml modification manually besides backing-up and porting the databases. There be Dragons basically, as we obviously cannot 100% go over each-and-every single app in the stable train like we did in the enterprise train. **⚙️ Type of change** - [x] ⚙️ Feature/App addition - [x] 🪛 Bugfix - [x] ⚠️ Breaking change (fix or feature that would cause existing functionality to not work as expected) - [x] 🔃 Refactor of current code **🧪 How Has This Been Tested?** Via CI and manually validation in a lot of cases where the CI did not correctly check things. Additional catalog item creation tooling for local testing has been added as well. **📃 Notes:** There will be issues in the future but we should get as much working well as we can. **✔️ Checklist:** - [x] ⚖️ My code follows the style guidelines of this project - [x] 👀 I have performed a self-review of my own code - [x] #️⃣ I have commented my code, particularly in hard-to-understand areas - [x] 📄 I have made corresponding changes to the documentation - [x] ⚠️ My changes generate no new warnings - [x] 🧪 I have added tests to this description that prove my fix is effective or that my feature works - [x] ⬆️ I increased versions for any altered app according to semantic versioning **➕ App addition** If this PR is an app addition please make sure you have done the following. - [ ] 🪞 I have opened a PR on [truecharts/containers](https://github.com/truecharts/containers) adding the container to TrueCharts mirror repo. - [ ] 🖼️ I have added an icon in the Chart's root directory called `icon.png` --- _Please don't blindly check all the boxes. Read them and only check those that apply. Those checkboxes are there for the reviewer to see what is this all about and the status of this PR with a quick glance._
2023-04-11 06:07:17 -04:00
env:
NB_UID: "{{ .Values.securityContext.container.PUID }}"
NB_GID: "{{ .Values.securityContext.pod.fsGroup }}"
NB_UMASK: "{{ .Values.securityContext.container.UMASK }}"
# User Defined
DOCKER_STACKS_JUPYTER_CMD: "{{ .Values.jupyter.jupyter_cmd }}"
RESTARTABLE: '{{ ternary "yes" "no" .Values.jupyter.restartable }}'