Question: Upgrading chart does not redeploy logging containers

Hi,

I am trying to upgrade the splunk connector release using the following helm command:

helm upgrade --tiller-namespace splunk-connect-k8s splunk-connect-k8s -f values.yaml custom-splunk-connect-for-kubernetes.tgz

Everytime I redeploy it creates new containers for the metrics and meta aspects of the release but it never redeploys the kubernetes logging and I need this to redeploy as well.

splunk-eks (develop) $ k get pods
NAME                                                              READY   STATUS    RESTARTS   AGE
splunk-connect-k8s-splunk-kubernetes-logging-ltrt7                1/1     Running   0          98m
splunk-connect-k8s-splunk-kubernetes-logging-p7snv                1/1     Running   0          102m
splunk-connect-k8s-splunk-kubernetes-logging-zddff                1/1     Running   0          102m
splunk-connect-k8s-splunk-kubernetes-metrics-49nlm                1/1     Running   0          42s
splunk-connect-k8s-splunk-kubernetes-metrics-agg-cc79cfcdbt62rg   1/1     Running   0          63s
splunk-connect-k8s-splunk-kubernetes-metrics-g8wqp                1/1     Running   0          50s
splunk-connect-k8s-splunk-kubernetes-metrics-kwdlr                1/1     Running   0          28s
splunk-connect-k8s-splunk-kubernetes-objects-84b4c9596c-drrjn     1/1     Running   0          63s
tiller-deploy-66fb8fc48c-x2wcn                                    1/1     Running   0          102m

Is there a reason why the logging pods do not redeploy and what do I need to do to get them to redeploy?

[matthewmodestino]

Why would you change the release name? Helm tracks in revisions of the release.

Please take a look at how fluentd does checkpointing:

https://docs.fluentd.org/input/tail

[rockb1017]

the logging pod keeps the record of positions where it has send to splunk, so once it gets restarted, it will pick up from where it left off.