Skip to content
This repository has been archived by the owner on Feb 22, 2022. It is now read-only.

[stable/node-red] node-red chart enhancements #12052

Merged
merged 6 commits into from
Mar 29, 2019

Conversation

billimek
Copy link
Collaborator

@billimek billimek commented Mar 10, 2019

What this PR does / why we need it:

  • based on the persistent nature of this chart, using a default strategy Type of 'Recreate' instead of 'RollingUpdate' - with an optional override
  • bumping node-red docker image to the latest stable version

Checklist

[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

  • DCO signed
  • Chart Version bumped
  • Variables are documented in the README.md

@helm-bot helm-bot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. Contribution Allowed If the contributor has signed the DCO or the CNCF CLA (prior to the move to a DCO). labels Mar 10, 2019
@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 10, 2019
@vsliouniaev
Copy link
Collaborator

@billimek
Copy link
Collaborator Author

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)

@vsliouniaev
Copy link
Collaborator

You will still get the same storage behaviour that you are looking for from StatefulSet - separate volumes will be used per pod

@helm-bot helm-bot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. Contribution Allowed If the contributor has signed the DCO or the CNCF CLA (prior to the move to a DCO). labels Mar 12, 2019
@helm-bot helm-bot added Contribution Allowed If the contributor has signed the DCO or the CNCF CLA (prior to the move to a DCO). size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Mar 12, 2019
@billimek
Copy link
Collaborator Author

Hi @vsliouniaev, I went ahead and included this change too.

@billimek
Copy link
Collaborator Author

/assign @unguiculus

@billimek
Copy link
Collaborator Author

/assign @davidkarlsen

@unguiculus
Copy link
Member

/hold
See #12047

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 25, 2019
* 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>
Signed-off-by: Jeff Billimek <jeff@billimek.com>
@helm-bot helm-bot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Mar 26, 2019
@billimek billimek changed the title [stable/node-red] switching node-red chart to SatefulSet [stable/node-red] node-red chart enhancements Mar 26, 2019
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)
@billimek
Copy link
Collaborator Author

/retest

@unguiculus
Copy link
Member

/hold cancel
/lgtm

@k8s-ci-robot k8s-ci-robot added lgtm Indicates that a PR is ready to be merged. and removed do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. labels Mar 29, 2019
@k8s-ci-robot
Copy link
Contributor

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot merged commit f5a751f into helm:master Mar 29, 2019
crackmac pushed a commit to crackmac/charts that referenced this pull request Mar 29, 2019
* 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>
crackmac pushed a commit to crackmac/charts that referenced this pull request Mar 29, 2019
* 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>
@billimek billimek deleted the node-red-statefulset branch April 1, 2019 00:43
devnulled pushed a commit to devnulled/charts that referenced this pull request Apr 25, 2019
* 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>
dermorz pushed a commit to dermorz/charts that referenced this pull request Apr 26, 2019
* 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>
goshlanguage pushed a commit to goshlanguage/charts that referenced this pull request May 17, 2019
* 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>
eyenx pushed a commit to eyenx/charts that referenced this pull request May 28, 2019
* 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>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. Contribution Allowed If the contributor has signed the DCO or the CNCF CLA (prior to the move to a DCO). lgtm Indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants