- Component Changes in CF-for-K8s
Re: Component Changes in CF-for-K8s
toggle quoted messageShow quoted text
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.
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?
Daniel 'Deejay' Jones - CTO
+44 (0)79 8000 9153
Join firstname.lastname@example.org to automatically receive all group messages.