Decomission porche and serve artifacts.k8s.io from Fastly

[upodroid]

We are spending a fair bit of money serving artifacts.k8s.io from GCS. We have plenty of unused bandwidth from Fastly, so we should decommission porche and serve all the traffic directly from Fastly.

@justinsb @hakman @kubernetes/sig-k8s-infra-leads

[ameukam]

Probably switch to a private bucket+Fastly service before decommission porche.

[upodroid]

artifacts.k8s.io is now running on Fastly, starting the infra decommissioning now.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale