Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
C
csusb-hpc
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
csusb-prp
csusb-hpc
Commits
2a3dac08
Commit
2a3dac08
authored
2 years ago
by
youngsuKim-CSUSB
Browse files
Options
Downloads
Patches
Plain Diff
Add nodeSelector
parent
9644ba9b
No related branches found
No related tags found
1 merge request
!13
Remove init container
Pipeline
#25731
passed
2 years ago
Stage: test
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
values.template.yaml
+33
-0
33 additions, 0 deletions
values.template.yaml
with
33 additions
and
0 deletions
values.template.yaml
+
33
−
0
View file @
2a3dac08
...
@@ -59,6 +59,39 @@ hub:
...
@@ -59,6 +59,39 @@ hub:
custom_spawn_pending_html
:
custom_spawn_pending_html
:
mountPath
:
/etc/jupyterhub/custom/spawn_pending.html
mountPath
:
/etc/jupyterhub/custom/spawn_pending.html
nodeSelector
:
topology.kubernetes.io/region
:
"
us-west"
kubernetes.io/hostname
:
"
perfsonar.csusb.edu"
# env: system
image
:
name
:
jupyterhub/k8s-hub
tag
:
'
1.2.0'
pullPolicy
:
'
'
pullSecrets
:
[]
livenessProbe
:
# The livenessProbe's aim to give JupyterHub sufficient time to startup but
# be able to restart if it becomes unresponsive for ~5 min.
enabled
:
true
initialDelaySeconds
:
300
periodSeconds
:
10
failureThreshold
:
30
timeoutSeconds
:
3
readinessProbe
:
# The readinessProbe's aim is to provide a successful startup indication,
# but following that never become unready before its livenessProbe fail and
# restarts it if needed. To become unready following startup serves no
# purpose as there are no other pod to fallback to in our non-HA deployment.
enabled
:
true
initialDelaySeconds
:
0
periodSeconds
:
2
failureThreshold
:
1000
timeoutSeconds
:
1
service
:
service
:
type
:
ClusterIP
type
:
ClusterIP
annotations
:
{}
annotations
:
{}
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment