* switching node-red chart to SatefulSet
* based on the persistent nature of this chart as well as [this discussion](https://github.com/helm/charts/issues/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>
Added the commented value to values.yaml
Documented the feature on the README
bump the chart version
Signed-off-by: Carlos Ravelo <ravelo.carlos@gmail.com>
details: if the `flows` setting is left unset, node-red will default the
files it creates for new flows to match the hostname of the container
it's running under. This hostname is dynamic and changes with a pod
restart. As a result changes made and persisted will be lost.
By defaulting the `flows` value to some static value, we ensure that the
changes will persist between pod restarts (assuming using persistent
storage)
Signed-off-by: Jeff Billimek <jeff@billimek.com>
* new chart [stable/node-red]
Signed-off-by: Jeff Billimek <jeff@billimek.com>
* TIL stable charts need to start from 1.0.0
Signed-off-by: Jeff Billimek <jeff@billimek.com>
* remediating label changes for new charts
Signed-off-by: Jeff Billimek <jeff@billimek.com>
Niklas Ravnsborg-GjertsenandKubernetes Prow Robot
Jeff BillimekandKubernetes Prow Robot
Carlos RaveloandKubernetes Prow Robot