Remove Travis CI dependency

[lucperkins]

This PR removes the need for Travis CI in the build pipeline, running everything on Netlify CI instead

[netlify]

Deploy preview for kubernetes-io-master-staging ready!

Built with commit de18d61

https://deploy-preview-13598--kubernetes-io-master-staging.netlify.com

[zacharysarah]

@lucperkins This will need a follow-up PR in k/test-infra.

[lucperkins]

@zacharysarah FYI: kubernetes/test-infra#12050

[fejta]

What is the advantage of netlify over prow?

[lucperkins]

@fejta None, really. There’s just no need for Prow/Travis when all of our CI workloads can be on Netlify rather than split across multiple platforms. We have hundreds of contributors across an expanding range of language communities, and anything we can do to reduce the per-PR cognitive burden of contributing is a small win.

[fejta]

Running everything on a single system makes sense for sure.

Prow is built by the community and the most commonly used CI system, so if you're going to pick a single system for your workloads, all things being equal I would recommend using that over Netlify.

[lucperkins]

@fejta Prow was not, however, built to deploy websites and is thus not a subsititute for Netlify, which is the default web publishing platform for the Kubernetes ecosystem

[fejta]

Prow has a good gitops story. It will trigger arbitrary kubernetes pod workflows in response to git events. These building blocks will compose into a decent CD system.

For example, over in test-infra we use prow to github events and:

• Publish new images at each commit
• Create daily PRs requesting to update to these latest images
• Update deployments to use these new images when the PR merges

Similarly, I suspect we can use kubernetes pods to deploy the kubernetes websites. Long-term this would seem an interesting space to explore.

[lucperkins]

@fejta Netlify is a fully featured web publishing platform that offers Kubernetes ecosystem projects an enormous feature set, including per-PR deploy previews, cache invalidation, global CDN delivery, support for numerous build tools, file-based redirects, and much more. I think it would be unwise to attempt to recreate this feature set in any system.

[tengqm]

Conclusions?

[lucperkins]

@tengqm The original intent behind the PR stands

[zacharysarah]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: zacharysarah

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [zacharysarah]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[zacharysarah]

P.S. Comedy gold: