Use main branch as the stable branch in Ingress demo

[rikatz]

We've renamed master to main (actually created a new one, over the stable branch and not the development branch).

So now we can use again the file present directly in main branch, assuming main is going to be the stable and that as soon as we release Ingress v1 that branch is gonna get merged into this one

[rikatz]

/cc @strongjz

[k8s-ci-robot]

@rikatz: GitHub didn't allow me to request PR reviews from the following users: strongjz.

Note that only kubernetes-sigs members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

/cc @strongjz

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[neolit123]

/lgtm

[aojea]

So now we can use again the file present directly in main branch, assuming main is going to be the stable and that as soon as we release Ingress v1 that branch is gonna get merged into this one

I can't follow, once you release v1 do we need to change again this file?

[rikatz]

Nope, we are going to use the main branch as the stable once we release v1.

So I'm going to merge the v1 branch into main branch, and we can add a note to people using k8s < v1.19 to point to the deprecated branch (which is called release-v1beta1 but we are going to find a better naming)

[BenTheElder]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: BenTheElder, rikatz

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 [BenTheElder]

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

[aojea]

Thanks Ricardo for the hard work