Date   

Re: [VOTE] CoreDNS moving to graduation

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


Re: [VOTE] CoreDNS moving to graduation

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


Re: [VOTE] CoreDNS moving to graduation

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


Re: [VOTE] CoreDNS moving to graduation

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


Re: [VOTE] CoreDNS moving to graduation

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




Re: [VOTE] CoreDNS moving to graduation

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


Re: [VOTE] CoreDNS moving to graduation

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


Re: [VOTE] CoreDNS moving to graduation

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




Re: [VOTE] CoreDNS moving to graduation

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


Re: [VOTE] CoreDNS moving to graduation

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


Re: [VOTE] CoreDNS moving to graduation

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


Re: [VOTE] CoreDNS moving to graduation

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


[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


RFC: Project Health Dashboard Updates

Chris Aniszczyk
 

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


TOC Agenda 1/15/2019

Chris Aniszczyk
 

Hey all, happy 2019! The TOC is meeting for the first time in 2019 tomorrow:


The rough agenda:
- Categories/SIGs Discussion+Finalization
- TOC election update (election voting closes Jan 22nd)
- KubeCon/CNCon EU CFP closes Jan 18th
- End User Program Update by Cheryl
- Community Backlog

See you tomorrow!

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


Re: next TOC call?

alexis richardson
 

thank you!

@all -- please shout if you have urgent topics for next week's call.  I'd like to press on with the SIGs/Categories effort.

a

On Mon, Jan 7, 2019 at 2:14 PM Chris Aniszczyk <caniszczyk@...> wrote:
8 days time, 1st and 3rd Tue, we cancelled the 1st Tue meeting as it was new years

On Mon, Jan 7, 2019 at 8:13 AM alexis richardson <alexis@...> wrote:
Chris

Do we have a TOC call tomorrow, or is it in eight days time?

a



--
Cheers,

Chris Aniszczyk
http://aniszczyk.org
+1 512 961 6719


Re: next TOC call?

Chris Aniszczyk
 

8 days time, 1st and 3rd Tue, we cancelled the 1st Tue meeting as it was new years


On Mon, Jan 7, 2019 at 8:13 AM alexis richardson <alexis@...> wrote:
Chris

Do we have a TOC call tomorrow, or is it in eight days time?

a



--
Cheers,

Chris Aniszczyk
http://aniszczyk.org
+1 512 961 6719


next TOC call?

alexis richardson
 

Chris

Do we have a TOC call tomorrow, or is it in eight days time?

a


Re: 14 open source projects get EU funding for bug bounty payments

alexis richardson
 

Excellent Chris, thanks so much re bounties!

Happy 2019 all


On Tue, 1 Jan 2019, 16:01 Chris Aniszczyk, <caniszczyk@...> wrote:
Nice to see the EU doing this, more governments should do it as we need to secure our digital infrastructure :)

re: Dublin, you can search for all CNCF meetups here: https://meetup.com/pro/cncf

If you want to create your own meetup in Dublin or team up with someone, you can find more info here:

re: security and bug bounties, we're going to be piloting a bug bounty with Kubernetes in 2019, close to finalizing the direction:

Also, we're going to perform a security audit and open source the results in early 2019 for Kubernetes: https://github.com/kubernetes/steering/issues/71

Anyways, happy 2019!

On Tue, Jan 1, 2019 at 12:42 AM Vineet Gupta <vineet.scm@...> wrote:
This is great news and would increase a big participation from all the companies and individuals , although people use these projects even now as well.

Dublin seems to be a great location and really came up fast after Brexit talks , Is there any plans for CNCF community to do meetup in the future there?

Thanks

On Mon, Dec 31, 2018 at 8:45 PM alexis richardson <alexis@...> wrote:




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


Re: 14 open source projects get EU funding for bug bounty payments

Chris Aniszczyk
 

Nice to see the EU doing this, more governments should do it as we need to secure our digital infrastructure :)

re: Dublin, you can search for all CNCF meetups here: https://meetup.com/pro/cncf

If you want to create your own meetup in Dublin or team up with someone, you can find more info here:

re: security and bug bounties, we're going to be piloting a bug bounty with Kubernetes in 2019, close to finalizing the direction:

Also, we're going to perform a security audit and open source the results in early 2019 for Kubernetes: https://github.com/kubernetes/steering/issues/71

Anyways, happy 2019!


On Tue, Jan 1, 2019 at 12:42 AM Vineet Gupta <vineet.scm@...> wrote:
This is great news and would increase a big participation from all the companies and individuals , although people use these projects even now as well.

Dublin seems to be a great location and really came up fast after Brexit talks , Is there any plans for CNCF community to do meetup in the future there?

Thanks

On Mon, Dec 31, 2018 at 8:45 PM alexis richardson <alexis@...> wrote:




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

4941 - 4960 of 7712