For a start, I filled out dummy answers (without submitting) to get to see
all the subsequent pages of the application form. You can see all the
questions they ask here:

https://docs.google.com/document/d/123fdfSGk5_tjdXAE0G1CeVcIpMBy9JBthwG0lwYjMXc/edit?usp=sharing

I could fill it out to the best of my ability, but want to give people a
chance to see the questions in case they have opinions on some of them.

On Wed, Aug 26, 2020 at 11:33 AM Ben Kochie <[email protected]> wrote:

> Yes, we should apply and get more details on the new FOSS plans.
>
> Anyone volunteer to take that on?
>
> On Wed, Aug 26, 2020 at 10:59 AM Julius Volz <[email protected]>
> wrote:
>
>> On Wed, Aug 26, 2020 at 10:16 AM Johannes Ziemke <[email protected]>
>> wrote:
>>
>>> Hi everyone,
>>>
>>> as mentioned in chat yesterday, Docker will limit the number of layers a
>>> user can pull within 6 hours:
>>>
>>>
>>> https://www.docker.com/blog/scaling-docker-to-serve-millions-more-developers-network-egress
>>>
>>> This will certainly cause problems for people pulling our images from
>>> the Docker Hub. Especially in Kubernetes scenarios where
>>> ImagePullPolicy=Always is common practice and often even enforced by
>>> running the AlwaysPullImages admission controller. This will likely lead to
>>> outages in dynamic environments (autoscaling, spot instances etc). I'd
>>> expect especially the node-exporter to be affected since it's probably the
>>> thing people run the most instances of in their infrastructure.
>>>
>>> There is not much we can do. We could beg Docker to void the limits for
>>> us
>>>
>>
>> I mean as the article states "Finally, as part of Docker’s commitment to
>> the open source community, before November 1 we will be announcing
>> availability of new open source plans. To apply for an open source plan,
>> please complete the short form here.".
>>
>> I wonder when exactly "before November 1" will be and how much time that
>> will give us to decide things. In case their OSS plans allow unlimited
>> pulls again, then we should be fine?
>>
>> But also fine switching to quay.io everywhere. But the general problem
>> is services that are expensive to run, but offered for free... wondering if
>> something similar will happen to quay.io at some point. But now that it
>> belongs to Red Hat, err, IBM, they might be big enough to not care about
>> the costs it produces.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Prometheus Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/prometheus-developers/CA%2BT6Yoy6qBfYQdEyidbs3MsAbvnKJZ6bDDr54Ha_rFLi%3DYP4ZQ%40mail.gmail.com
>> <https://groups.google.com/d/msgid/prometheus-developers/CA%2BT6Yoy6qBfYQdEyidbs3MsAbvnKJZ6bDDr54Ha_rFLi%3DYP4ZQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Prometheus Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/prometheus-developers/CA%2BT6YoyqdwOFRY5qgbzsVzb3idp8xw8UbnP8T734mXpycNytbQ%40mail.gmail.com.

Reply via email to