[cf-dev] Component Changes in CF-for-K8s

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

[cf-dev] Component Changes in CF-for-K8s

Daniel Jones
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
_._,_._,_

Links:

You receive all messages sent to this group.

View/Reply Online (#8886) | [hidden email] | [hidden email] | Mute This Topic | New Topic


Reminder that all communication on this mailing list is subject to the Cloud Foundry Foundation's code of conduct, which can be found here: https://www.cloudfoundry.org/code-of-conduct/
Your Subscription | [hidden email] | Unsubscribe [[hidden email]]
_._,_._,_
Reply | Threaded
Open this post in threaded view
|

Re: [cf-dev] 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 <[hidden email]> 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

_._,_._,_

Links:

You receive all messages sent to this group.

View/Reply Online (#8888) | [hidden email] | [hidden email] | Mute This Topic | New Topic


Reminder that all communication on this mailing list is subject to the Cloud Foundry Foundation's code of conduct, which can be found here: https://www.cloudfoundry.org/code-of-conduct/
Your Subscription | [hidden email] | Unsubscribe [[hidden email]]
_._,_._,_
Reply | Threaded
Open this post in threaded view
|

Re: [cf-dev] Component Changes in CF-for-K8s

Scott Sisil
In reply to this post by Daniel Jones
Hi Daniel,

CAPI PM here - yes, kpack is replacing traditional staging in CF4K8s so we can move to an image based staging workflow for k8s.  The nice thing with kpack is that it makes use of CNB (buildpacks.io) and the buildpacks team has done the work to make sure this new buildpacks work in both CF4BOSH and CF4K8s.  

On Mon, Feb 10, 2020 at 4:00 AM Daniel Jones <[hidden email]> 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

_._,_._,_

Links:

You receive all messages sent to this group.

View/Reply Online (#8889) | [hidden email] | [hidden email] | Mute This Topic | New Topic


Reminder that all communication on this mailing list is subject to the Cloud Foundry Foundation's code of conduct, which can be found here: https://www.cloudfoundry.org/code-of-conduct/
Your Subscription | [hidden email] | Unsubscribe [[hidden email]]
_._,_._,_