-
Notifications
You must be signed in to change notification settings - Fork 16.8k
[stable/node-red] node-red chart enhancements #12052
Conversation
Have you considered using https://kubernetes.io/docs/tutorials/stateful-application/basic-stateful-set/#parallel-pod-management? |
Hi @vsliouniaev, I have not. Is this something we should probably do when using StatefulSets? I would like to make sure that it wouldn't impede with using a block-storage like rook/ceph where you can't have the new pod trying to use the same storage as the old pod (this is a problem when using Deployments with the default RollingUpdate policy) |
You will still get the same storage behaviour that you are looking for from StatefulSet - separate volumes will be used per pod |
2d79739
to
dbe7ffa
Compare
Hi @vsliouniaev, I went ahead and included this change too. |
/assign @unguiculus |
/assign @davidkarlsen |
/hold |
* based on the persistent nature of this chart as well as [this discussion](helm#1863), migrating the chart to a StatefulSet instead of a deployment. As a result bumping the major version * bumping node-red docker image to the latest stable version * using volumeClaimTemplates for statefulSet Signed-off-by: Jeff Billimek <jeff@billimek.com>
Signed-off-by: Jeff Billimek <jeff@billimek.com>
dbe7ffa
to
b788297
Compare
Signed-off-by: Jeff Billimek <jeff@billimek.com>
Signed-off-by: Jeff Billimek <jeff@billimek.com>
…o node-red-statefulset * 'node-red-statefulset' of github.com:billimek/charts: Implemented the option to add a subPath when enabling persistence (helm#12517)
/retest |
/hold cancel |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: billimek, unguiculus The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
* switching node-red chart to SatefulSet * based on the persistent nature of this chart as well as [this discussion](helm#1863), migrating the chart to a StatefulSet instead of a deployment. As a result bumping the major version * bumping node-red docker image to the latest stable version * using volumeClaimTemplates for statefulSet Signed-off-by: Jeff Billimek <jeff@billimek.com> * using Parallel podManagementPolicy Signed-off-by: Jeff Billimek <jeff@billimek.com> * revert to Deployment and leverage strategy types Signed-off-by: Jeff Billimek <jeff@billimek.com> * hard-code replica count Signed-off-by: Jeff Billimek <jeff@billimek.com>
* switching node-red chart to SatefulSet * based on the persistent nature of this chart as well as [this discussion](helm#1863), migrating the chart to a StatefulSet instead of a deployment. As a result bumping the major version * bumping node-red docker image to the latest stable version * using volumeClaimTemplates for statefulSet Signed-off-by: Jeff Billimek <jeff@billimek.com> * using Parallel podManagementPolicy Signed-off-by: Jeff Billimek <jeff@billimek.com> * revert to Deployment and leverage strategy types Signed-off-by: Jeff Billimek <jeff@billimek.com> * hard-code replica count Signed-off-by: Jeff Billimek <jeff@billimek.com> Signed-off-by: Kevin Duane <duank001@apps.disney.com>
* switching node-red chart to SatefulSet * based on the persistent nature of this chart as well as [this discussion](helm#1863), migrating the chart to a StatefulSet instead of a deployment. As a result bumping the major version * bumping node-red docker image to the latest stable version * using volumeClaimTemplates for statefulSet Signed-off-by: Jeff Billimek <jeff@billimek.com> * using Parallel podManagementPolicy Signed-off-by: Jeff Billimek <jeff@billimek.com> * revert to Deployment and leverage strategy types Signed-off-by: Jeff Billimek <jeff@billimek.com> * hard-code replica count Signed-off-by: Jeff Billimek <jeff@billimek.com>
* switching node-red chart to SatefulSet * based on the persistent nature of this chart as well as [this discussion](helm#1863), migrating the chart to a StatefulSet instead of a deployment. As a result bumping the major version * bumping node-red docker image to the latest stable version * using volumeClaimTemplates for statefulSet Signed-off-by: Jeff Billimek <jeff@billimek.com> * using Parallel podManagementPolicy Signed-off-by: Jeff Billimek <jeff@billimek.com> * revert to Deployment and leverage strategy types Signed-off-by: Jeff Billimek <jeff@billimek.com> * hard-code replica count Signed-off-by: Jeff Billimek <jeff@billimek.com>
* switching node-red chart to SatefulSet * based on the persistent nature of this chart as well as [this discussion](helm#1863), migrating the chart to a StatefulSet instead of a deployment. As a result bumping the major version * bumping node-red docker image to the latest stable version * using volumeClaimTemplates for statefulSet Signed-off-by: Jeff Billimek <jeff@billimek.com> * using Parallel podManagementPolicy Signed-off-by: Jeff Billimek <jeff@billimek.com> * revert to Deployment and leverage strategy types Signed-off-by: Jeff Billimek <jeff@billimek.com> * hard-code replica count Signed-off-by: Jeff Billimek <jeff@billimek.com>
* switching node-red chart to SatefulSet * based on the persistent nature of this chart as well as [this discussion](helm#1863), migrating the chart to a StatefulSet instead of a deployment. As a result bumping the major version * bumping node-red docker image to the latest stable version * using volumeClaimTemplates for statefulSet Signed-off-by: Jeff Billimek <jeff@billimek.com> * using Parallel podManagementPolicy Signed-off-by: Jeff Billimek <jeff@billimek.com> * revert to Deployment and leverage strategy types Signed-off-by: Jeff Billimek <jeff@billimek.com> * hard-code replica count Signed-off-by: Jeff Billimek <jeff@billimek.com>
What this PR does / why we need it:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]