-
Notifications
You must be signed in to change notification settings - Fork 0
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
Use helm values to parameterize dev settings #9
base: main
Are you sure you want to change the base?
Conversation
We want these to be managed by helm instead of manually running the `kubectl apply...` commands
Now the PV can get computed dynamically in dev. By default, the PV will be created with a hostpath that's in the root of this project. The user can override that behavior through the use of the `OGDC_PV_HOST_PATH` envvar.
Make clear this resoruce is only used in dev
Let this be managed by helm. Still TODO: require that the password/username be passed in at install-time or pull from some secrets store that ADC/NSIDC have joint access to. Is there something already in place on the ADC k8s?
c9cd456
to
e06d98f
Compare
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 config has a hard-coded username and password, which I would like to remove. These should be required values provided at helm-execution time.
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.
@@ -1,12 +1,14 @@ | |||
{{ if eq .Values.ENV "dev" }} |
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.
We'll only apply this PV in dev. In non-dev environments on the ADC k8s cluster, the already-configured CephFS-based PV will be used. Reference on that here: https://github.com/DataONEorg/k8s-cluster/blob/main/storage/storage.md
Resolves #3
This same approach can be extended to support non-dev environments. E.g., I would like to update the PVC yaml with whatever config is necessary to enable utilization of the CephFS on the ADC k8s.