Agree with Christian, this is our internal wiring. As long as we
provide automated upgrade procedure which will seamlessly migrate from
heka to alternative we want, we should be good without deprecation per
se.
Cheers,
Michal
On 29 September 2016 at 04:36, Christian Berendt
wrote:
>> On 29 Sep 2
> On 29 Sep 2016, at 06:26, Steven Dake (stdake) wrote:
>
> If you have a different parsing of the deprecation policy, feel free to chime
> in.
Heka is only used as an internal component of Kolla and is not provided as a
service for the operators. It should be sufficient to replace Heka by som
First off, apologies for missing most of the team meeting today. I have read
through the logs and saw a discussion about deprecating heka. We need to
ensure that we follow the deprecation policy. My understanding of the
deprecation policy is as follows (in a nutshell):
1. We must mail
