To update the package to go-systemd v22.0.0 we would need to get rid of the capnslog implementation. This blocks the update in other projects as well, like Kubernetes. (see https://github.com/kubernetes/kubernetes/pull/85097)
I know that it is already planned to replace capnslog with logrus, so I'd like to suggest in moving forward with this plan now. Is there anything to consider for the implementation? I saw that you have a deprecation policy, right?
Currently etcd supports both capnslog and zap logger. I believe capnslog will be deprecated in the next minor release 3.5.
/cc @gyuho - discussed at the kubecon
Hey @spzala 馃憢, do you have any idea how to move forward with this issue? Is the implementation already ongoing or do you still need assistance? :)
Hi @saschagrunert, I am currently working on removing capnslog from etcd. Should be able to sent out a PR in the next few days.
Awesome @jingyih, thank you for the update. :)
@saschagrunert FYI, removing of capnslog is tracked here #11426. I am trying to get all the changes ready by the end of this week.
@saschagrunert FYI, removing of capnslog is tracked here #11426. I am trying to get all the changes ready by the end of this week.
Awesome, thank you for the heads-up :green_heart:
@saschagrunert FYI, #11426 is done. capnslog is removed from etcd codebase.
Cool, thanks! Do you have any timeline for the next release to be cut?
I am not aware of any timeline. I would prefer to have v3.5 released mid this year.
Most helpful comment
Hi @saschagrunert, I am currently working on removing capnslog from etcd. Should be able to sent out a PR in the next few days.