Operating system
Fedora release 44 (Forty Four)
Helmfile Version
1.5.0
Helm Version
3.20.1
Bug description
Previously when using trackMode: kubedog you would get a bunch of status lines printed out while kubedog was watching the deploy, e.g.
Tracking 30 resources from release sb-486457667 with kubedog
Tracking 30 resources with kubedog (filtered from 30 total)
Tracking breakdown: Deployments=3, StatefulSets=2, DaemonSets=0, Jobs=0, Canaries=0
DEPLOYMENT REPLICAS AVAILABLE UP-TO-DATE
│ sb-486457667-myapp-temporal-worker 3/2 2 1
│ │ POD READY RESTARTS STATUS ---
│ ├── 486457667-myapp-tempora 0/1 2 RunContainerError Waiting for: up-to-date 1->2, replicas 3->2
│ │ l-worker-6878cc7977-t2btv
│ ├── 486457667-myapp-tempora 1/1 0 Running
│ │ l-worker-7c798f8bf5-fcfnd
│ └── 486457667-myapp-tempora 1/1 0 Running
│ l-worker-7c798f8bf5-rddv6
However after upgrading to helmfile 1.5.0 I no longer see these messages, just the following
Found 30 resources in manifest for release sb-486457667
Tracking 30 resources from release sb-486457667 with kubedog
Tracking 30 resources with kubedog (filtered from 30 total)
Tracking breakdown: stss=2, deploys=3
All resources tracked successfully
UPDATED RELEASES:
This also means that trackLogs is useless as this output isn't shown either
Example helmfile.yaml
name: myapp
namespace: myapp
createNamespace: true
chart: ./charts/myapp
values:
myapp-values.yaml.gotmpl
disableValidationOnInstall: true
trackMode: kubedog
trackTimeout: 300 # seconds
trackLogs: true
Error message you've seen (if any)
None
Steps to reproduce
Create helmfile with kubedog tracking. Apply it, note that no kubedog status messages are shown
Working Helmfile Version
1.4.4
Relevant discussion
No response
Operating system
Fedora release 44 (Forty Four)
Helmfile Version
1.5.0
Helm Version
3.20.1
Bug description
Previously when using
trackMode: kubedogyou would get a bunch of status lines printed out while kubedog was watching the deploy, e.g.However after upgrading to helmfile 1.5.0 I no longer see these messages, just the following
This also means that
trackLogsis useless as this output isn't shown eitherExample helmfile.yaml
Error message you've seen (if any)
None
Steps to reproduce
Create helmfile with kubedog tracking. Apply it, note that no kubedog status messages are shown
Working Helmfile Version
1.4.4
Relevant discussion
No response