[VOTE] CoreDNS moving to graduation


Chris Aniszczyk
 

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


John Belamaric
 

big surprise, but +1 non-binding from me :)

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


Ihor Dvoretskyi
 

+1 (non-binding)

On Tue, Jan 15, 2019 at 7: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


Alena Prokharchyk
 

+1 non binding


From: cncf-toc@... <cncf-toc@...> on behalf of Ihor Dvoretskyi <ihor.dvoretskyi@...>
Sent: Tuesday, January 15, 2019 9:49:34 AM
To: Chris Aniszczyk
Cc: CNCF TOC
Subject: Re: [cncf-toc] [VOTE] CoreDNS moving to graduation
 
+1 (non-binding)

On Tue, Jan 15, 2019 at 7: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


Sonya Koptyev <sonya@...>
 

+1 non-binding 

Thanks,
Sonya

Sonya Koptyev | Director of Evangelism | m: +1 425 505 0100



On Jan 15, 2019, 9:50 AM -0800, Alena Prokharchyk <alena@...>, wrote:

+1 non binding


From: cncf-toc@... <cncf-toc@...> on behalf of Ihor Dvoretskyi <ihor.dvoretskyi@...>
Sent: Tuesday, January 15, 2019 9:49:34 AM
To: Chris Aniszczyk
Cc: CNCF TOC
Subject: Re: [cncf-toc] [VOTE] CoreDNS moving to graduation
 
+1 (non-binding)

On Tue, Jan 15, 2019 at 7: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


Ruben Orduz <orduzr@...>
 

Decidedly +1 (non-binding)

On Jan 15, 2019, at 12:49 PM, Ihor Dvoretskyi <ihor.dvoretskyi@...> wrote:

+1 (non-binding)

On Tue, Jan 15, 2019 at 7: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




Randy Abernethy
 

+1 nb

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


--

--
Randy Abernethy
Managing Partner
RX-M, LLC
randy.abernethy@...
o 415-800-2922
c 415-624-6447


Lee Calcote
 

+1 non-binding

- Lee

On 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


Doug Davis <dug@...>
 

+1 non-binding


thanks
-Doug
_______________________________________________________
STSM | IBM Open Source, Cloud Architecture & Technology
(919) 254-6905 | IBM 444-6905 | dug@...
The more I'm around some people, the more I like my dog

"Chris Aniszczyk" ---01/15/2019 12:47:20 PM---CoreDNS has requested to move to the graduation maturity level: https://urldefense.proofpoint.com/v2

From: "Chris Aniszczyk" <caniszczyk@...>
To: CNCF TOC <cncf-toc@...>
Date: 01/15/2019 12:47 PM
Subject: [cncf-toc] [VOTE] CoreDNS moving to graduation
Sent by: cncf-toc@...





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




Yong Tang
 

+1 (non-binding)


From: cncf-toc@... <cncf-toc@...> on behalf of Chris Aniszczyk <caniszczyk@...>
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


Bob Killen <rkillen@...>
 

+1 non-binding

Great project seeing quite a bit of use :) 

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



--
Bob Killen
Research Cloud Administrator
University of Michigan


Igor Mameshin
 

+1 (non-binding)

Warm regards,
Igor

--
Igor Mameshin · CTO · Agile Stacks, Inc · Mobile: 858.229.7358 · igor@...




On Tue, Jan 15, 2019 at 9:55 AM Bob Killen <rkillen@...> wrote:
+1 non-binding

Great project seeing quite a bit of use :) 

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



--
Bob Killen
Research Cloud Administrator
University of Michigan


Justin Cormack
 

+1 (non binding)

On Tue, Jan 15, 2019 at 5: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


Richard Hartmann
 

+1 NB

On Tue, Jan 15, 2019 at 6: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


alexis richardson
 

+1 binding



On Tue, 15 Jan 2019, 18:33 Richard Hartmann, <richih@...> wrote:
+1 NB

On Tue, Jan 15, 2019 at 6: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
>




Liz Rice
 

+1 nb


On Tue, 15 Jan 2019 at 18:37, alexis richardson <alexis@...> wrote:
+1 binding



On Tue, 15 Jan 2019, 18:33 Richard Hartmann, <richih@...> wrote:
+1 NB

On Tue, Jan 15, 2019 at 6: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
>



--
Liz Rice
@lizrice  | lizrice.com+44 (0) 780 126 1145


Yassine Tijani <ytijani@...>
 

+1 nb

Le mar. 15 janv. 2019 à 19:51, Liz Rice <liz@...> a écrit :
+1 nb

On Tue, 15 Jan 2019 at 18:37, alexis richardson <alexis@...> wrote:
+1 binding



On Tue, 15 Jan 2019, 18:33 Richard Hartmann, <richih@...> wrote:
+1 NB

On Tue, Jan 15, 2019 at 6: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
>



--
Liz Rice
@lizrice  | lizrice.com+44 (0) 780 126 1145


nicolas.frankel@...
 

+1 non-binding

Best regards,

Nicolas Fränkel


Christian Jantz
 

+1 nb

Kind regards
Christian `Chris` Jantz


AWS Certified Solutions Architect - ProfessionalAWS Certified DevOps Engineer - ProfessionalAWS Certified Security - Specialty

I try to keep response times low but, that means being the most efficient. 
Taking this into account, please excuse my brevity of keeping messages to the point. 




On Tue, Jan 15 2019 at 7:54 PM, <nicolas.frankel@...> wrote:
+1 non-binding

Best regards,

Nicolas Fränkel


Roger Klorese
 

+1 (non-binding)


Roger B.A. Klorese
Senior Product Manager
SUSE
705 5th Ave S
Suite 1000
Seattle WA 98104
(P)+1 206.217.7432
(M)+1 425.444.5493
roger.klorese@...
Schedule a meeting: https://doodle.com/RogerKlorese
GPG Key: D567 F186 A6AE D244 067E  95E4 E67D 019F 0670 D9CC


From: cncf-toc@... <cncf-toc@...> on behalf of alexis richardson <alexis@...>
Sent: Tuesday, January 15, 2019 10:36:45 AM
To: Richard Hartmann
Cc: Chris Aniszczyk; CNCF TOC
Subject: Re: [cncf-toc] [VOTE] CoreDNS moving to graduation
 
+1 binding



On Tue, 15 Jan 2019, 18:33 Richard Hartmann, <richih@...> wrote:
+1 NB

On Tue, Jan 15, 2019 at 6: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
>