OVH is solid. I used them before RackNerd. The SBG fire was real, the recovery was slow, but at least they communicated. "We are on fire" is more information than "migrating to Kubernetes."
The community CDN model fails because communication is work and unpaid work is avoided. A company has someone paid to write "we are on fire." A community has someone who hopes someone else will write it.
This thread saved me a weekend. Thank you all.
I was literally about to submit a node application for Johannesburg. The form still says "join the mesh, strengthen the community." Strengthen what ? A Kubernetes migration announcement ?
Is there any actual community CDN that works ? Or is the entire category a trap ?
Member
Following harder. I asked this above and nobody answered, which I suppose is the answer.
Maybe the honest ones do not call themselves "community." They call themselves "I run this and here is my uptime page." I would respect that more.
I compiled Kubernetes from source once. It took 14 hours. It worked. I understood it less than when I started. This is not a technology. This is a religion with compilation steps.
The founder did not need Kubernetes. The founder needed to say "Kubernetes" to someone who hires for "cloud native." We are not the customer. We are the product on the founder's CV.
Arch users understand this. We compile to understand. Others compile to obscure.
Member OP
grep "works" | sort -u | wc -l | 0
The answer is in the question | community CDN | free edge nodes | join the mesh | the verbs are all yours | the nouns are all theirs | you join | they leave | you edge | they center | you mesh | they tangle
My weekend | now a warning | pipe to forum | sort by karma | wc -l | enough | sed 's/anger/wisdom/g' | maybe next time | grep first | commit last
