Re: Component Changes in CF-for-K8s


Jesse Weaver
 

We (the Loggregator team) are looking to replace the existing Loggregator infrastructure with Fluentd + Log Cache.

Please see our proposed architecture at https://docs.google.com/document/d/112yROjqKtTJLVgC4RbmXEfC2KLQqKY3VQ34hzTmBQIU/edit# ; we're looking to get early stages of this into CF4K8S very soon.


On Mon, Feb 10, 2020 at 3:01 AM Daniel Jones <daniel.jones@...> wrote:
Hi folks,

What's the deal with components in CF getting CNCF-friendly replacements in CF-for-K8s? The repo points out that Istio, envoy, kpack and fluentd are in the mix.

Presumably kpack is replacing traditional staging? And is fluentd replacing Loggregator, or supplementing it?

Has there been any discussion of what this means for maintaining feature parity between CF4BOSH and CF4K8s, and for technical certification of CF platforms?

Regards,
Daniel 'Deejay' Jones - CTO
+44 (0)79 8000 9153
EngineerBetter Ltd - More than cloud platform specialists

Join cf-dev@lists.cloudfoundry.org to automatically receive all group messages.