I think the FAQ states that only the inactive images will be scheduled for deletion. https://www.docker.com/pricing/retentionfaq What will happen to inactive images once the expiration date is

This is more of a question for CNCF Staff than the TOC :) I moved the issue here: https://github.com/cncf/foundation/issues/106 I haven't fully read the policy yet to understand the impact but we are

Starting Nov 1, 2020, Docker is planning to limit retention of images on Docker Hub for free accounts to 6m [1]. This will likely affect many CNCF projects that distribute binaries. For example, while

Hi everyone, Per the TOC's recommendation, the K3s team has updated our README.md to include a roadmap and some other information that hopefully helps clarify what K3s is and isn't. We appreciate the

+1 Binding

The TOC discussed the concerns around the PD dependency this morning. Given Liu's indication that the library could be migrated to the TiKV project, let's go ahead and do that. Liu, can you please

+1 binding

Thanks TOC for raising this concern. I am Tang Liu, and I am speaking here both as a TiKV maintainer and a member of the broader eco-system & community. It’s true that Placement Driver is an

It is described as "Placement driver for TiKV" and TiKV appears to have a strong dependency on it so perhaps pd should be considered part of TiKV? We should ask TiKV maintainers about this.

The chasm statement is interesting in the abstract. The well-deserved implication is “production use” is far to broad a term for a huge variety of situations, and I withdraw the question. Has the

Hi Liz, We may have missed this. I can take a look and get back to you asap. Thanks, Erin

Finally reviewing the TiKV graduation application. Mostly it looks great to me but has there been any discussion of TiKV's dependency on https://github.com/pingcap/pd? I’m not familiar with PD so

I can speak to some of this... The CNCF describes projects in terms of crossing the chasm. You can find that here. Sandbox is labeled as being for the innovators. A production recommendation really

sandbox projects are early stage / experimental and where we want to enable neutral collaboration. There is no DD so we are not giving any recommendations (Including not recommending for production).

To me, this does not feel like either of those two upstream projects. Characterizing k3s as packaging only or tooling used to manage Kubernetes is not addressing: The forking issue, e.g. not using

I expect there are many people in this thread that lack some context. So, I figured I'd try to add some. If someone has more to add or a correction please do so. These are intermixed with some of my

+1 (binding)

+100 NB. Great! Q

I don't think it needs to be accepted as a sandbox project. 1. What is the purpose of acceptance? 2. What is the difference between it and k8s? Finally, sandbox should not be abused. -1 정철

+1 non-binding Thank you, Acornsoft, Alex 2020년 8월 7일 (금) 오후 11:02, Jimmy Song <jimmysong@...>님이 작성: