Date   

Re: [VOTE] CoreDNS moving to graduation

Christopher LILJENSTOLPE <cdl@...>
 

+1 non binding

On Tue, Jan 15, 2019 at 9:47 AM Chris Aniszczyk <caniszczyk@...> wrote:
CoreDNS has requested to move to the graduation maturity level:
https://github.com/cncf/toc/pull/172

The CoreDNS community was one of earlier projects that joined CNCF at the inception/sandbox level on March 2017 (sponsored by Jon Boulle) and moved to the incubation maturity level on Feb 2018. As of Kubernetes v1.13, CoreDNS is the default DNS server (https://kubernetes.io/blog/2018/12/03/kubernetes-1-13-release-announcement/) and the community went under an external security audit last year sponsored by CNCF: https://coredns.io/2018/03/15/cure53-security-assessment/ 

The CoreDNS community believes it has fulfilled all the graduation criteria:

- Document that it is being used successfully in production by at least three independent end users:

* SoundCloud uses CoreDNS as internal cache+proxy in Kubernetes clusters to handle hundreds of thousands DNS service discovery requests per second.
* Infoblox uses CoreDNS in its Active Trust Cloud SaaS service, as well as for Kubernetes cluster DNS.
* Admiral uses CoreDNS to handle geographic DNS requests for our public-facing microservices.
* Qunar uses CoreDNS for service discovery of its GPU machine learning cloud with TensorFlow and Kubernetes.
* Tradeshift uses CoreDNS to look up company identifiers across multiple shards/regions/zones
* AdGuard uses CoreDNS in AdGuard Home and, therefore, in production public AdGuard DNS servers.
* Bose, Zalando, Yandex, Hellofresh, Sodimac, Kismia and many others use CoreDNS for their production's Kubernetes Cluster: https://github.com/coredns/coredns/blob/master/ADOPTERS.md

- Have a healthy number of committers and at least two from different organizations: 16+ maintainers: Google, Infoblox, Independent(s) - More than 100+ contributors - https://github.com/coredns/coredns/blob/master/OWNERS and https://github.com/coredns/coredns/graphs/contributors

- Demonstrate a substantial ongoing flow of commits and merged contributions: 10+ releases since becoming an incubating project and average about 150 PRs merged / quarter: https://all.devstats.cncf.io/d/54/project-health?orgId=1&var-repogroup_name=CoreDNS

- Have achieved a CII badge: https://bestpractices.coreinfrastructure.org/projects/1250

- Define a governance model: https://github.com/coredns/coredns/blob/master/GOVERNANCE.md

Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/172

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

--
Chris Aniszczyk (@cra) | +1-512-961-6719



--
Christopher LILJENSTOLPE
Co-Founder & CTO, Solutions
Tigera
cdl@... | @liljenstolpe | @liljenstolpe
Follow us: Blog  | Twitter | LinkedIn

Zero Trust Network Security & Continuous Compliance for Modern Applications


Re: [VOTE] CoreDNS moving to graduation

Benjamin Hindman
 

+1 binding


On Tue, Jan 15, 2019 at 12:47 PM Chris Aniszczyk <caniszczyk@...> wrote:
CoreDNS has requested to move to the graduation maturity level:
https://github.com/cncf/toc/pull/172

The CoreDNS community was one of earlier projects that joined CNCF at the inception/sandbox level on March 2017 (sponsored by Jon Boulle) and moved to the incubation maturity level on Feb 2018. As of Kubernetes v1.13, CoreDNS is the default DNS server (https://kubernetes.io/blog/2018/12/03/kubernetes-1-13-release-announcement/) and the community went under an external security audit last year sponsored by CNCF: https://coredns.io/2018/03/15/cure53-security-assessment/ 

The CoreDNS community believes it has fulfilled all the graduation criteria:

- Document that it is being used successfully in production by at least three independent end users:

* SoundCloud uses CoreDNS as internal cache+proxy in Kubernetes clusters to handle hundreds of thousands DNS service discovery requests per second.
* Infoblox uses CoreDNS in its Active Trust Cloud SaaS service, as well as for Kubernetes cluster DNS.
* Admiral uses CoreDNS to handle geographic DNS requests for our public-facing microservices.
* Qunar uses CoreDNS for service discovery of its GPU machine learning cloud with TensorFlow and Kubernetes.
* Tradeshift uses CoreDNS to look up company identifiers across multiple shards/regions/zones
* AdGuard uses CoreDNS in AdGuard Home and, therefore, in production public AdGuard DNS servers.
* Bose, Zalando, Yandex, Hellofresh, Sodimac, Kismia and many others use CoreDNS for their production's Kubernetes Cluster: https://github.com/coredns/coredns/blob/master/ADOPTERS.md

- Have a healthy number of committers and at least two from different organizations: 16+ maintainers: Google, Infoblox, Independent(s) - More than 100+ contributors - https://github.com/coredns/coredns/blob/master/OWNERS and https://github.com/coredns/coredns/graphs/contributors

- Demonstrate a substantial ongoing flow of commits and merged contributions: 10+ releases since becoming an incubating project and average about 150 PRs merged / quarter: https://all.devstats.cncf.io/d/54/project-health?orgId=1&var-repogroup_name=CoreDNS

- Have achieved a CII badge: https://bestpractices.coreinfrastructure.org/projects/1250

- Define a governance model: https://github.com/coredns/coredns/blob/master/GOVERNANCE.md

Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/172

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

--
Chris Aniszczyk (@cra) | +1-512-961-6719

--
Benjamin Hindman
Founder of Mesosphere and Co-Creator of Apache Mesos

Follow us on Twitter: @mesosphere

Follow Us Twitter LinkedIn Facebook YouTube
 


Re: [VOTE] CoreDNS moving to graduation

Ken Owens
 

+1 Binding

On Tue, Jan 15, 2019 at 11:47 AM Chris Aniszczyk <caniszczyk@...> wrote:
CoreDNS has requested to move to the graduation maturity level:
https://github.com/cncf/toc/pull/172

The CoreDNS community was one of earlier projects that joined CNCF at the inception/sandbox level on March 2017 (sponsored by Jon Boulle) and moved to the incubation maturity level on Feb 2018. As of Kubernetes v1.13, CoreDNS is the default DNS server (https://kubernetes.io/blog/2018/12/03/kubernetes-1-13-release-announcement/) and the community went under an external security audit last year sponsored by CNCF: https://coredns.io/2018/03/15/cure53-security-assessment/ 

The CoreDNS community believes it has fulfilled all the graduation criteria:

- Document that it is being used successfully in production by at least three independent end users:

* SoundCloud uses CoreDNS as internal cache+proxy in Kubernetes clusters to handle hundreds of thousands DNS service discovery requests per second.
* Infoblox uses CoreDNS in its Active Trust Cloud SaaS service, as well as for Kubernetes cluster DNS.
* Admiral uses CoreDNS to handle geographic DNS requests for our public-facing microservices.
* Qunar uses CoreDNS for service discovery of its GPU machine learning cloud with TensorFlow and Kubernetes.
* Tradeshift uses CoreDNS to look up company identifiers across multiple shards/regions/zones
* AdGuard uses CoreDNS in AdGuard Home and, therefore, in production public AdGuard DNS servers.
* Bose, Zalando, Yandex, Hellofresh, Sodimac, Kismia and many others use CoreDNS for their production's Kubernetes Cluster: https://github.com/coredns/coredns/blob/master/ADOPTERS.md

- Have a healthy number of committers and at least two from different organizations: 16+ maintainers: Google, Infoblox, Independent(s) - More than 100+ contributors - https://github.com/coredns/coredns/blob/master/OWNERS and https://github.com/coredns/coredns/graphs/contributors

- Demonstrate a substantial ongoing flow of commits and merged contributions: 10+ releases since becoming an incubating project and average about 150 PRs merged / quarter: https://all.devstats.cncf.io/d/54/project-health?orgId=1&var-repogroup_name=CoreDNS

- Have achieved a CII badge: https://bestpractices.coreinfrastructure.org/projects/1250

- Define a governance model: https://github.com/coredns/coredns/blob/master/GOVERNANCE.md

Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/172

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

--
Chris Aniszczyk (@cra) | +1-512-961-6719


Re: [VOTE] CoreDNS moving to graduation

郑淮城 <huaicheng.zheng@...>
 

+1 non-binding

 

郑淮城
星环信息科技(上海)有限公司
15216615728
徐汇区虹漕路88号越虹广场B11-12

 

 

发件人: <cncf-toc@...> 代表 "Wilson, Dan" <dan.wilson01@...>
日期: 2019119 星期六 上午5:03
收件人: Chris Aniszczyk <caniszczyk@...>, CNCF TOC <cncf-toc@...>
主题: Re: [cncf-toc] [VOTE] CoreDNS moving to graduation

 

+1 non-binding

 

 

From: <cncf-toc@...> on behalf of Chris Aniszczyk <caniszczyk@...>
Date: Tuesday, January 15, 2019 at 9:47 AM
To: CNCF TOC <cncf-toc@...>
Subject: [cncf-toc] [VOTE] CoreDNS moving to graduation

 

CoreDNS has requested to move to the graduation maturity level:
https://github.com/cncf/toc/pull/172

 

The CoreDNS community was one of earlier projects that joined CNCF at the inception/sandbox level on March 2017 (sponsored by Jon Boulle) and moved to the incubation maturity level on Feb 2018. As of Kubernetes v1.13, CoreDNS is the default DNS server (https://kubernetes.io/blog/2018/12/03/kubernetes-1-13-release-announcement/) and the community went under an external security audit last year sponsored by CNCF: https://coredns.io/2018/03/15/cure53-security-assessment/ 

The CoreDNS community believes it has fulfilled all the graduation criteria:

- Document that it is being used successfully in production by at least three independent end users:

 

* SoundCloud uses CoreDNS as internal cache+proxy in Kubernetes clusters to handle hundreds of thousands DNS service discovery requests per second.
* Infoblox uses CoreDNS in its Active Trust Cloud SaaS service, as well as for Kubernetes cluster DNS.
* Admiral uses CoreDNS to handle geographic DNS requests for our public-facing microservices.

* Qunar uses CoreDNS for service discovery of its GPU machine learning cloud with TensorFlow and Kubernetes.
* Tradeshift uses CoreDNS to look up company identifiers across multiple shards/regions/zones
* AdGuard uses CoreDNS in AdGuard Home and, therefore, in production public AdGuard DNS servers.
* Bose, Zalando, Yandex, Hellofresh, Sodimac, Kismia and many others use CoreDNS for their production's Kubernetes Cluster: https://github.com/coredns/coredns/blob/master/ADOPTERS.md


- Have a healthy number of committers and at least two from different organizations: 16+ maintainers: Google, Infoblox, Independent(s) - More than 100+ contributors - https://github.com/coredns/coredns/blob/master/OWNERS and https://github.com/coredns/coredns/graphs/contributors


- Demonstrate a substantial ongoing flow of commits and merged contributions: 10+ releases since becoming an incubating project and average about 150 PRs merged / quarter: https://all.devstats.cncf.io/d/54/project-health?orgId=1&var-repogroup_name=CoreDNS

- Have achieved a CII badge: https://bestpractices.coreinfrastructure.org/projects/1250

- Define a governance model: https://github.com/coredns/coredns/blob/master/GOVERNANCE.md

Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/172

 

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

 

--

Chris Aniszczyk (@cra) | +1-512-961-6719


Re: [VOTE] CoreDNS moving to graduation

Zhang Lei
 

+1 NB

We use & like CoreDNS!

On Fri, Jan 18, 2019 at 12:40 PM Benjamin Porter <bporter@...> wrote:
+1 non-binding

On Fri, Jan 18, 2019 at 11:34 AM Cathy zhang <cathy.h.zhang@...> wrote:

+1 non-binding

 

Cathy

 

From: cncf-toc@... [mailto:cncf-toc@...] On Behalf Of Christian Posta
Sent: Friday, January 18, 2019 8:54 AM
To: Chris Aniszczyk <caniszczyk@...>
Cc: CNCF TOC <cncf-toc@...>
Subject: Re: [cncf-toc] [VOTE] CoreDNS moving to graduation

 

+1 non binding

 

On Tue, Jan 15, 2019 at 10:47 AM Chris Aniszczyk <caniszczyk@...> wrote:

CoreDNS has requested to move to the graduation maturity level:
https://github.com/cncf/toc/pull/172

 

The CoreDNS community was one of earlier projects that joined CNCF at the inception/sandbox level on March 2017 (sponsored by Jon Boulle) and moved to the incubation maturity level on Feb 2018. As of Kubernetes v1.13, CoreDNS is the default DNS server (https://kubernetes.io/blog/2018/12/03/kubernetes-1-13-release-announcement/) and the community went under an external security audit last year sponsored by CNCF: https://coredns.io/2018/03/15/cure53-security-assessment/ 

The CoreDNS community believes it has fulfilled all the graduation criteria:

- Document that it is being used successfully in production by at least three independent end users:

 

* SoundCloud uses CoreDNS as internal cache+proxy in Kubernetes clusters to handle hundreds of thousands DNS service discovery requests per second.
* Infoblox uses CoreDNS in its Active Trust Cloud SaaS service, as well as for Kubernetes cluster DNS.
* Admiral uses CoreDNS to handle geographic DNS requests for our public-facing microservices.

* Qunar uses CoreDNS for service discovery of its GPU machine learning cloud with TensorFlow and Kubernetes.
* Tradeshift uses CoreDNS to look up company identifiers across multiple shards/regions/zones
* AdGuard uses CoreDNS in AdGuard Home and, therefore, in production public AdGuard DNS servers.
* Bose, Zalando, Yandex, Hellofresh, Sodimac, Kismia and many others use CoreDNS for their production's Kubernetes Cluster: https://github.com/coredns/coredns/blob/master/ADOPTERS.md


- Have a healthy number of committers and at least two from different organizations: 16+ maintainers: Google, Infoblox, Independent(s) - More than 100+ contributors - https://github.com/coredns/coredns/blob/master/OWNERS and https://github.com/coredns/coredns/graphs/contributors


- Demonstrate a substantial ongoing flow of commits and merged contributions: 10+ releases since becoming an incubating project and average about 150 PRs merged / quarter: https://all.devstats.cncf.io/d/54/project-health?orgId=1&var-repogroup_name=CoreDNS

- Have achieved a CII badge: https://bestpractices.coreinfrastructure.org/projects/1250

- Define a governance model: https://github.com/coredns/coredns/blob/master/GOVERNANCE.md

Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/172

 

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

 

--

Chris Aniszczyk (@cra) | +1-512-961-6719


 

--

Christian Posta

twitter: @christianposta

 

 

 


Re: [VOTE] CoreDNS moving to graduation

Ayrat Khayretdinov <akhayretdinov@...>
 

+1 (non-binding)


On Tue, Jan 15, 2019, 12:47 Chris Aniszczyk <caniszczyk@... wrote:
CoreDNS has requested to move to the graduation maturity level:
https://github.com/cncf/toc/pull/172

The CoreDNS community was one of earlier projects that joined CNCF at the inception/sandbox level on March 2017 (sponsored by Jon Boulle) and moved to the incubation maturity level on Feb 2018. As of Kubernetes v1.13, CoreDNS is the default DNS server (https://kubernetes.io/blog/2018/12/03/kubernetes-1-13-release-announcement/) and the community went under an external security audit last year sponsored by CNCF: https://coredns.io/2018/03/15/cure53-security-assessment/ 

The CoreDNS community believes it has fulfilled all the graduation criteria:

- Document that it is being used successfully in production by at least three independent end users:

* SoundCloud uses CoreDNS as internal cache+proxy in Kubernetes clusters to handle hundreds of thousands DNS service discovery requests per second.
* Infoblox uses CoreDNS in its Active Trust Cloud SaaS service, as well as for Kubernetes cluster DNS.
* Admiral uses CoreDNS to handle geographic DNS requests for our public-facing microservices.
* Qunar uses CoreDNS for service discovery of its GPU machine learning cloud with TensorFlow and Kubernetes.
* Tradeshift uses CoreDNS to look up company identifiers across multiple shards/regions/zones
* AdGuard uses CoreDNS in AdGuard Home and, therefore, in production public AdGuard DNS servers.
* Bose, Zalando, Yandex, Hellofresh, Sodimac, Kismia and many others use CoreDNS for their production's Kubernetes Cluster: https://github.com/coredns/coredns/blob/master/ADOPTERS.md

- Have a healthy number of committers and at least two from different organizations: 16+ maintainers: Google, Infoblox, Independent(s) - More than 100+ contributors - https://github.com/coredns/coredns/blob/master/OWNERS and https://github.com/coredns/coredns/graphs/contributors

- Demonstrate a substantial ongoing flow of commits and merged contributions: 10+ releases since becoming an incubating project and average about 150 PRs merged / quarter: https://all.devstats.cncf.io/d/54/project-health?orgId=1&var-repogroup_name=CoreDNS

- Have achieved a CII badge: https://bestpractices.coreinfrastructure.org/projects/1250

- Define a governance model: https://github.com/coredns/coredns/blob/master/GOVERNANCE.md

Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/172

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

--
Chris Aniszczyk (@cra) | +1-512-961-6719


Re: [VOTE] CoreDNS moving to graduation

Wilson, Dan <dan.wilson01@...>
 

+1 non-binding

 

 

From: <cncf-toc@...> on behalf of Chris Aniszczyk <caniszczyk@...>
Date: Tuesday, January 15, 2019 at 9:47 AM
To: CNCF TOC <cncf-toc@...>
Subject: [cncf-toc] [VOTE] CoreDNS moving to graduation

 

CoreDNS has requested to move to the graduation maturity level:
https://github.com/cncf/toc/pull/172

 

The CoreDNS community was one of earlier projects that joined CNCF at the inception/sandbox level on March 2017 (sponsored by Jon Boulle) and moved to the incubation maturity level on Feb 2018. As of Kubernetes v1.13, CoreDNS is the default DNS server (https://kubernetes.io/blog/2018/12/03/kubernetes-1-13-release-announcement/) and the community went under an external security audit last year sponsored by CNCF: https://coredns.io/2018/03/15/cure53-security-assessment/ 

The CoreDNS community believes it has fulfilled all the graduation criteria:

- Document that it is being used successfully in production by at least three independent end users:

 

* SoundCloud uses CoreDNS as internal cache+proxy in Kubernetes clusters to handle hundreds of thousands DNS service discovery requests per second.
* Infoblox uses CoreDNS in its Active Trust Cloud SaaS service, as well as for Kubernetes cluster DNS.
* Admiral uses CoreDNS to handle geographic DNS requests for our public-facing microservices.

* Qunar uses CoreDNS for service discovery of its GPU machine learning cloud with TensorFlow and Kubernetes.
* Tradeshift uses CoreDNS to look up company identifiers across multiple shards/regions/zones
* AdGuard uses CoreDNS in AdGuard Home and, therefore, in production public AdGuard DNS servers.
* Bose, Zalando, Yandex, Hellofresh, Sodimac, Kismia and many others use CoreDNS for their production's Kubernetes Cluster: https://github.com/coredns/coredns/blob/master/ADOPTERS.md


- Have a healthy number of committers and at least two from different organizations: 16+ maintainers: Google, Infoblox, Independent(s) - More than 100+ contributors - https://github.com/coredns/coredns/blob/master/OWNERS and https://github.com/coredns/coredns/graphs/contributors


- Demonstrate a substantial ongoing flow of commits and merged contributions: 10+ releases since becoming an incubating project and average about 150 PRs merged / quarter: https://all.devstats.cncf.io/d/54/project-health?orgId=1&var-repogroup_name=CoreDNS

- Have achieved a CII badge: https://bestpractices.coreinfrastructure.org/projects/1250

- Define a governance model: https://github.com/coredns/coredns/blob/master/GOVERNANCE.md

Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/172

 

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

 

--

Chris Aniszczyk (@cra) | +1-512-961-6719


Re: [VOTE] CoreDNS moving to graduation

bporter@...
 

+1 non-binding

On Fri, Jan 18, 2019 at 11:34 AM Cathy zhang <cathy.h.zhang@...> wrote:

+1 non-binding

 

Cathy

 

From: cncf-toc@... [mailto:cncf-toc@...] On Behalf Of Christian Posta
Sent: Friday, January 18, 2019 8:54 AM
To: Chris Aniszczyk <caniszczyk@...>
Cc: CNCF TOC <cncf-toc@...>
Subject: Re: [cncf-toc] [VOTE] CoreDNS moving to graduation

 

+1 non binding

 

On Tue, Jan 15, 2019 at 10:47 AM Chris Aniszczyk <caniszczyk@...> wrote:

CoreDNS has requested to move to the graduation maturity level:
https://github.com/cncf/toc/pull/172

 

The CoreDNS community was one of earlier projects that joined CNCF at the inception/sandbox level on March 2017 (sponsored by Jon Boulle) and moved to the incubation maturity level on Feb 2018. As of Kubernetes v1.13, CoreDNS is the default DNS server (https://kubernetes.io/blog/2018/12/03/kubernetes-1-13-release-announcement/) and the community went under an external security audit last year sponsored by CNCF: https://coredns.io/2018/03/15/cure53-security-assessment/ 

The CoreDNS community believes it has fulfilled all the graduation criteria:

- Document that it is being used successfully in production by at least three independent end users:

 

* SoundCloud uses CoreDNS as internal cache+proxy in Kubernetes clusters to handle hundreds of thousands DNS service discovery requests per second.
* Infoblox uses CoreDNS in its Active Trust Cloud SaaS service, as well as for Kubernetes cluster DNS.
* Admiral uses CoreDNS to handle geographic DNS requests for our public-facing microservices.

* Qunar uses CoreDNS for service discovery of its GPU machine learning cloud with TensorFlow and Kubernetes.
* Tradeshift uses CoreDNS to look up company identifiers across multiple shards/regions/zones
* AdGuard uses CoreDNS in AdGuard Home and, therefore, in production public AdGuard DNS servers.
* Bose, Zalando, Yandex, Hellofresh, Sodimac, Kismia and many others use CoreDNS for their production's Kubernetes Cluster: https://github.com/coredns/coredns/blob/master/ADOPTERS.md


- Have a healthy number of committers and at least two from different organizations: 16+ maintainers: Google, Infoblox, Independent(s) - More than 100+ contributors - https://github.com/coredns/coredns/blob/master/OWNERS and https://github.com/coredns/coredns/graphs/contributors


- Demonstrate a substantial ongoing flow of commits and merged contributions: 10+ releases since becoming an incubating project and average about 150 PRs merged / quarter: https://all.devstats.cncf.io/d/54/project-health?orgId=1&var-repogroup_name=CoreDNS

- Have achieved a CII badge: https://bestpractices.coreinfrastructure.org/projects/1250

- Define a governance model: https://github.com/coredns/coredns/blob/master/GOVERNANCE.md

Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/172

 

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

 

--

Chris Aniszczyk (@cra) | +1-512-961-6719


 

--

Christian Posta

twitter: @christianposta

 

 

 


Re: [VOTE] CoreDNS moving to graduation

Cathy zhang <cathy.h.zhang@...>
 

+1 non-binding

 

Cathy

 

From: cncf-toc@... [mailto:cncf-toc@...] On Behalf Of Christian Posta
Sent: Friday, January 18, 2019 8:54 AM
To: Chris Aniszczyk <caniszczyk@...>
Cc: CNCF TOC <cncf-toc@...>
Subject: Re: [cncf-toc] [VOTE] CoreDNS moving to graduation

 

+1 non binding

 

On Tue, Jan 15, 2019 at 10:47 AM Chris Aniszczyk <caniszczyk@...> wrote:

CoreDNS has requested to move to the graduation maturity level:
https://github.com/cncf/toc/pull/172

 

The CoreDNS community was one of earlier projects that joined CNCF at the inception/sandbox level on March 2017 (sponsored by Jon Boulle) and moved to the incubation maturity level on Feb 2018. As of Kubernetes v1.13, CoreDNS is the default DNS server (https://kubernetes.io/blog/2018/12/03/kubernetes-1-13-release-announcement/) and the community went under an external security audit last year sponsored by CNCF: https://coredns.io/2018/03/15/cure53-security-assessment/ 

The CoreDNS community believes it has fulfilled all the graduation criteria:

- Document that it is being used successfully in production by at least three independent end users:

 

* SoundCloud uses CoreDNS as internal cache+proxy in Kubernetes clusters to handle hundreds of thousands DNS service discovery requests per second.
* Infoblox uses CoreDNS in its Active Trust Cloud SaaS service, as well as for Kubernetes cluster DNS.
* Admiral uses CoreDNS to handle geographic DNS requests for our public-facing microservices.

* Qunar uses CoreDNS for service discovery of its GPU machine learning cloud with TensorFlow and Kubernetes.
* Tradeshift uses CoreDNS to look up company identifiers across multiple shards/regions/zones
* AdGuard uses CoreDNS in AdGuard Home and, therefore, in production public AdGuard DNS servers.
* Bose, Zalando, Yandex, Hellofresh, Sodimac, Kismia and many others use CoreDNS for their production's Kubernetes Cluster: https://github.com/coredns/coredns/blob/master/ADOPTERS.md


- Have a healthy number of committers and at least two from different organizations: 16+ maintainers: Google, Infoblox, Independent(s) - More than 100+ contributors - https://github.com/coredns/coredns/blob/master/OWNERS and https://github.com/coredns/coredns/graphs/contributors


- Demonstrate a substantial ongoing flow of commits and merged contributions: 10+ releases since becoming an incubating project and average about 150 PRs merged / quarter: https://all.devstats.cncf.io/d/54/project-health?orgId=1&var-repogroup_name=CoreDNS

- Have achieved a CII badge: https://bestpractices.coreinfrastructure.org/projects/1250

- Define a governance model: https://github.com/coredns/coredns/blob/master/GOVERNANCE.md

Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/172

 

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

 

--

Chris Aniszczyk (@cra) | +1-512-961-6719


 

--

Christian Posta

twitter: @christianposta

 

 

 


Re: [VOTE] CoreDNS moving to graduation

Christian Posta
 

+1 non binding

On Tue, Jan 15, 2019 at 10:47 AM Chris Aniszczyk <caniszczyk@...> wrote:
CoreDNS has requested to move to the graduation maturity level:
https://github.com/cncf/toc/pull/172

The CoreDNS community was one of earlier projects that joined CNCF at the inception/sandbox level on March 2017 (sponsored by Jon Boulle) and moved to the incubation maturity level on Feb 2018. As of Kubernetes v1.13, CoreDNS is the default DNS server (https://kubernetes.io/blog/2018/12/03/kubernetes-1-13-release-announcement/) and the community went under an external security audit last year sponsored by CNCF: https://coredns.io/2018/03/15/cure53-security-assessment/ 

The CoreDNS community believes it has fulfilled all the graduation criteria:

- Document that it is being used successfully in production by at least three independent end users:

* SoundCloud uses CoreDNS as internal cache+proxy in Kubernetes clusters to handle hundreds of thousands DNS service discovery requests per second.
* Infoblox uses CoreDNS in its Active Trust Cloud SaaS service, as well as for Kubernetes cluster DNS.
* Admiral uses CoreDNS to handle geographic DNS requests for our public-facing microservices.
* Qunar uses CoreDNS for service discovery of its GPU machine learning cloud with TensorFlow and Kubernetes.
* Tradeshift uses CoreDNS to look up company identifiers across multiple shards/regions/zones
* AdGuard uses CoreDNS in AdGuard Home and, therefore, in production public AdGuard DNS servers.
* Bose, Zalando, Yandex, Hellofresh, Sodimac, Kismia and many others use CoreDNS for their production's Kubernetes Cluster: https://github.com/coredns/coredns/blob/master/ADOPTERS.md

- Have a healthy number of committers and at least two from different organizations: 16+ maintainers: Google, Infoblox, Independent(s) - More than 100+ contributors - https://github.com/coredns/coredns/blob/master/OWNERS and https://github.com/coredns/coredns/graphs/contributors

- Demonstrate a substantial ongoing flow of commits and merged contributions: 10+ releases since becoming an incubating project and average about 150 PRs merged / quarter: https://all.devstats.cncf.io/d/54/project-health?orgId=1&var-repogroup_name=CoreDNS

- Have achieved a CII badge: https://bestpractices.coreinfrastructure.org/projects/1250

- Define a governance model: https://github.com/coredns/coredns/blob/master/GOVERNANCE.md

Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/172

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

--
Chris Aniszczyk (@cra) | +1-512-961-6719



--
Christian Posta
twitter: @christianposta




Re: [VOTE] CoreDNS moving to graduation

Erin Boyd
 

+1 non-binding

On Fri, Jan 18, 2019 at 9:24 AM Mark Peek via Lists.Cncf.Io <markpeek=vmware.com@...> wrote:

+1 non-binding

 

From: <cncf-toc@...> on behalf of Chris Aniszczyk <caniszczyk@...>
Date: Tuesday, January 15, 2019 at 9:47 AM
To: CNCF TOC <cncf-toc@...>
Subject: [cncf-toc] [VOTE] CoreDNS moving to graduation

 

CoreDNS has requested to move to the graduation maturity level:
https://github.com/cncf/toc/pull/172

 

The CoreDNS community was one of earlier projects that joined CNCF at the inception/sandbox level on March 2017 (sponsored by Jon Boulle) and moved to the incubation maturity level on Feb 2018. As of Kubernetes v1.13, CoreDNS is the default DNS server (https://kubernetes.io/blog/2018/12/03/kubernetes-1-13-release-announcement/) and the community went under an external security audit last year sponsored by CNCF: https://coredns.io/2018/03/15/cure53-security-assessment/ 

The CoreDNS community believes it has fulfilled all the graduation criteria:

- Document that it is being used successfully in production by at least three independent end users:

 

* SoundCloud uses CoreDNS as internal cache+proxy in Kubernetes clusters to handle hundreds of thousands DNS service discovery requests per second.
* Infoblox uses CoreDNS in its Active Trust Cloud SaaS service, as well as for Kubernetes cluster DNS.
* Admiral uses CoreDNS to handle geographic DNS requests for our public-facing microservices.

* Qunar uses CoreDNS for service discovery of its GPU machine learning cloud with TensorFlow and Kubernetes.
* Tradeshift uses CoreDNS to look up company identifiers across multiple shards/regions/zones
* AdGuard uses CoreDNS in AdGuard Home and, therefore, in production public AdGuard DNS servers.
* Bose, Zalando, Yandex, Hellofresh, Sodimac, Kismia and many others use CoreDNS for their production's Kubernetes Cluster: https://github.com/coredns/coredns/blob/master/ADOPTERS.md


- Have a healthy number of committers and at least two from different organizations: 16+ maintainers: Google, Infoblox, Independent(s) - More than 100+ contributors - https://github.com/coredns/coredns/blob/master/OWNERS and https://github.com/coredns/coredns/graphs/contributors


- Demonstrate a substantial ongoing flow of commits and merged contributions: 10+ releases since becoming an incubating project and average about 150 PRs merged / quarter: https://all.devstats.cncf.io/d/54/project-health?orgId=1&var-repogroup_name=CoreDNS

- Have achieved a CII badge: https://bestpractices.coreinfrastructure.org/projects/1250

- Define a governance model: https://github.com/coredns/coredns/blob/master/GOVERNANCE.md

Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/172

 

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

 

--

Chris Aniszczyk (@cra) | +1-512-961-6719


Re: [VOTE] CoreDNS moving to graduation

Mark Peek
 

+1 non-binding

 

From: <cncf-toc@...> on behalf of Chris Aniszczyk <caniszczyk@...>
Date: Tuesday, January 15, 2019 at 9:47 AM
To: CNCF TOC <cncf-toc@...>
Subject: [cncf-toc] [VOTE] CoreDNS moving to graduation

 

CoreDNS has requested to move to the graduation maturity level:
https://github.com/cncf/toc/pull/172

 

The CoreDNS community was one of earlier projects that joined CNCF at the inception/sandbox level on March 2017 (sponsored by Jon Boulle) and moved to the incubation maturity level on Feb 2018. As of Kubernetes v1.13, CoreDNS is the default DNS server (https://kubernetes.io/blog/2018/12/03/kubernetes-1-13-release-announcement/) and the community went under an external security audit last year sponsored by CNCF: https://coredns.io/2018/03/15/cure53-security-assessment/ 

The CoreDNS community believes it has fulfilled all the graduation criteria:

- Document that it is being used successfully in production by at least three independent end users:

 

* SoundCloud uses CoreDNS as internal cache+proxy in Kubernetes clusters to handle hundreds of thousands DNS service discovery requests per second.
* Infoblox uses CoreDNS in its Active Trust Cloud SaaS service, as well as for Kubernetes cluster DNS.
* Admiral uses CoreDNS to handle geographic DNS requests for our public-facing microservices.

* Qunar uses CoreDNS for service discovery of its GPU machine learning cloud with TensorFlow and Kubernetes.
* Tradeshift uses CoreDNS to look up company identifiers across multiple shards/regions/zones
* AdGuard uses CoreDNS in AdGuard Home and, therefore, in production public AdGuard DNS servers.
* Bose, Zalando, Yandex, Hellofresh, Sodimac, Kismia and many others use CoreDNS for their production's Kubernetes Cluster: https://github.com/coredns/coredns/blob/master/ADOPTERS.md


- Have a healthy number of committers and at least two from different organizations: 16+ maintainers: Google, Infoblox, Independent(s) - More than 100+ contributors - https://github.com/coredns/coredns/blob/master/OWNERS and https://github.com/coredns/coredns/graphs/contributors


- Demonstrate a substantial ongoing flow of commits and merged contributions: 10+ releases since becoming an incubating project and average about 150 PRs merged / quarter: https://all.devstats.cncf.io/d/54/project-health?orgId=1&var-repogroup_name=CoreDNS

- Have achieved a CII badge: https://bestpractices.coreinfrastructure.org/projects/1250

- Define a governance model: https://github.com/coredns/coredns/blob/master/GOVERNANCE.md

Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/172

 

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

 

--

Chris Aniszczyk (@cra) | +1-512-961-6719


Re: [VOTE] CoreDNS moving to graduation

Bryan Cantrill <bryan@...>
 

+1, binding.

        - Bryan


On Tue, Jan 15, 2019, 9:47 AM Chris Aniszczyk <caniszczyk@... wrote:
CoreDNS has requested to move to the graduation maturity level:
https://github.com/cncf/toc/pull/172

The CoreDNS community was one of earlier projects that joined CNCF at the inception/sandbox level on March 2017 (sponsored by Jon Boulle) and moved to the incubation maturity level on Feb 2018. As of Kubernetes v1.13, CoreDNS is the default DNS server (https://kubernetes.io/blog/2018/12/03/kubernetes-1-13-release-announcement/) and the community went under an external security audit last year sponsored by CNCF: https://coredns.io/2018/03/15/cure53-security-assessment/ 

The CoreDNS community believes it has fulfilled all the graduation criteria:

- Document that it is being used successfully in production by at least three independent end users:

* SoundCloud uses CoreDNS as internal cache+proxy in Kubernetes clusters to handle hundreds of thousands DNS service discovery requests per second.
* Infoblox uses CoreDNS in its Active Trust Cloud SaaS service, as well as for Kubernetes cluster DNS.
* Admiral uses CoreDNS to handle geographic DNS requests for our public-facing microservices.
* Qunar uses CoreDNS for service discovery of its GPU machine learning cloud with TensorFlow and Kubernetes.
* Tradeshift uses CoreDNS to look up company identifiers across multiple shards/regions/zones
* AdGuard uses CoreDNS in AdGuard Home and, therefore, in production public AdGuard DNS servers.
* Bose, Zalando, Yandex, Hellofresh, Sodimac, Kismia and many others use CoreDNS for their production's Kubernetes Cluster: https://github.com/coredns/coredns/blob/master/ADOPTERS.md

- Have a healthy number of committers and at least two from different organizations: 16+ maintainers: Google, Infoblox, Independent(s) - More than 100+ contributors - https://github.com/coredns/coredns/blob/master/OWNERS and https://github.com/coredns/coredns/graphs/contributors

- Demonstrate a substantial ongoing flow of commits and merged contributions: 10+ releases since becoming an incubating project and average about 150 PRs merged / quarter: https://all.devstats.cncf.io/d/54/project-health?orgId=1&var-repogroup_name=CoreDNS

- Have achieved a CII badge: https://bestpractices.coreinfrastructure.org/projects/1250

- Define a governance model: https://github.com/coredns/coredns/blob/master/GOVERNANCE.md

Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/172

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

--
Chris Aniszczyk (@cra) | +1-512-961-6719


Re: [VOTE] CoreDNS moving to graduation

Camille Fournier
 

+1 binding

On Tue, Jan 15, 2019 at 12:47 PM Chris Aniszczyk <caniszczyk@...> wrote:
CoreDNS has requested to move to the graduation maturity level:
https://github.com/cncf/toc/pull/172

The CoreDNS community was one of earlier projects that joined CNCF at the inception/sandbox level on March 2017 (sponsored by Jon Boulle) and moved to the incubation maturity level on Feb 2018. As of Kubernetes v1.13, CoreDNS is the default DNS server (https://kubernetes.io/blog/2018/12/03/kubernetes-1-13-release-announcement/) and the community went under an external security audit last year sponsored by CNCF: https://coredns.io/2018/03/15/cure53-security-assessment/ 

The CoreDNS community believes it has fulfilled all the graduation criteria:

- Document that it is being used successfully in production by at least three independent end users:

* SoundCloud uses CoreDNS as internal cache+proxy in Kubernetes clusters to handle hundreds of thousands DNS service discovery requests per second.
* Infoblox uses CoreDNS in its Active Trust Cloud SaaS service, as well as for Kubernetes cluster DNS.
* Admiral uses CoreDNS to handle geographic DNS requests for our public-facing microservices.
* Qunar uses CoreDNS for service discovery of its GPU machine learning cloud with TensorFlow and Kubernetes.
* Tradeshift uses CoreDNS to look up company identifiers across multiple shards/regions/zones
* AdGuard uses CoreDNS in AdGuard Home and, therefore, in production public AdGuard DNS servers.
* Bose, Zalando, Yandex, Hellofresh, Sodimac, Kismia and many others use CoreDNS for their production's Kubernetes Cluster: https://github.com/coredns/coredns/blob/master/ADOPTERS.md

- Have a healthy number of committers and at least two from different organizations: 16+ maintainers: Google, Infoblox, Independent(s) - More than 100+ contributors - https://github.com/coredns/coredns/blob/master/OWNERS and https://github.com/coredns/coredns/graphs/contributors

- Demonstrate a substantial ongoing flow of commits and merged contributions: 10+ releases since becoming an incubating project and average about 150 PRs merged / quarter: https://all.devstats.cncf.io/d/54/project-health?orgId=1&var-repogroup_name=CoreDNS

- Have achieved a CII badge: https://bestpractices.coreinfrastructure.org/projects/1250

- Define a governance model: https://github.com/coredns/coredns/blob/master/GOVERNANCE.md

Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/172

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

--
Chris Aniszczyk (@cra) | +1-512-961-6719


Re: RFC: Project Health Dashboard Updates

Richard Hartmann
 

This is developing nicely, thanks!

Two nitpicks:
* "Project health" vs "Projects health" is bad naming; how about
naming the latter "CNCF project overview" or something like that?
* Looking at the overview, I am unclear what entity IPB is in the
committer highscores and there's no way to click through to the data
to take a better look

On Tue, Jan 15, 2019 at 5:27 PM Chris Aniszczyk
<caniszczyk@...> wrote:

Here's the latest project health dashboard after initial rounds of feedbacks:
https://all.devstats.cncf.io/d/53/projects-health?orgId=1

If you want to filter by project, you can do that via here:
https://all.devstats.cncf.io/d/54/project-health?orgId=1&var-repogroup_name=Prometheus
https://all.devstats.cncf.io/d/54/project-health?orgId=1&var-repogroup_name=CoreDNS

Thanks and look forward to your feedback!

--
Chris Aniszczyk (@cra) | +1-512-961-6719


Re: [VOTE] CoreDNS moving to graduation

heng du
 

+1

徐翔轩 <eleven.xu@...> 于2019年1月17日周四 下午12:22写道:

+1 non-binding

在 2019年1月17日,12:14,Roman Chepurnyi via Lists.Cncf.Io <roman.chepurnyi=thredup.com@...> 写道:

+1 non-binding 

Roman

On Tue, Jan 15, 2019 at 9:47 AM Chris Aniszczyk <caniszczyk@...> wrote:
CoreDNS has requested to move to the graduation maturity level:
https://github.com/cncf/toc/pull/172

The CoreDNS community was one of earlier projects that joined CNCF at the inception/sandbox level on March 2017 (sponsored by Jon Boulle) and moved to the incubation maturity level on Feb 2018. As of Kubernetes v1.13, CoreDNS is the default DNS server (https://kubernetes.io/blog/2018/12/03/kubernetes-1-13-release-announcement/) and the community went under an external security audit last year sponsored by CNCF: https://coredns.io/2018/03/15/cure53-security-assessment/ 

The CoreDNS community believes it has fulfilled all the graduation criteria:

- Document that it is being used successfully in production by at least three independent end users:

* SoundCloud uses CoreDNS as internal cache+proxy in Kubernetes clusters to handle hundreds of thousands DNS service discovery requests per second.
* Infoblox uses CoreDNS in its Active Trust Cloud SaaS service, as well as for Kubernetes cluster DNS.
* Admiral uses CoreDNS to handle geographic DNS requests for our public-facing microservices.
* Qunar uses CoreDNS for service discovery of its GPU machine learning cloud with TensorFlow and Kubernetes.
* Tradeshift uses CoreDNS to look up company identifiers across multiple shards/regions/zones
* AdGuard uses CoreDNS in AdGuard Home and, therefore, in production public AdGuard DNS servers.
* Bose, Zalando, Yandex, Hellofresh, Sodimac, Kismia and many others use CoreDNS for their production's Kubernetes Cluster: https://github.com/coredns/coredns/blob/master/ADOPTERS.md

- Have a healthy number of committers and at least two from different organizations: 16+ maintainers: Google, Infoblox, Independent(s) - More than 100+ contributors - https://github.com/coredns/coredns/blob/master/OWNERSand https://github.com/coredns/coredns/graphs/contributors

- Demonstrate a substantial ongoing flow of commits and merged contributions: 10+ releases since becoming an incubating project and average about 150 PRs merged / quarter: https://all.devstats.cncf.io/d/54/project-health?orgId=1&var-repogroup_name=CoreDNS

- Have achieved a CII badge: https://bestpractices.coreinfrastructure.org/projects/1250

- Define a governance model: https://github.com/coredns/coredns/blob/master/GOVERNANCE.md

Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/172

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

-- 
Chris Aniszczyk (@cra) | +1-512-961-6719




-- 
Thanks,
Roman 


Re: [VOTE] CoreDNS moving to graduation

徐翔轩 <eleven.xu@...>
 

+1 non-binding

在 2019年1月17日,12:14,Roman Chepurnyi via Lists.Cncf.Io <roman.chepurnyi=thredup.com@...> 写道:

+1 non-binding 

Roman

On Tue, Jan 15, 2019 at 9:47 AM Chris Aniszczyk <caniszczyk@...> wrote:
CoreDNS has requested to move to the graduation maturity level:
https://github.com/cncf/toc/pull/172

The CoreDNS community was one of earlier projects that joined CNCF at the inception/sandbox level on March 2017 (sponsored by Jon Boulle) and moved to the incubation maturity level on Feb 2018. As of Kubernetes v1.13, CoreDNS is the default DNS server (https://kubernetes.io/blog/2018/12/03/kubernetes-1-13-release-announcement/) and the community went under an external security audit last year sponsored by CNCF: https://coredns.io/2018/03/15/cure53-security-assessment/ 

The CoreDNS community believes it has fulfilled all the graduation criteria:

- Document that it is being used successfully in production by at least three independent end users:

* SoundCloud uses CoreDNS as internal cache+proxy in Kubernetes clusters to handle hundreds of thousands DNS service discovery requests per second.
* Infoblox uses CoreDNS in its Active Trust Cloud SaaS service, as well as for Kubernetes cluster DNS.
* Admiral uses CoreDNS to handle geographic DNS requests for our public-facing microservices.
* Qunar uses CoreDNS for service discovery of its GPU machine learning cloud with TensorFlow and Kubernetes.
* Tradeshift uses CoreDNS to look up company identifiers across multiple shards/regions/zones
* AdGuard uses CoreDNS in AdGuard Home and, therefore, in production public AdGuard DNS servers.
* Bose, Zalando, Yandex, Hellofresh, Sodimac, Kismia and many others use CoreDNS for their production's Kubernetes Cluster: https://github.com/coredns/coredns/blob/master/ADOPTERS.md

- Have a healthy number of committers and at least two from different organizations: 16+ maintainers: Google, Infoblox, Independent(s) - More than 100+ contributors - https://github.com/coredns/coredns/blob/master/OWNERSand https://github.com/coredns/coredns/graphs/contributors

- Demonstrate a substantial ongoing flow of commits and merged contributions: 10+ releases since becoming an incubating project and average about 150 PRs merged / quarter: https://all.devstats.cncf.io/d/54/project-health?orgId=1&var-repogroup_name=CoreDNS

- Have achieved a CII badge: https://bestpractices.coreinfrastructure.org/projects/1250

- Define a governance model: https://github.com/coredns/coredns/blob/master/GOVERNANCE.md

Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/172

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

-- 
Chris Aniszczyk (@cra) | +1-512-961-6719




-- 
Thanks,
Roman 


Re: [VOTE] CoreDNS moving to graduation

Roman Chepurnyi
 

+1 non-binding 

Roman

On Tue, Jan 15, 2019 at 9:47 AM Chris Aniszczyk <caniszczyk@...> wrote:
CoreDNS has requested to move to the graduation maturity level:
https://github.com/cncf/toc/pull/172

The CoreDNS community was one of earlier projects that joined CNCF at the inception/sandbox level on March 2017 (sponsored by Jon Boulle) and moved to the incubation maturity level on Feb 2018. As of Kubernetes v1.13, CoreDNS is the default DNS server (https://kubernetes.io/blog/2018/12/03/kubernetes-1-13-release-announcement/) and the community went under an external security audit last year sponsored by CNCF: https://coredns.io/2018/03/15/cure53-security-assessment/ 

The CoreDNS community believes it has fulfilled all the graduation criteria:

- Document that it is being used successfully in production by at least three independent end users:

* SoundCloud uses CoreDNS as internal cache+proxy in Kubernetes clusters to handle hundreds of thousands DNS service discovery requests per second.
* Infoblox uses CoreDNS in its Active Trust Cloud SaaS service, as well as for Kubernetes cluster DNS.
* Admiral uses CoreDNS to handle geographic DNS requests for our public-facing microservices.
* Qunar uses CoreDNS for service discovery of its GPU machine learning cloud with TensorFlow and Kubernetes.
* Tradeshift uses CoreDNS to look up company identifiers across multiple shards/regions/zones
* AdGuard uses CoreDNS in AdGuard Home and, therefore, in production public AdGuard DNS servers.
* Bose, Zalando, Yandex, Hellofresh, Sodimac, Kismia and many others use CoreDNS for their production's Kubernetes Cluster: https://github.com/coredns/coredns/blob/master/ADOPTERS.md

- Have a healthy number of committers and at least two from different organizations: 16+ maintainers: Google, Infoblox, Independent(s) - More than 100+ contributors - https://github.com/coredns/coredns/blob/master/OWNERS and https://github.com/coredns/coredns/graphs/contributors

- Demonstrate a substantial ongoing flow of commits and merged contributions: 10+ releases since becoming an incubating project and average about 150 PRs merged / quarter: https://all.devstats.cncf.io/d/54/project-health?orgId=1&var-repogroup_name=CoreDNS

- Have achieved a CII badge: https://bestpractices.coreinfrastructure.org/projects/1250

- Define a governance model: https://github.com/coredns/coredns/blob/master/GOVERNANCE.md

Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/172

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

--
Chris Aniszczyk (@cra) | +1-512-961-6719



--
Thanks,
Roman 


Re: [VOTE] CoreDNS moving to graduation

GolfenGuo
 

+1 non-binding

 

 

Thanks

--

郭峰  Golfen Guo

+86 18016427071

Shanghai DaoCloud Network Technology Co,. Ltd

#Your Containers. Delivered!#

 

发件人: <cncf-toc@...> 代表 Chris Aniszczyk <caniszczyk@...>
日期: 2019116 星期三 上午1:47
收件人: CNCF TOC <cncf-toc@...>
主题: [cncf-toc] [VOTE] CoreDNS moving to graduation

 

CoreDNS has requested to move to the graduation maturity level:
https://github.com/cncf/toc/pull/172

 

The CoreDNS community was one of earlier projects that joined CNCF at the inception/sandbox level on March 2017 (sponsored by Jon Boulle) and moved to the incubation maturity level on Feb 2018. As of Kubernetes v1.13, CoreDNS is the default DNS server (https://kubernetes.io/blog/2018/12/03/kubernetes-1-13-release-announcement/) and the community went under an external security audit last year sponsored by CNCF: https://coredns.io/2018/03/15/cure53-security-assessment/ 

The CoreDNS community believes it has fulfilled all the graduation criteria:

- Document that it is being used successfully in production by at least three independent end users:

 

* SoundCloud uses CoreDNS as internal cache+proxy in Kubernetes clusters to handle hundreds of thousands DNS service discovery requests per second.
* Infoblox uses CoreDNS in its Active Trust Cloud SaaS service, as well as for Kubernetes cluster DNS.
* Admiral uses CoreDNS to handle geographic DNS requests for our public-facing microservices.

* Qunar uses CoreDNS for service discovery of its GPU machine learning cloud with TensorFlow and Kubernetes.
* Tradeshift uses CoreDNS to look up company identifiers across multiple shards/regions/zones
* AdGuard uses CoreDNS in AdGuard Home and, therefore, in production public AdGuard DNS servers.
* Bose, Zalando, Yandex, Hellofresh, Sodimac, Kismia and many others use CoreDNS for their production's Kubernetes Cluster: https://github.com/coredns/coredns/blob/master/ADOPTERS.md


- Have a healthy number of committers and at least two from different organizations: 16+ maintainers: Google, Infoblox, Independent(s) - More than 100+ contributors - https://github.com/coredns/coredns/blob/master/OWNERS and https://github.com/coredns/coredns/graphs/contributors


- Demonstrate a substantial ongoing flow of commits and merged contributions: 10+ releases since becoming an incubating project and average about 150 PRs merged / quarter: https://all.devstats.cncf.io/d/54/project-health?orgId=1&var-repogroup_name=CoreDNS

- Have achieved a CII badge: https://bestpractices.coreinfrastructure.org/projects/1250

- Define a governance model: https://github.com/coredns/coredns/blob/master/GOVERNANCE.md

Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/172

 

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

 

--

Chris Aniszczyk (@cra) | +1-512-961-6719


本邮件及附件含 DaoCloud 保密信息,仅限发送给上面地址中列出的个人或群组,禁止任何其他人以任何形式使用本邮件中的信息。若误收本邮件,请务必通知发送人并直接删去,不得使用、传播或复制本邮件。


Re: [VOTE] CoreDNS moving to graduation

Payne, Michael H
 

+1 non-binding

 

From: cncf-toc@... [mailto:cncf-toc@...] On Behalf Of Chris Aniszczyk
Sent: Tuesday, January 15, 2019 9:47 AM
To: CNCF TOC
Subject: [cncf-toc] [VOTE] CoreDNS moving to graduation

 

CoreDNS has requested to move to the graduation maturity level:
https://github.com/cncf/toc/pull/172

 

The CoreDNS community was one of earlier projects that joined CNCF at the inception/sandbox level on March 2017 (sponsored by Jon Boulle) and moved to the incubation maturity level on Feb 2018. As of Kubernetes v1.13, CoreDNS is the default DNS server (https://kubernetes.io/blog/2018/12/03/kubernetes-1-13-release-announcement/) and the community went under an external security audit last year sponsored by CNCF: https://coredns.io/2018/03/15/cure53-security-assessment/ 

The CoreDNS community believes it has fulfilled all the graduation criteria:

- Document that it is being used successfully in production by at least three independent end users:

 

* SoundCloud uses CoreDNS as internal cache+proxy in Kubernetes clusters to handle hundreds of thousands DNS service discovery requests per second.
* Infoblox uses CoreDNS in its Active Trust Cloud SaaS service, as well as for Kubernetes cluster DNS.
* Admiral uses CoreDNS to handle geographic DNS requests for our public-facing microservices.

* Qunar uses CoreDNS for service discovery of its GPU machine learning cloud with TensorFlow and Kubernetes.
* Tradeshift uses CoreDNS to look up company identifiers across multiple shards/regions/zones
* AdGuard uses CoreDNS in AdGuard Home and, therefore, in production public AdGuard DNS servers.
* Bose, Zalando, Yandex, Hellofresh, Sodimac, Kismia and many others use CoreDNS for their production's Kubernetes Cluster: https://github.com/coredns/coredns/blob/master/ADOPTERS.md


- Have a healthy number of committers and at least two from different organizations: 16+ maintainers: Google, Infoblox, Independent(s) - More than 100+ contributors - https://github.com/coredns/coredns/blob/master/OWNERS and https://github.com/coredns/coredns/graphs/contributors


- Demonstrate a substantial ongoing flow of commits and merged contributions: 10+ releases since becoming an incubating project and average about 150 PRs merged / quarter: https://all.devstats.cncf.io/d/54/project-health?orgId=1&var-repogroup_name=CoreDNS

- Have achieved a CII badge: https://bestpractices.coreinfrastructure.org/projects/1250

- Define a governance model: https://github.com/coredns/coredns/blob/master/GOVERNANCE.md

Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/172

 

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

 

--

Chris Aniszczyk (@cra) | +1-512-961-6719

This message is confidential and subject to terms at: https://www.jpmorgan.com/emaildisclaimer including on confidentiality, legal privilege, viruses and monitoring of electronic messages. If you are not the intended recipient, please delete this message and notify the sender immediately. Any unauthorized use is strictly prohibited.

4921 - 4940 of 7730