-
Notifications
You must be signed in to change notification settings - Fork 19
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
fix: Make the dynamic plugins root PVC storage class configurable [RHDHBUGS-156][RHIDP-5573] #69
fix: Make the dynamic plugins root PVC storage class configurable [RHDHBUGS-156][RHIDP-5573] #69
Conversation
…volumeClaimSpec` field in the values file This way, the whole PVC spec is configurable, including the storage class name, along with other things like the PVC size and access modes.
|
/cherry-pick release-1.3 Backport needed for 1.3 (https://issues.redhat.com/browse/RHIDP-5835) and 1.4 (https://issues.redhat.com/browse/RHIDP-5836) |
@rm3l: #69 failed to apply on top of branch "release-1.3":
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
…DHBUGS-156][RHIDP-5573] (redhat-developer#69) * Extract the dynamic plugins root PVC spec in a `dynamicPlugins.cache.volumeClaimSpec` field in the values file This way, the whole PVC spec is configurable, including the storage class name, along with other things like the PVC size and access modes. * Bump the Chart version * Extract the PostgreSQL PVC storageClass field to highlight that this configurable as well See https://github.com/bitnami/charts/blob/postgresql/12.10.0/bitnami/postgresql/README.md#postgresql-primary-parameters * Add test values file * Regenerate README
…DHBUGS-156][RHIDP-5573] (redhat-developer#69) * Extract the dynamic plugins root PVC spec in a `dynamicPlugins.cache.volumeClaimSpec` field in the values file This way, the whole PVC spec is configurable, including the storage class name, along with other things like the PVC size and access modes. * Bump the Chart version * Extract the PostgreSQL PVC storageClass field to highlight that this configurable as well See https://github.com/bitnami/charts/blob/postgresql/12.10.0/bitnami/postgresql/README.md#postgresql-primary-parameters * Add test values file * Regenerate README
…DHBUGS-156][RHIDP-5573] (redhat-developer#69) * Extract the dynamic plugins root PVC spec in a `dynamicPlugins.cache.volumeClaimSpec` field in the values file This way, the whole PVC spec is configurable, including the storage class name, along with other things like the PVC size and access modes. * Bump the Chart version * Extract the PostgreSQL PVC storageClass field to highlight that this configurable as well See https://github.com/bitnami/charts/blob/postgresql/12.10.0/bitnami/postgresql/README.md#postgresql-primary-parameters * Add test values file * Regenerate README
…DHBUGS-156][RHIDP-5573] (redhat-developer#69) * Extract the dynamic plugins root PVC spec in a `dynamicPlugins.cache.volumeClaimSpec` field in the values file This way, the whole PVC spec is configurable, including the storage class name, along with other things like the PVC size and access modes. * Bump the Chart version * Extract the PostgreSQL PVC storageClass field to highlight that this configurable as well See https://github.com/bitnami/charts/blob/postgresql/12.10.0/bitnami/postgresql/README.md#postgresql-primary-parameters * Add test values file * Regenerate README
…DHBUGS-156][RHIDP-5573] (#69) (#80) * Extract the dynamic plugins root PVC spec in a `dynamicPlugins.cache.volumeClaimSpec` field in the values file This way, the whole PVC spec is configurable, including the storage class name, along with other things like the PVC size and access modes. * Bump the Chart version * Extract the PostgreSQL PVC storageClass field to highlight that this configurable as well See https://github.com/bitnami/charts/blob/postgresql/12.10.0/bitnami/postgresql/README.md#postgresql-primary-parameters * Add test values file * Regenerate README
…DHBUGS-156][RHIDP-5573] (redhat-developer#69) * Extract the dynamic plugins root PVC spec in a `dynamicPlugins.cache.volumeClaimSpec` field in the values file This way, the whole PVC spec is configurable, including the storage class name, along with other things like the PVC size and access modes. * Bump the Chart version * Extract the PostgreSQL PVC storageClass field to highlight that this configurable as well See https://github.com/bitnami/charts/blob/postgresql/12.10.0/bitnami/postgresql/README.md#postgresql-primary-parameters * Add test values file * Regenerate README
…DHBUGS-156][RHIDP-5573] (#69) (#90) * Extract the dynamic plugins root PVC spec in a `dynamicPlugins.cache.volumeClaimSpec` field in the values file This way, the whole PVC spec is configurable, including the storage class name, along with other things like the PVC size and access modes. * Bump the Chart version * Extract the PostgreSQL PVC storageClass field to highlight that this configurable as well See https://github.com/bitnami/charts/blob/postgresql/12.10.0/bitnami/postgresql/README.md#postgresql-primary-parameters * Add test values file * Regenerate README
Description of the change
This PR extracts the dynamic plugins root PVC spec in a new
dynamicPlugins.cache.volumeClaimSpec
field in the values file.This way, the whole PVC spec is configurable, including the storage class name, along with other things like the PVC size and access modes.
This should also help with https://issues.redhat.com/browse/RHIDP-5516 (make it possible to disable the dynamic plugin cache PVC and switch to an ephemeral volume).
Existing or Associated Issue(s)
Additional Information
Checklist
Chart.yaml
according to semver.values.yaml
and added to the README.md. The pre-commit utility can be used to generate the necessary content. Usepre-commit run -a
to apply changes.pre-commit
hook.ct lint
command.