Create flakefinder.ci.kubevirt.io

[dhiller]

According to https://github.com/kubevirt/project-infra/blob/af319c994cb0c71cb1e134e1176a5ab5bfb97753/docs/cncf-tools.md#cncf-tools maintainers can administer the domains below kubevirt.io .

For better visibility of the reports, and to not always have to re-announce the entry page, a new subdomain address

flakefinder.ci.kubevirt.io

should be assigned to the FlakeFinder reports landing page

https://storage.googleapis.com/kubevirt-prow/reports/flakefinder/index.html

/cc @aburdenthehand

[dhiller]

/cc

[aburdenthehand]

@dhiller I have raised a ticket with servicedesk.

[dhiller]

We need to create a static website in our account to host the content, here's the docs how to do this: https://cloud.google.com/storage/docs/hosting-static-website?_ga=2.195525868.-1990292114.1669733613&_gac=1.182093397.1674215094.CjwKCAiAh9qdBhAOEiwAvxIok94RqAabu1pYopj4hSwUoUNEUhA9XytAYAnMGPra3rZTcmkKOwppPhoCoGEQAvD_BwE

[kubevirt-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[kubevirt-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

[kubevirt-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

[kubevirt-bot]

@kubevirt-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

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.

[dhiller]

/remove-lifecycle rotten

/reopen

[kubevirt-bot]

@dhiller: Reopened this issue.

In response to this:

/remove-lifecycle rotten

/reopen

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.

[kubevirt-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[kubevirt-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

[kubevirt-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

[kubevirt-bot]

@kubevirt-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

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.

[dhiller]

/reopen
/remove-lifecycle rotten

[kubevirt-bot]

@dhiller: Reopened this issue.

In response to this:

/reopen
/remove-lifecycle rotten

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.

[kubevirt-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[dhiller]

/lifecycle frozen

[brianmcarey]

@dhiller - for this we could just set up a simple webserver on the control plane cluster and host a copy of the latest flakefinder reports there? It would probably be more straight forward and the deployment could be controlled with automation.