Skip to content
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

feat(helm): add support for providing additional volumes and adding init containers #455

Closed
wants to merge 2 commits into from

Conversation

jnels124
Copy link
Contributor

@jnels124 jnels124 commented Jun 21, 2023

Pull Request template

Please, go through these steps before you submit a PR.

Why is this PR required? What issue does it fix?:
Adds support for additional volumes and init containers
What this PR does?:
Updates deployment yaml to support volume and init container config via values.yaml

Does this PR require any upgrade changes?:
No

If the changes in this PR are manually verified, list down the scenarios covered::
deployed helm chart with various init containers and additional volumes.
Verified init containers executed correctly.

Any additional information for your reviewer? :

Checklist:

Signed-off-by: Jesse Nelson <jesse@swirldslabs.com>
@niladrih
Copy link
Member

Why is this change required?

@jnels124
Copy link
Contributor Author

@niladrih This is required for our usecase because we would like to automatically bootstrap the nodes with the setup required for zfs. Currently, we are doing this via a daemon set that runs an init container and then a pause container(simply because a container is required). It would be simpler if we could just specify an init container to run within the node and controller deployments.

@@ -38,6 +38,13 @@ spec:
priorityClassName: {{ template "zfslocalpv.zfsController.priorityClassName" . }}
{{- end }}
serviceAccount: {{ .Values.serviceAccount.zfsController.name }}
{{- if .Values.zfsController.initContainers }}

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should add initContainers and additionalVolumes to values.yaml with [] default.

Signed-off-by: Jesse Nelson <jesse@swirldslabs.com>
@niladrih
Copy link
Member

These changes have been included in #461, closing this one. This is available in the released version v2.3.0.

@niladrih niladrih closed this Jul 29, 2023
@jnels124
Copy link
Contributor Author

These changes were added to 2.3

@jnels124 jnels124 deleted the init-container branch February 20, 2024 20:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support additional Volumes and Init containers for helm install
3 participants