You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I always get the following in the logs of any backup pod: [controller-runtime] log.SetLogger(...) was never called; logs will not be displayed. The backup pods are always successful and the data is actually backed up, but they always print this this trackback and I don't know why? Nothing is broken, just a bit confusing.
Additional Context
I'm using s3 as my backend and B2 as the remote s3 provider. All is working there fine. Again, none of this breaks anything. It just causes weird log messages that I don't understand. Thanks for any help you can provide and thanks for continuing to maintain this project!
Description
I always get the following in the logs of any backup pod:
[controller-runtime] log.SetLogger(...) was never called; logs will not be displayed.
The backup pods are always successful and the data is actually backed up, but they always print this this trackback and I don't know why? Nothing is broken, just a bit confusing.Additional Context
I'm using s3 as my backend and B2 as the remote s3 provider. All is working there fine. Again, none of this breaks anything. It just causes weird log messages that I don't understand. Thanks for any help you can provide and thanks for continuing to maintain this project!
Logs
Expected Behavior
No stack traces in the logs.
Steps To Reproduce
I'm using the
4.7.0
helm chart on k8s. I deploy the crds first, and then the helm chart, both via Argo CD. You can see my full values here:https://github.com/small-hack/argocd-apps/blob/730c3494444d19f8cad59184e0ba2039bcead4d6/k8up/k8up_argocd_appset.yaml#L42-L75
This happens with both Backups and Schedules manifests applied manually through kubectl.
Version of K8up
v2.10.0
Version of Kubernetes
1.29.5
Distribution of Kubernetes
K3s
The text was updated successfully, but these errors were encountered: